Use Cases for Grocery Loots

8/3/2019 Use Cases for Grocery Loots

1/26

Use Cases for GroceryLoots 1

Use Cases

For

GroceryLoots

Version 1.0

Prepared by

Arsalan Ali Najwani

Syed Abid Hassan

Syed Shariq Ali

Farjad Feroz

Shaheed Zulfiqar Ali Bhutto Institute of Science & Technology (SZABIST)

Computer Science Department

October 11, 2011


2/26


Contents

Use Cases forAdmin Portal ..................................................................................................................... 5

1. Inventory Management................................................................................................................. 5

1.1. Inventory Catalogs .................................................................................................................... 5

2. Customers Management ............................................................................................................... 6

2.1. Customers ............................................................................................................................ 6

2.2. Customers Login .................................................................................................................. 7

2.3. Send Email to Customers...................................................................................................... 8

2.4. Customer Contact Requests .................................................................................................. 9

3. Distributor Management............................................................................................................. 10

3.1. Distributors ........................................................................................................................ 10

3.2. Distributors Login .............................................................................................................. 11

3.3. Send Email to Distributors.................................................................................................. 12

3.4. Distributor Contact Requests .............................................................................................. 12

4. Orders Management ................................................................................................................... 13

4.1. Orders ................................................................................................................................ 14

4.2. Orders History .................................................................................................................... 14

5. Revenue Management ................................................................................................................ 15

5.1. Revenue ............................................................................................................................. 15

Use Cases for Distributor Portal............................................................................................................. 16

1. Shop Management...................................................................................................................... 16

1.1. Shops ................................................................................................................................. 16

2. Orders Management ................................................................................................................... 18

2.1. Orders ................................................................................................................................ 18

2.2. Orders History .................................................................................................................... 19

3. Revenue Management ................................................................................................................ 19

3.1. Revenue ............................................................................................................................. 19

Use Cases for Customer View................................................................................................................ 20

1. Sign-Up ..................................................................................................................................... 20

2. Login ......................................................................................................................................... 21


3/26


3. Forgot Password......................................................................................................................... 22

4. Manage Personal Profile............................................................................................................. 22

5. Shopping Cart ............................................................................................................................ 23

6. Checkout.................................................................................................................................... 24

7. Purchase History ........................................................................................................................ 25


4/26


Use Case List

Primary Actor Use Cases for Administrator

Administrator Inventory CatalogsAdministrator Customers

Administrator Customers Login

Administrator Send Email to Customers

Administrator Customers Contact Requests

Administrator Distributors

Administrator Distributors Login

Administrator Send Email to Distributors

Administrator Distributors Contact Requests

Administrator Orders

Administrator Orders History

Administrator Revenue

Primary Actor Use Cases for Distributor Portal

Distributor Shops

Distributor Orders

Distributor Orders History

Distributor Revenue

Primary Actor Use Cases for Customer/Administrator/Distributor ViewAdmin. Distributor and Customer Sign-up

Admin. Distributor and Customer Login

Admin. Distributor and Customer Forgot Password

Admin. Distributor and Customer Manage Personal Profile

Primary Actor Use Cases for Customer View

Customer Shopping Cart

Customer Checkout

Customer Purchase History


5/26


Use Cases for Admin Portal

1. Inventory Management1.1. Inventory Catalogs

Use Case ID UC-1 Use Case Name Inventory Catalogs

Date Created 4th

October 2011 Date Last Updated 4th

October 2011

Scope E-Grocery

Primary Actor Administrator

Description This feature will allow an administrator to manage inventory catalogs andgrocery items.

Stake Holders and

Interestsy Admin - Will be responsible to manage the inventory catalogs and

grocery items.

Pre-Conditions y Application shouldbe properly sync with database. Buttons like (Add,Edit, and Delete) with proper functionality should be there.

y User must be an Admin.y Admin needs to login in to the system.

Post Conditions y Administrator has done with add, update, delete, rename or search ofgrocery catalogs and/or its items.

Frequency of

Occurrence

This feature will be used whenever the administrator needs to manage

inventory catalogs and/or grocery items.

Main Success Scenario

Actors Action Systems Response

Administrator enters URL of ourwebsite.

