Scribd
Upload
402 views12 pages

Test Note

The SDLC process and stages are defined including requirements analysis, design, coding, testing, deployment, and maintenance, with the goal of developing and maintaining software through this process.

Uploaded by

Hương Trần
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
402 views12 pages

Test Note

The SDLC process and stages are defined including requirements analysis, design, coding, testing, deployment, and maintenance, with the goal of developing and maintaining software through this process.

Uploaded by

Hương Trần
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Attd mangement System for HNAU:

S1:Requirement Analysis-->Problem given by client


1.Which i need to develop
Java
2.Mobile Apps/Web Apps
WebApps
3.What are the features/Functions i need to have
1.Mark the attd
2.View the attd Percentage
3.Report needs to be generated
4.How frequent you need to store attd.
Session wise.

S2:Design--->Solution to the Problem/Requirement


1. Algorithm
2. Flowcharts
3. Use case Daigrams,State Diagram

S3:Implementation
Coding--Java

S4:Testing
Validating the requirement[Are we building the right product?]-Validation
Verifing the code [Are we building product right?]-Verification

S5:Deployment of Software at client Place


[Installing the software at Client Place.]

S6:Maintenance:
1.Fix Bug
2.Adding new Features
Trigger the mail/Message to the scholars whose percentage is below 90.

Process of Software Development->Software Engineering


Req Analysis->Design->Coding->Testing->Deployment->Maintenance.[To develop/Maintain
Software]

attd min90%,internal 5-->pay-->generate Hall Ticket-->Exam[To write Exam]

Product Vs Process
Attd management Sys Vs

SDLC[Software Development Life Cycle]:


start--alot of stage->end
Stages: Req Analysis->Design->Coding->Testing->Deployment->Maintenance.
OutComes:SRS-->Design Document->Executable Application-->TestCase Document-->installation
Manual/User manual-->ChangeRequest
[Software Requirement Spectification].

Types OF SDLC Models:


1.WaterFall Model
2.sprial Model
3.Agile Model

SDLC:

1. Requirements:
- Online users
- Web app or mobile app
- Main Functions:
- Funds transfer…
2. Design:
- Design document about algorithm, flowchart, use case
3. Implementation: coding:
4. Testing
5. Deployment
6. Maintenance:

Exercise:

-future requirement: the account should be available in all formats PDF, Excel.
"Zebra Kingdom" is a brand new Amusement park that is going to be inaugurated shortly in the
City and is promoted as the place for breath-taking charm. The theme park has more than 30
exhilarating and thrilling rides and as a special feature of the park, the park Authorities have
placed many Booking Kiosks at the entrance which would facilitate the public to purchase their
entrance tickets and ride tickets.

There are few rides in the park that are not suitable for children and aged people, hence the
park Authorities wanted to program the kiosks to issue the tickets based on people’s age. If the
age given is less than 15 (Children) or greater than 60 (Aged), then the system should display as
"Not Allowed", otherwise it should display as "Allowed".

algorithm:
1. get the age
2. Consider:
age <15 or age > 60 --> display "Not allowed"
otherwise --> display "Allowed"
3.
START
Age = 0
If(age< 15 or age >60)
print NotAllowed
else
print Allowed
END
Testing the Food ordering online app:
Unit Test: for cart
- add item to cart
- update quantity
- delete item
- show and view item
- Check storage function of the cart after log out

Food ordering online app:

Intergration testing: (
- Checking detail data of food which is saved in database when resturants post thier food.
- Check detail information of buyer and driver when register.

System testing:
- Check for all funtions for a buyer: login, search, food cart, book a driver, place an order

- check function for seller(restaurants): login, post their product(food), post their discount(if
have), recieve oders form buyer

- Check funtion for driver: login, revivce order delivery from buyer and

System integration testing:


- check data flows among the buyer app, driver app and seller app when trying o place an order.
Customer name:

- Valid value: alphabet (2-64)


- Invalid value: alphabet <2
- Invalid value: alphabet > 64
 Boundary: alphabet 1, 2- 64, 65

Account number:

- Valid value: only digits, number > 0


- Invalid value: alphabets
- Invalid value: number <=0
 Boundary: digits 0, 1

Loan amount:

- Valid value: 500 – 900


- Invalid: <500 and >900
 Boundary: 499, 500-900, 901

R1 R2 R3 R4 R5 R6 R7 R8
Customer T T T F F F F T
Account T F F T T F F F
Loan T T F T F T F T
action Accepted Unaccepted Unaccepted Unaccepted Unaccepted Unaccepted Unaccepted Unaccepted

Use case: Order tracking

Actor: Customer

Pre-condition: Customer login and place an order

Post-condition: Message or email showing the order status

Events: Enter order id or name, press search button

Alternatives: see order status in online shopping system

Exceptions: User can view all status of order

Test case Test case 1 Test case 2 Test case 3 Test case 4
Start State Welcome to ATM ATM ask System display ATM ask
system customer for menu of customer for
enter PIN transaction other transaction
Input Insert card Enter PIN User choose Customer: want
withdraw money to finish
transaction transaction
Output Reading card and Valid PIN Transaction is ATM ejects card
accepted performed
Finish State ATM ask System display ATM ask End Process
customer for menu of customer for
enter PIN transaction other transaction

Test case ID format


Job Title:
+ Valid Value: Choose one of the selection
+ Invalide Value: Not choose any selection
Minimum Rating:
+ Valid Value: only digits, number >=0
+ Invalid Value: alphabets
` + Invalid value: number <0
--> Boundary: -1, 0, 1
Maximum rating:
+ Valid Value: only digits, number>=0 and number <= 100
+ Invalid Value: alphabets
` + Invalid value: number <0, number > 100
--> Boundary: -1, 0, 100, 101

S
 Only 6 test case design.
Note = desription
Better = one tag exit in only one test case

You might also like