Use case for online grocery

1. Login
1.1Introduction
Login will verify the password and username of the person who is
trying to access the software components and restrict access on
wrong password and username allowing only the person incharge to
view /edit /update the components of software database
1.2Actors
DEO, customer, admin
1.3Pre conditions
The person should have the right username and password to log in
1.4Post conditions
The person is logged in and can view the data or make the required
changes
1.5Basic flow the person logs into the software system database
1.5.1 The system requests the actor for his/her username and
password
1.5.2 The actor enters his username and password
1.5.3 System validates name and password and if it finds it correct
allows the actor to log on into the system
1.6Alternative flow Invalid username and password
If in the basic flow enters wrong username or password the system
does not allow the actor to log in
1.7Special requirements none
1.8Use case requirements none

2. Manage customer database

2.1Introduction
Allow ADMIN to maintain customer details .This includes adding,
changing and deleting customer information
2.2Actors
ADMIN
2.3Pre conditions
ADMIN should be logged on to the system before this use case
begins
2.4Post conditions
If use case is successful customer details information is
added/updated /deleted from the system
2.5Basic Flow :
starts when ADMIN wishes to add/modify/update/delete
employee payment details
I.
The system requests the ADMIN to specify the function
he/she would like to perform (add/update /delete )
II.
One of the sub flow will execute after getting the information
a. If the ADMIN selects add customer details , add
customer details sub flow will execute

b. If ADMIN selects update customer details ,update

customer details sub flow will be executed
c. If ADMIN selects delete customer details ,delete
customer details sub flow will be executed
2.5.1 Add customer details
I.
The system requests the ADMIN to enter
Name
Address
II.
System generates unique ID
2.5.2
I.

Update a customer detail

System requires ADMIN to enter customer_id

II.ADMIN enters the customer_id.The system retrieves and

displays the student information
III.
IV.
2.5.3
I.
II.
III.
IV.
V.

The ADMIN makes the desired changes to the

customer information
After changes the system updates the customer
record with changed information
Delete a customer details
The system requests the ADMIN to specify the
customer_id
ADMIN enters the customer_id. The system retrives
and displays the customer information
The system prompts the ADMIN to confirm the
deletion of the customer
The ADMIN confirms the deletion
The system marks the customer record for deletion

2.6 Alternative flow

2.6.1 Customer not found
If in a update customer details or delete an customer
customer details sub flow a customer with the specific
customer_id
does not exist in the system the system displays an error
message
2.6.2 Update cancelled
If in the update customer details sub flow the ADMIN
decides not to update the customer details ,the update is
cancelled and the basic flow is restarted at the beginning
2.6.3 Delete cancelled
In the delete an customer details subflow if the ADMIN
decides not to delete a customer details record ,the delete
is cancelled and basic flow is re started at the beginning

2.7 special requirements-none

2.8 use case relationship none

3. Manage Items
3.1Introduction
Allow DEO to maintain item details .This includes adding, changing
and deleting item information
3.2Actors -DEO
3.3 Pre conditions-DEO should be logged on to the system
before this use case begins
3.4 Post conditions-If use case is successful item information is
added/updated /deleted from the system
3.5Basic Flow :starts when DEO wishes to
add/modify/update/delete item details
I.
The system requests the DEO to specify the function
he/she would like to perform (add/update /delete )
II.
One of the sub flow will execute after getting the
information
a. If the DEO selects add item details , add item
details sub flow will execute
b. If DEO selects update item details ,update item
details sub flow will be executed
c. If DEO selects delete item details ,delete item
details sub flow will be executed
3.5.1 Add item details
I.
The system requests the DEO to enter
Name
Price
Brand
3.5.2 Update a item details
I.
The DEO makes the desired changes to the
item information
II.
After changes the system updates the item
record with changed information
3.5.2 Delete a item details
i. The system requests the DEO to
specify the item info
ii.
iii.
iv.
v.

DEO enters the item info. The system retrieves and disp lays the
item information
The system prompts the DEO to confirm the deletion of the item
The DEO confirms the deletion
The system marks the item for deletion

3.6 Alternative flow

3.6.1 Item not found
If in a update item details or delete an item
item details sub flow a item with the specific item
does not exist in the system the system displays an error
message
3.6.2 Update cancelled
If in the update item sub flow the DEO decides not to
update the item details ,the update is cancelled and the
basic flow is restarted at the beginning
3.6.3 Delete cancelled
In the delete an item details subflow if the DEO decides not
to delete a item record ,the delete is cancelled and basic
flow is restarted at the beginning
3.7 special requirements-none
3.8 use case relationship none

4. View item
4.1 introduction the actor gets the view of item
4.2 actor customer
4.3 pre conditions None
4.4 post conditions if the use case is successful the employee is able to see the
item
4.5 Basic flow The actor searches for the desired item and gets the detailed view
of the item
4.6 Alternative flow The item does not exist in the database and an error message
comes up.
4.7 special requirements none
4.8 use case requirements none

5. View delivery options

5.1 introduction the actor views the delivery options and filld his desired
preferance

5.2 actor customer

5.3 pre conditions The item must be available for delivery to the actor
5.4 post conditions if the use case is successful the actor is able to fill in his desired
preference of delivery option
5.5 Basic flow The actor fills in his desired preference of delivery according to his
preferences and the order gets accepted
5.6 Alternative flow The item/delivery option is not available for the specific item
for the actor
5.7 special requirements none
5.8 use case requirements none

6 Cancel order
6.1 introduction the actor is able to cancel his placed order
6.2 actor customer
6.3 pre conditions The customer should be logged onto the system before
cancelling the order
6.4 post conditions if the use case is successful the customer is able to cancel his
placed order
6.5 Basic flow The customer acoording to his preferences if chosses to cancel an
order ,the order is cancelled
6.6 Alternative flow If the order the customer is trying to delete is not in his cart or
if the item has been dispatched for delivery ,or if the cancellation is not allowed by
the admin ,cancellation of the order fails
6.7 special requirements none
6.8 use case requirements none

7 Generate bill
7.1 introduction
The actor logs into to the system to generate the bill of the item and
payment details
7.2 Actors Admin

7.3 Pre conditions- The actor should be logged in the system to generate bill
7.4 Post condition- the bill is generated by the admin of different items
7.5 basic flow the admin enters the item details which generates the pay of
the specific customer
7.6 alternative-flow :the item does not match with any item in the list and gives an
error

message

7.7 special requirements none

7.8 use case requirements none

8 View payment options

8.1 introduction the actor views the payment options and fills his desired
preference
8.2 actor customer, admin
8.3 pre conditions The actor should have placed the order for item before selecting
payment options
8.4 post conditions if the item has a versatile mode of payment the actor can
choose it according to his preferences
8.6 Alternative flow The admin has not mentioned the payment option as per
desired preference of the customer on any particular item.
8.7 special requirements none
8.8 use case requirements none

9. Generate report
9.1 introduction-The actor logs into to the system to generate the report of the item
ordered and the payment details.
9.2 Actors Admin
9.3 Pre conditions- The actor should be logged in the system to generate report
9.4 Post condition- the report is generated by the admin of different items ordered
by the customer
9.5 basic flow the admin enters the item details which generates the report of
the specific item

9.6 alternative-flow the item does not match with any item in the list and gives an
error message
9.7 special requirements none
9.8 use case requirements none