Lands on the Home page of the website

Administrator wishes to log-in to thesystem.

Login page is shown.

Administrator enters his username andpassword.

y Administrator authentication is performed.y Administrator is logged into the system.

Administrator wishes to manage

inventory catalogs and/or groceryitems.

Inventory Catalog page will be shown to the

Administrator.

Administrator wishes to perform

certain actions like add, edit/update,delete, rename, search of catalogsand/or grocery items.

In return the responses which system would provide are:

y Adding inventory catalogs and/or grocery items.y Editing/Updating the details of specific inventory

catalog and/or grocery items.

y Deleting specific inventory catalog and/or groceryitems.

y Categorizing grocery items into their respectivecatalogs.

y Providing the search results for grocery items.Administrator submits the changes

request.

Request is processed and all the views are updated.


6/26


Exceptions

y Incorrect Passwordo Error prompt will be shown asking to re-enter the login information.

y Database sync problemo Proper exception handling will be done and errors will be shown to the Admin so he can

rectify them as soon as possible.

2. Customers Management2.1.Customers

Use Case ID UC-2 Use Case Name Customers

Date Created 5th October 2011 Date LastUpdated

5th October 2011

Scope E-Grocery


Description This feature allows an administrator to manage customers in a way that

he can retrieve information about our customers and he can take certain

actions including editing of customers information, change passwordand to active/inactive any customer.

Stake Holders and

Interests

Admin: Allows managing existing customers.

Pre-Conditions y A pplication should be properly sync with database. Properinformation about our customers should be there in the database.Search box and the buttons (Add, Edit, Delete, change password,

active/inactive, and Export in CSV) with proper functionality

should be there.

y User must be an Administrator.y Administrator needs to login into the system.

Post Conditions Admin will be able to manage customers i.e. he can view active/inactivecustomers, make changes or delete/inactive any existing customer, and

export the report in CSV format.

Frequency of

Occurrence

This feature will be used whenever the admin wants to review the details

of customers, make changes to the customers profile and toactive/inactive any customer.



Administrator enters URL. Lands on the Home page of the websiteAdministrator wishes to log-in to thesystem.


Administrator enters his username and

Password.y Administrator authentication is performed.y Administrator is logged into the system

Administrator wishes to manage the

customers and then he clicks on

customers tab.

Customers Management page will be shown to the

Administrator, with the list of existing customers.


7/26


Administrator will select a Customer to

be managed.

Customer details will be shown to the Administrator.

Administrator wishes toadd/edit/delete/change password/active

or inactive a particular customer and

his details.

y System retrieves customers information.y Update in database when administrator will perform

actions like add, edit, delete, change password andactive/inactive any customer.

Administrator exports the list ofcustomers in CSV format.

Downloading window will be shown.

Exceptions




2.2.Customers Login

Use Case ID UC-3 Use Case Name Customers Login


5th October 2011

Scope E-Grocery


Description This feature will provide details about how many customers are

currently logged in.

Stake Holders and

Interests

Admin can estimate how many customers are currently logged in and

using our website.

Pre-Conditions yThe customer has already registered on our we

bsite and he/she iscurrently using our website. The functionality of login and

registration is working smoothly.

y User must be an administrator.y Administrator needs to login into the system.

Post Conditions y It will display the details of those customers which are currentlylogged in.

Frequency of

OccurrenceThis feature will be used whenever an admin wants to view the numberof customers currently logged in and using the website.


Actors Action Systems ResponseAdministrator enters URL. Lands on the Home page of the website

Administrator wishes to log-in to the

system.



Password.y Administrator authentication is performed.y Administrator is logged into the system

Administrator will click on customerlogin tab to check how many

System will provide the output by listing all thecustomers which are currently logged in.


8/26


customers are currently logged in and

using our website.

Exceptions




2.3.Send Email to Customers

Use Case ID UC-4 Use Case Name Send Email toCustomers

Date Created 5th October 2011 Date Last

Updated

5th October 2011

Scope E-Grocery


Description This feature will allow an administrator to send an email to customer(s)regarding any update, promotion/deals etc.

Stake Holders and

InterestsAdmin will let the customers know about any update/promotion/deals byusing this feature.

Pre-Conditions y SMTP and POP are active and running.y User must be an administrator.y Administrator needs to login into the system.

Post Conditions y Customer(s) receives an email.Frequency of

Occurrence

This feature will be used whenever an admin wants to send an email to

customer(s) regarding any update, promotion/deals etc.



Administrator enters URL. Lands on the Home page of the website




Password.y Administrator authentication is performed.y Administrator is logged into the system.

The administrator will click on sendemail to customerbutton where first he

will select an option from bulk mailoptions and then he will write a

message and finally he will click on

send button.

After pressing the send button our customer(s) willreceive an email.

Exceptions



9/26


y Problem in SMTP and POPo In case if misconfigurations in SMTP and POP cause any problem so configuration

management will be done by an admin.

2.4.Customer Contact Requests

Use Case ID UC-5 Use Case Name Customer ContactRequests


Updated

5th October 2011

Scope E-Grocery


Description This feature will allow an administrator to check and reply to themessages and queries which are sent by the customers.

Stake Holders and

Interests

Admin will use this features so he can interact with them and to

entertain their queries.

Pre-Conditions y Contact us page is there on the website and customers are using it.y User must be an administrator.y Administrator needs to login into the system.

Post Conditions y Prompt reply to the customers queries.Frequency of

Occurrence

This feature will be used whenever an admin needs to check and reply to

the messages and queries which are sent by the customers.





system.


Administrator enters his username andPassword.


The administrator will click oncustomer contact requests button tocheck all the messages and queries

which are received from customers and

the actions which he would takeinclude 1) Reply to those messages 2)

Delete those messages.

y Shows all the messages.y Delete the messages.y Send reply message to the customers.

Exceptions




y Problem in SMTP and POP


10/26


o In case if misconfigurations in SMTP and POP cause any problem so configurationmanagement will be done by an admin.

3. Distributor Management3.1.Distributors

Use Case ID UC-6 Use Case Name Distributors


Updated

5th October 2011

Scope E-Grocery


Description This feature allows an administrator to manage distributors in a way that

he can retrieve information about our distributors and he can take certainactions including editing of distributors information, change password

and to active/inactive any distributor.

Stake Holders and

Interests

Admin: Allows managing existing distributors.

Pre-Conditions y A pplication should be properly sync with database. Properinformation about our distributors should be there in the database.

Search box and the buttons (Add, Edit, Delete, change password,

activate/deactivate, and Export in CSV) with proper functionalityshould be there.

y User must be an Administrator.y Administrator needs to login into the system.

Post Conditions Admin will be able to manage distributors i.e. he can view

active/inactive distributors, make changes or delete any existingdistributor, export the report in CSV format.

Frequency ofOccurrence This feature willb

e used whenever the admin wants to review the detailsof distributors, make changes to the distributors profile and toactive/inactive any distributor.





system.


Administrator enters his username andPassword.


Administrator wishes to manage thedistributors and click on distributorstab.

Distributors Management page will be shown to theAdministrator, with the list of existing distributors.

Administrator will select a distributor

to be managed.

Distributors details will be shown to the Administrator.

Administrator wishes toadd/edit/delete/change password/active

or inactive a particular distributor and

his details.

y System retrieves distributors information.y Update in database when administrator will perform

actions like add, edit, delete, change password and


11/26


active/inactive any distributor.

Administrator exports the list ofdistributors in CSV format.

Downloading window will be shown.

Exceptions




3.2.Distributors Login

Use Case ID UC-7 Use Case Name Distributors Login


Updated

5th October 2011

Scope E-Grocery


Description This feature would provide details about how many distributors are

currently logged in.

Stake Holders and

Interests

Admin can estimate how many distributors are currently logged in andusing our website.

Pre-Conditions y The distributor has already registered on our website and he iscurrently using our website. The functionality of login andregistration is working smoothly.

y User must be an administrator.y Administrator needs to login into the system.

Post Conditionsy

It will display the details of those distrib

utors which are currentlylogged in.

Frequency of

Occurrence

This feature will be used whenever an admin wants to view the number

of distributors currently logged in and using the website.







Password.

y Administrator authentication is performed.y Administrator is logged into the system

Administrator will click on distributorslogin tab to check how many

distributors are currently logged in andusing our website.

System will provide the output by listing all thedistributors which are currently logged in.

Exceptions

y Incorrect Password


12/26


o Error prompt will be shown asking to re-enter the login information.y Database sync problem

o Proper exception handling will be done and errors will be shown to the Admin so he canrectify them as soon as possible.

3.3.Send Email to Distributors

Use Case ID UC-8 Use Case Name Send Email to

Distributors


5th October 2011

Scope E-Grocery


Description This feature will allow an administrator to send an email to distributor(s)regarding any update.

Stake Holders and

Interests

Admin will let the distributors know about any update by using thisfeature.

Pre-Conditions y SMTP and POP are active and running.y User must be an administrator.y Administrator needs to login into the system.

Post Conditions y Distributor(s) receives an email.Frequency of

OccurrenceThis feature will be used whenever an admin wants to send an email todistributor(s) regarding any update etc.




Administrator wishes to log-in to thesystem. Login page is shown.



The administrator will click on sendemail to distributors button where first

he will select an option from bulk mail

options and then he will write amessage and finally he will click on

send button.

After pressing the send button our distributor(s) willreceive an email.

Exceptions


y Problem in SMTP and POPo In case if misconfigurations in SMTP and POP cause any problem so configuration

management will be done by an admin.

3.4.Distributor Contact Requests


13/26


Use Case ID UC-9 Use Case Name Distributor Contact

Requests


5th October 2011

Scope E-Grocery


Description This feature will allow an administrator to check and reply to the

messages and queries which are sent by the distributors.

Stake Holders and

Interests

Admin will use this features so he can interact with them and to

entertain their queries.

Pre-Conditions y Contact us page is there on the website and distributors are using it.y User must be an administrator.y Administrator needs to login into the system.

Post Conditions y Prompt reply to the distributors queries.Frequency of

Occurrence

This feature will be used whenever an admin needs to check and reply tothe messages and queries which are sent by the distributors.





system.




The administrator will click on

distributor contact requests button tocheck all the messages and queries

which are received from distributorsand the actions which he would take

include 1) Reply to those messages 2)

Delete those messages.

y Shows all the messages.y Delete the messages.y Send reply message to the distributors.

Exceptions



rectify them as soon as possible.y Problem in SMTP and POP

o In case if misconfigurations in SMTP and POP cause any problem so configurationmanagement will be done by an admin.

4. Orders Management


14/26


4.1.Orders

Use Case ID UC-10 Use Case Name Orders

Date Created 5th October 2011 Date Last Updated 5th October 2011

Scope E-Grocery


Description This feature allows an administrator to keep track of customers orders.

Stake Holders and

Interestsy Admin- Admin can view all the orders and keep track of them.

Pre-Conditions y Administrator needs to be logged-in to the system.y Customer has already placed an order.

Post Conditions Order details will be shown to the Administrator like order is delivered,in a queue or cancelled/money refunded.

Frequency of

Occurrence

This process will be used whenever an administrator wants to view the

order and its status or wants to cancel any order.








The administrator will click on the

orders tab to keep track of daily orders

and their respective customers.

Order management interface is shown.

In case if any unwanted situation occur

administrator can choose cancel and

refund option.

Order is cancelled and the money is refunded.

Exceptions


y Database sync problemo Proper exception handling will be done and errors will be shown to the Admin so he canrectify them as soon as possible.

4.2.Orders History

Use Case ID UC-11 Use Case Name Orders History


Scope E-Grocery


15/26



Description This feature allows an administrator to keep track of the orders whichhave been placed on the website so far.

Stake Holders and

Interestsy Admin- Admin can view all the history of the orders which have

been placed so far.

Pre-Conditions y Proper maintenance of orders log. Searching option is there on thewebsite.

y Administrator needs to be logged-in to the system.Post Conditions y It will show the complete list of orders which have been placed so

farby the customer(s).

Frequency of

Occurrence

This process will be used whenever an administrator wants to view theorder history.


Actors Action Systems ResponseAdministrator enters URL. Lands on the Home page of the website


system.



Password.y Administrator authentication is performed.y Administrator is Logged into the system

An administrator will click on ordershistory tab to check the orders historyi.e. the orders which have been placed

so far. An administrator can also

search the orders history of a specific

customer.

y Order management interface is shown.y Show the complete list of orders which have been

placed so farby the customer(s).

Exceptions




5. Revenue Management5.1.Revenue

Use Case ID UC-12 Use Case Name Revenue


Scope E-Grocery


Description To calculate and view earned revenues.


16/26


Stake Holders and

Interestsy AdministratorWill be able to calculate overall business

revenues.

Pre-Conditions Administrator needs to be logged-in to the system.

Post Conditions Earned revenues table will be shown to the Administrator.

Frequency of

Occurrence

This process will be used wheneverAdministrator wants to view or

calculate the earned profits/revenues.





system.


Administrator enters ID and Password. y Administrator authentication is performed.y Administrator is Logged into the system

Administrator wishes to view revenuesearned.

Revenue management interface is shown.

Administrator wishes to calculaterevenues.

System will provide the following calculating options;Day

Week

MonthYearOverall

Exceptions




Use Cases for Distributor Portal

1. Shop Management1.1.ShopsUse Case ID UC-13 Use Case Name Shops


Scope E-Grocery

Primary Actor Distributor

Description This feature will allow Distributor to manage shop, i.e. their profiles anddetails.

Stake Holders and

Interests

Distributor- Allows managing existing shops as well as adding new

shops.


17/26


Pre-Conditions y User must be distributor.y Distributor needs to login into the system.

Post Conditions Distributor will be able to manage shops under him.

Frequency of

Occurrence

Whenever the distributor wants to view the list of shops or update the

list, this feature will be used.



Distributor enters URL. Lands on the Home page of the website

Distributor wishes to log-in to the

system.


Distributor enters ID and Password. y Distributor authentication is performed.y Distributor is logged into the system

Distributor wishes to manage theShops.

Shop Management page will be shown to the distributor,with the list of existing shops under that distributor.

Distributor will select a shop to be

managed.

Shop details will be shown to the distributor.

Distributor wishes to edit a particularshop details.

Distributor will be given multiple options to manage aparticular shop. Which includes;

y Shops under the distributory Managing a Shop Profiley Add a shop to the listy Deleting a shop.

Distributor makes changes through the

interface.

Changes will be saved along with the updating of

database and all the views.

Exceptions

y Incorrect Passwordo Error prompt will be shown asking to re-enter the login information

Extensions

y Editing Shop Detailso Distributor can make changes to the details of the shop in his own list only.o The new data will be stored in the database and a confirmation message will be displayed

on the screen.

y Deleting a particular Shopo In order to delete a Shop, Distributor will select a particularshop and select the delete

option.

o The database will be updated and the particular shop will be deleted along with theupdating of all the views. Confirmation message will be shown on screen.

y Adding a Shopo If the Distributor wishes to add a Shop, then he will use this option.o Distributor will provide the valid shop details and then add shop.o Database will be updated and a new shop will be added to the list of that distributor.


18/26


2. Orders Management2.1. Orders

Use Case ID UC-14 Use Case Name Orders

Date Created 5

th

Octob

er 2011 Date Last Updated 5

th

Octob

er 2011Scope E-Grocery


Description To view the orders and update its status.

Stake Holders and

Interestsy Distributor- Each distributor will be able to view his orders and

update their status.

Pre-Conditions y Distributor needs to be logged-in to the system.Post Conditions y Order details will be shown to the Distributor.Frequency of

Occurrence

This process will be used whenever Distributor wants to view the orders

or update the order status.





system.


Distributor enters ID and Password. y Distributor authentication is performed.y Distributor is Logged into the system

Distributor wishes to view the orders. Order management interface is shown.

Distributor wishes to update the orderstatus.

System will provide the following options to theDistributor;

y View Ordersy Update Order Status

Exceptions


Extensions

y Update order Statuso Only distributor can update the status of order, i.e. from pendingto delivered.o Once the status is updated, Admin's and Customers view is also updated along with

updating of database.

y View Orderso Distributor will be able to view the current orders as well as the previous orders.o Each Distributor and Customer can view only his orders.


19/26


2.2.Orders History

Use Case ID UC-15 Use Case Name Orders History


Scope E-Grocery

Primary Actor Distrib

utorDescription This feature allows distributor to keep track of the orders which have

been assigned to him so far.

Stake Holders and

Interests

Distributor - Distributor can view all the history of the orders which

have been assigned to him so far.

Pre-Conditions y Proper maintenance of orders log. Searching option is there on thewebsite.

y Distributor needs to be logged-in to the system.Post Conditions It will show the complete list of orders which have been assigned to him

so far.

Frequency of

Occurrence

This process will be used whenever Distributor wants to view his order

history.





system.


Distributor enters his username andPassword.

y Distributor authentication is performed.y Distributor is Logged into the system

Distrib

utor will click on orders historytab to check the orders history i.e. the

orders which have been assigned to

him so far. Distributor can also searchthe orders history for a specific date.

yOrder management interface is shown.

y Show the complete list of orders which have beenassigned so far to him.

Exceptions


3. Revenue Management3.1. Revenue

Use Case ID UC-16 Use Case Name Revenue


Scope E-Grocery


Description To calculate and view earned revenues.


20/26


Stake Holders and

Interestsy Distributor- Each distributor will be able to view his earned profits.

Pre-Conditions Distributor needs to be logged-in to the system.

Post Conditions Earned revenues table will be shown to the Distributor.

Frequency of

Occurrence

This process will be used whenever Distributor wants to view the earned

profits/revenues.





system.


Distributor enters ID and Password. y Distributor authentication is performed.y Distributor is Logged into the system

Distributor wishes to view revenues

earned.

Revenue management interface is shown.

Distributor wishes to calculaterevenues.

System will provide the following calculating options;Day.

Week.

Month.Year.Overall.

Exceptions


Use Cases for Customer View

1. Sign-UpUse Case ID UC-17 Use Case Name Sign-Up

Date Created 4th

October 2011 Date Created 4th

October 2011

Scope E-Grocery

Primary Actor User(Customer)

DistributorAdministrator

Description It will allow users to become the member of the website.

Stake Holders and

Interests

User- He will be able to commit and manage his purchases.

Pre-Conditions y Access to the internety User has filled the registration form properly and all the

information he has provided is valid.


21/26


Post Conditions Upon logging in, registered users can perform desired operations.

Frequency of Occurrence First time user will use this feature in order to get complete access.



User enters URL. Lands on the Home page of the website

User wishes to register. Registration page is shown.

User clicks on sign-up button and

enters desired details which includesusername, password, address etc.

y Availability is checked.y Proper Validation and Verification of the fields.y User is registered onto the website.

Exceptions

y Incomplete/Incorrect Detailso In case of incomplete/incorrect information customer will be prompted to re-enter the

information.y Unavailable/Occupied ID

o Customer will be asked to choose a different ID.2. LoginUse Case ID UC-18 Use Case Name Login


Scope E-Grocery


Customer

DistributorDescription It deals with the detailed login procedure of GroceryLoots.

Stake Holders and

Interests

AdministratorHe will get the access to overall management

features of the Portal.Customer - He will be able to commit and manage his purchases.Distributor- He will get access to his Portal.

Pre-Conditions Provision of valid and authenticated ID and Password along with

the access to internet.

Post Conditions Upon logging in, user can perform desired operations.

Frequency of Occurrence In order to access the core features user always needs to be loggedinto the Website.




User wishes to log into the system. Login page is shown.

User enters ID and Password y User authentication is performed.y User is Logged into the system


22/26


Exceptions


y Un-registered Usero User will be asked to sign-up/register to the website

3. Forgot PasswordUse Case ID UC-19 Use Case Name Login

Date Created 4th


October 2011

Scope E-Grocery


CustomerDistributor

Description It will allow a user to reset his/her password.

Stake Holders and

Interests

User will reset their passwords from this feature.

Pre-Conditions User is already registered on our website.

Post Conditions User will receive an email which would allow him/her to reset

his/her password.

Frequency of Occurrence User will use this feature when he forgets his password and want to

reset it.



User enters URL. Lands on the Home page of the web

siteUser clicks on forgot password buttonwhere he enters his email address andusername and then he submits the

request.

User receives an email which would allow him/her toreset his/her password.

Exceptions

y Incorrect Email ID or Usernameo Error prompt will be shown asking to re-enter the desired information

y Un-registered Usero User will be asked to sign-up/register to the website.

4. Manage Personal ProfileUse Case ID UC-20 Use Case Name Manage Personal

Profile

Date Created 4th October 2011 Date Created 4th October 2011

Scope E-Grocery



23/26


Customer

Distributor

Description Actors will be able to manage their personal profile.

Stakeholders and

Interests

Admin/Customer/Distributor- Canmanage their personal profiles i.e.

Update or View profile.

Pre-Conditions User should be logged-in to the system.

Post Conditions User will be able to manage the profile.

Frequency of

Occurrence

This operation will be used whenever the user wishes to edit/update hispersonal profile.




User wishes to log-in to the system. Login page is shown.

User enters ID and Password. y User authentication is performed.y

User is Logged into the systemUser wishes to manage the profile. Profile will be shown to the user.

User wishes to edit/update the profile. System will provide the following options;

y Editing/Updating Information.y Deactivate the profile.

Exceptions


Extensions

y If user wants to edit his personal detailso If user wants to update his details then he will click settings and select update personal

profile options.

o All the information of the user will be displayed on the screen.o User can make changes to any of his data like e-mail, location etc. and press submit.o The new data will be stored in the database and a confirmation message will be displayed

on the screen.

y Deactivating Accounto If user wants to deactivate his account then he will click the deactivate button and the

account will be deactivated.

o The database will be updated and the status of particular user will be changed todeactivate.5. Shopping CartUse Case ID UC-21 Use Case Name Shopping Cart


Scope E-Grocery


24/26


Primary Actor Customer

Description It will allow customer to manage his/her own cart.

Stake Holders and

Interests

Customers- They will use it to manage their carts.

Pre-Conditions Customer has added items in his carts otherwise his carts should be

empty.

Post Conditions Add/remove of items from the cart and updating of cart.

Frequency of Occurrence Customers will use this feature whenever he/she wants to order

grocery.



Customer enters URL. Lands on the Home page of the website

Customer adds/removes grocery items

in his carts. He can shop more if they

want to, his carts will be updatedinstantly. Once he is done he can presscheck out button.

The responses which system would generate include:

add/remove of items from the cart and then update the

cart.

6. CheckoutUse Case ID UC-22 Use Case Name Checkout


Scope E-Grocery


Description It will allow customers to follow a series of steps for the

confirmation of their orders.Stake Holders and

Interests

Customers- They will use this to commit their orders.

Pre-Conditions Customer is logged in.

Post Conditions After validating all the information placement of order iscompleted.

Frequency of Occurrence Customer will use this feature whenever he/she wants to order

grocery.



Customer enters URL. Lands on the Home page of the websiteCustomer wishes to log-in to the

system.


Customer enters ID and Password. y Customer authentication is performed.y Customer is logged into the system.

Customer has to go through following

steps: 1) Delivery Information 2)Billing Information 3) Order Summary

4) placement of order.

Validation and verification of information which

customer has provided.


25/26


Exceptions

y Incorrect Username or Password/Information:o Error prompt will be shown asking to re-enter the desired information

y Un-registered Usero User will be asked to sign-up/register to the website.

7. Purchase HistoryUse Case ID UC-23 Use Case Name Purchase History

Date Created 4th


October 2011

Scope E-Grocery


Description It will allow customer to check his purchase history.

Stake Holders and

Interests

Customers- They will use this feature to check their purchasehistory.

Pre-Conditions Customer is logged in.

Post Conditions Customer views his purchase history

Frequency of Occurrence Customers will use this feature whenever he/she wants to viewhis/her purchase history.



Customer enters URL. Lands on the Home page of the website

Customer wishes to log-in to thesystem.


Customer enters ID and Password. y Customer authentication is performed.y Customer is logged into the system.Customer will click on purchase

history button to check his purchase

history.

In return the application will show the complete history

related to respective customer.

Exceptions

y Incorrect Username or Password:o Error prompt will be shown asking to re-enter the desired information


26/26


Revision History

Name Date Reason For Changes Version

Use Cases for Grocery Loots

Documents