Use Cases For Grocery Loots

Use Cases for GroceryLoots
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
Contents
Use Cases for Admin Portal ..................................................................................................................... 5 1. Inventory Management................................................................................................................. 5 1.1. Inventory Catalogs .................................................................................................................... 5 2. Customers Management ............................................................................................................... 6 2.1. 2.2. 2.3. 2.4. 3. Customers ............................................................................................................................ 6 Customers Login .................................................................................................................. 7 Send Email to Customers ...................................................................................................... 8 Customer Contact Requests .................................................................................................. 9
Distributor Management ............................................................................................................. 10 3.1. 3.2. 3.3. 3.4. Distributors ........................................................................................................................ 10 Distributors Login .............................................................................................................. 11 Send Email to Distributors .................................................................................................. 12 Distributor Contact Requests .............................................................................................. 12
4.
Orders Management ................................................................................................................... 13 4.1. 4.2. Orders ................................................................................................................................ 14 Orders History .................................................................................................................... 14
5.
Revenue Management ................................................................................................................ 15 5.1. Revenue ............................................................................................................................. 15
Use Cases for Distributor Portal ............................................................................................................. 16 1. Shop Management...................................................................................................................... 16 1.1. 2. Shops ................................................................................................................................. 16
Orders Management ................................................................................................................... 18 2.1. 2.2. Orders ................................................................................................................................ 18 Orders History .................................................................................................................... 19
3.
Revenue Management ................................................................................................................ 19 3.1. Revenue ............................................................................................................................. 19
Use Cases for Customer View................................................................................................................ 20 1. 2. Sign-Up ..................................................................................................................................... 20 Login ......................................................................................................................................... 21
Use Cases for GroceryLoots 3. 4. 5. 6. 7.
Forgot Password......................................................................................................................... 22 Manage Personal Profile............................................................................................................. 22 Shopping Cart ............................................................................................................................ 23 Checkout .................................................................................................................................... 24 Purchase History ........................................................................................................................ 25
Use Case List
Primary Actor Administrator Administrator Administrator Administrator Administrator Administrator Administrator Administrator Administrator Administrator Administrator Administrator
Use Cases for Administrator Inventory Catalogs Customers Customers Login Send Email to Customers Customers Contact Requests Distributors Distributors Login Send Email to Distributors Distributors Contact Requests Orders Orders History Revenue
Primary Actor Distributor Distributor Distributor Distributor
Use Cases for Distributor Portal Shops Orders Orders History Revenue
Primary Actor Admin. Distributor and Customer Admin. Distributor and Customer Admin. Distributor and Customer Admin. Distributor and Customer
Use Cases for Customer/Administrator/Distributor View Sign-up Login Forgot Password Manage Personal Profile
Primary Actor Customer Customer Customer
Use Cases for Customer View Shopping Cart Checkout Purchase History
Use Cases for Admin Portal

1. Inventory Management
1.1. Inventory Catalogs
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions UC-1 Use Case Name Inventory Catalogs th 4 October 2011 Date Last Updated 4th October 2011 E-Grocery Administrator This feature will allow an administrator to manage inventory catalogs and grocery items. y Admin - Will be responsible to manage the inventory catalogs and grocery items. y Application should be 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. y Administrator has done with add, update, delete, rename or search of grocery catalogs and/or its items. This feature will be used whenever the administrator needs to manage inventory catalogs and/or grocery items.
Post Conditions Frequency of Occurrence Main Success Scenario
Actors Action Administrator enters URL of our website. Administrator wishes to log-in to the system. Administrator enters his username and password. Administrator wishes to manage inventory catalogs and/or grocery items. Administrator wishes to perform certain actions like add, edit/update, delete, rename, search of catalogs and/or grocery items.
Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system. Inventory Catalog page will be shown to the Administrator. 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 grocery items. y Categorizing grocery items into their respective catalogs. y Providing the search results for grocery items. Request is processed and all the views are updated.
Administrator submits the changes request.
Use Cases for GroceryLoots Exceptions y y
Incorrect Password o Error prompt will be shown asking to re-enter the login information. Database sync problem o 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 Management
2.1.Customers
Use Case ID Date Created Scope Primary Actor Description UC-2 5th October 2011 E-Grocery Administrator 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 password and to active/inactive any customer. Admin: Allows managing existing customers. Application should be properly sync with database. Proper information 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. Admin will be able to manage customers i.e. he can view active/inactive customers, make changes or delete/inactive any existing customer, and export the report in CSV format. This feature will be used whenever the admin wants to review the details of customers, make changes to the customers profile and to active/inactive any customer. y Use Case Name Date Last Updated Customers 5th October 2011
Stake Holders and Interests Pre-Conditions
Post Conditions
Frequency of Occurrence
Main Success Scenario Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. Administrator wishes to manage the customers and then he clicks on customers tab. Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system Customers Management page will be shown to the Administrator, with the list of existing customers.
Use Cases for GroceryLoots Administrator will select a Customer to be managed. Administrator wishes to add/edit/delete/change password/active or inactive a particular customer and his details. Administrator exports the list of customers in CSV format. Exceptions y y Customer details will be shown to the Administrator. System retrieves customers information. Update in database when administrator will perform actions like add, edit, delete, change password and active/inactive any customer. Downloading window will be shown. y y
2.2.Customers Login
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions UC-3 5th October 2011 E-Grocery Administrator This feature will provide details about how many customers are currently logged in. Admin can estimate how many customers are currently logged in and using our website. y The customer has already registered on our website and he/she is currently 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. y It will display the details of those customers which are currently logged in. This feature will be used whenever an admin wants to view the number of customers currently logged in and using the website. Use Case Name Date Last Updated Customers Login 5th October 2011
Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. Administrator will click on customer login tab to check how many
Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system System will provide the output by listing all the customers which are currently logged in.
Use Cases for GroceryLoots customers are currently logged in and using our website. Exceptions y y
2.3.Send Email to Customers

Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions UC-4 5th October 2011 E-Grocery Administrator This feature will allow an administrator to send an email to customer(s) regarding any update, promotion/deals etc. Admin will let the customers know about any update/promotion/deals by using this feature. y SMTP and POP are active and running. y User must be an administrator. y Administrator needs to login into the system. y Customer(s) receives an email. This feature will be used whenever an admin wants to send an email to customer(s) regarding any update, promotion/deals etc. Use Case Name Date Last Updated Send Email to Customers 5th October 2011
Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. The administrator will click on send email to customer button where first he will select an option from bulk mail options and then he will write a message and finally he will click on send button. Exceptions y
Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system. After pressing the send button our customer(s) will receive an email.
Incorrect Password o Error prompt will be shown asking to re-enter the login information.
Use Cases for GroceryLoots Problem in SMTP and POP o 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 Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions UC-5 5th October 2011 E-Grocery Administrator This feature will allow an administrator to check and reply to the messages and queries which are sent by the customers. Admin will use this features so he can interact with them and to entertain their queries. 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. y Prompt reply to the customers queries. This feature will be used whenever an admin needs to check and reply to the messages and queries which are sent by the customers. Use Case Name Date Last Updated Customer Contact Requests 5th October 2011
Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. The administrator will click on customer contact requests button to check all the messages and queries which are received from customers and the actions which he would take include 1) Reply to those messages 2) Delete those messages.
Systems Response Lands on the Home page of the website Login page is shown. y y y y y Administrator authentication is performed. Administrator is logged into the system. Shows all the messages. Delete the messages. Send reply message to the customers.
Exceptions y y Incorrect Password o Error prompt will be shown asking to re-enter the login information. Database sync problem o Proper exception handling will be done and errors will be shown to the Admin so he can rectify them as soon as possible. Problem in SMTP and POP
Use Cases for GroceryLoots In case if misconfigurations in SMTP and POP cause any problem so configuration management will be done by an admin.
10
3. Distributor Management
3.1.Distributors
Use Case ID Date Created Scope Primary Actor Description UC-6 5th October 2011 E-Grocery Administrator This feature allows an administrator to manage distributors in a way that he can retrieve information about our distributors and he can take certain actions including editing of distributors information, change password and to active/inactive any distributor. Admin: Allows managing existing distributors. y Application should be properly sync with database. Proper information 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 functionality should be there. y User must be an Administrator. y Administrator needs to login into the system. Admin will be able to manage distributors i.e. he can view active/inactive distributors, make changes or delete any existing distributor, export the report in CSV format. This feature will be used whenever the admin wants to review the details of distributors, make changes to the distributors profile and to active/inactive any distributor. Use Case Name Date Last Updated Distributors 5th October 2011
Post Conditions
Main Success Scenario Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. Administrator wishes to manage the distributors and click on distributors tab. Administrator will select a distributor to be managed. Administrator wishes to add/edit/delete/change password/active or inactive a particular distributor and his details. Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system. Distributors Management page will be shown to the Administrator, with the list of existing distributors. Distributors details will be shown to the Administrator. y System retrieves distributors information. y Update in database when administrator will perform actions like add, edit, delete, change password and
Use Cases for GroceryLoots active/inactive any distributor. Downloading window will be shown.
11
Administrator exports the list of distributors in CSV format. Exceptions y y
3.2.Distributors Login
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions UC-7 5th October 2011 E-Grocery Administrator This feature would provide details about how many distributors are currently logged in. Admin can estimate how many distributors are currently logged in and using our website. y The distributor has already registered on our website and he is currently 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. y It will display the details of those distributors which are currently logged in. This feature will be used whenever an admin wants to view the number of distributors currently logged in and using the website. Use Case Name Date Last Updated Distributors Login 5th October 2011
Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. Administrator will click on distributors login tab to check how many distributors are currently logged in and using our website. Exceptions y Incorrect Password
Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system System will provide the output by listing all the distributors which are currently logged in.
12
o Error prompt will be shown asking to re-enter the login information. Database sync problem o Proper exception handling will be done and errors will be shown to the Admin so he can rectify them as soon as possible.
3.3.Send Email to Distributors

Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions UC-8 5th October 2011 E-Grocery Administrator This feature will allow an administrator to send an email to distributor(s) regarding any update. Admin will let the distributors know about any update by using this feature. y SMTP and POP are active and running. y User must be an administrator. y Administrator needs to login into the system. y Distributor(s) receives an email. This feature will be used whenever an admin wants to send an email to distributor(s) regarding any update etc. Use Case Name Date Last Updated Send Email to Distributors 5th October 2011
Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. The administrator will click on send email to distributors button where first he will select an option from bulk mail options and then he will write a message and finally he will click on send button. Exceptions y y
Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system. After pressing the send button our distributor(s) will receive an email.
Incorrect Password o Error prompt will be shown asking to re-enter the login information. Problem in SMTP and POP o 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
Use Cases for GroceryLoots Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions UC-9 5th October 2011 E-Grocery Administrator This feature will allow an administrator to check and reply to the messages and queries which are sent by the distributors. Admin will use this features so he can interact with them and to entertain their queries. 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. y Prompt reply to the distributors queries. This feature will be used whenever an admin needs to check and reply to the messages and queries which are sent by the distributors. Use Case Name Date Last Updated Distributor Contact Requests 5th October 2011
13
Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. The administrator will click on distributor contact requests button to check all the messages and queries which are received from distributors and the actions which he would take include 1) Reply to those messages 2) Delete those messages.
Systems Response Lands on the Home page of the website Login page is shown. y y y y y Administrator authentication is performed. Administrator is logged into the system. Shows all the messages. Delete the messages. Send reply message to the distributors.
Exceptions y y Incorrect Password o Error prompt will be shown asking to re-enter the login information. Database sync problem o Proper exception handling will be done and errors will be shown to the Admin so he can rectify them as soon as possible. Problem in SMTP and POP o In case if misconfigurations in SMTP and POP cause any problem so configuration management will be done by an admin.
4. Orders Management
14
4.1.Orders
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions Post Conditions Frequency of Occurrence Main Success Scenario Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. The administrator will click on the orders tab to keep track of daily orders and their respective customers. In case if any unwanted situation occur administrator can choose cancel and refund option. Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is logged into the system. Order management interface is shown. UC-10 Use Case Name Orders 5th October 2011 Date Last Updated 5th October 2011 E-Grocery Administrator This feature allows an administrator to keep track of customers orders. y Admin- Admin can view all the orders and keep track of them. y Administrator needs to be logged-in to the system. y Customer has already placed an order. Order details will be shown to the Administrator like order is delivered, in a queue or cancelled/money refunded. This process will be used whenever an administrator wants to view the order and its status or wants to cancel any order.
Order is cancelled and the money is refunded.
Exceptions y y Incorrect Password o Error prompt will be shown asking to re-enter the login information. Database sync problem o Proper exception handling will be done and errors will be shown to the Admin so he can rectify them as soon as possible.
4.2.Orders History
Use Case ID Date Created Scope UC-11 5th October 2011 E-Grocery Use Case Name Date Last Updated Orders History 5th October 2011
Use Cases for GroceryLoots Primary Actor Description Administrator This feature allows an administrator to keep track of the orders which have been placed on the website so far. y Admin- Admin can view all the history of the orders which have been placed so far. y Proper maintenance of orders log. Searching option is there on the website. y Administrator needs to be logged-in to the system. y It will show the complete list of orders which have been placed so far by the customer(s). This process will be used whenever an administrator wants to view the order history.
15
Post Conditions
Frequency of Occurrence Main Success Scenario
Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters his username and Password. An administrator will click on orders history tab to check the orders history i.e. the orders which have been placed so far. An administrator can also search the orders history of a specific customer. Exceptions y y
Systems Response Lands on the Home page of the website Login page is shown. y Administrator authentication is performed. y Administrator is Logged into the system y Order management interface is shown. y Show the complete list of orders which have been placed so far by the customer(s).
5. Revenue Management
5.1.Revenue
Use Case ID Date Created Scope Primary Actor Description UC-12 Use Case Name 4th October 2011 Date Last Updated E-Grocery Administrator To calculate and view earned revenues. Revenue 4th October 2011
Use Cases for GroceryLoots Stake Holders and Interests Pre-Conditions Post Conditions Frequency of Occurrence Administrator Will be able to calculate overall business revenues. Administrator needs to be logged-in to the system. Earned revenues table will be shown to the Administrator. This process will be used whenever Administrator wants to view or calculate the earned profits/revenues. y
16
Main Success Scenario Actors Action Administrator enters URL. Administrator wishes to log-in to the system. Administrator enters ID and Password. Systems Response Lands on the Home page of the website Login page is shown. y y Administrator authentication is performed. Administrator is Logged into the system
Administrator wishes to view revenues earned. Administrator wishes to calculate revenues.
Revenue management interface is shown. System will provide the following calculating options; Day Week Month Year Overall
Exceptions y y Incorrect Password o Error prompt will be shown asking to re-enter the login information. Database sync problem o Proper exception handling will be done and errors will be shown to the Admin so he can rectify them as soon as possible.
Use Cases for Distributor Portal

1. Shop Management
1.1. Shops
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests UC-13 Use Case Name Shops 4th October 2011 Date Last Updated 4th October 2011 E-Grocery Distributor This feature will allow Distributor to manage shop, i.e. their profiles and details. Distributor- Allows managing existing shops as well as adding new shops.
Use Cases for GroceryLoots Pre-Conditions Post Conditions Frequency of Occurrence Main Success Scenario Actors Action Distributor enters URL. Distributor wishes to log-in to the system. Distributor enters ID and Password. Distributor wishes to manage the Shops. Distributor will select a shop to be managed. Distributor wishes to edit a particular shop details. Systems Response Lands on the Home page of the website Login page is shown. y Distributor authentication is performed. y Distributor is logged into the system Shop Management page will be shown to the distributor, with the list of existing shops under that distributor. Shop details will be shown to the distributor. Distributor will be given multiple options to manage a particular shop. Which includes; y Shops under the distributor y Managing a Shop Profile y Add a shop to the list y Deleting a shop. Changes will be saved along with the updating of database and all the views. y User must be distributor. y Distributor needs to login into the system. Distributor will be able to manage shops under him. Whenever the distributor wants to view the list of shops or update the list, this feature will be used.
17
Distributor makes changes through the interface. Exceptions y
Incorrect Password o Error prompt will be shown asking to re-enter the login information
Extensions y Editing Shop Details o 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. Deleting a particular Shop o In order to delete a Shop, Distributor will select a particular shop and select the delete option. o The database will be updated and the particular shop will be deleted along with the updating of all the views. Confirmation message will be shown on screen. Adding a Shop o 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
2. Orders Management
2.1. Orders
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions Post Conditions Frequency of Occurrence Main Success Scenario Actors Action Distributor enters URL. Distributor wishes to log-in to the system. Distributor enters ID and Password. Systems Response Lands on the Home page of the website Login page is shown. y Distributor authentication is performed. y Distributor is Logged into the system Order management interface is shown. System will provide the following options to the Distributor; y View Orders y Update Order Status UC-14 Use Case Name Orders 5th October 2011 Date Last Updated 5th October 2011 E-Grocery Distributor To view the orders and update its status. y Distributor- Each distributor will be able to view his orders and update their status. y Distributor needs to be logged-in to the system. y Order details will be shown to the Distributor. This process will be used whenever Distributor wants to view the orders or update the order status.
Distributor wishes to view the orders. Distributor wishes to update the order status.
Exceptions y Incorrect Password o Error prompt will be shown asking to re-enter the login information.
Extensions y Update order Status o Only distributor can update the status of order, i.e. from pending to delivered. o Once the status is updated, Admin's and Customers view is also updated along with updating of database. View Orders o 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
2.2.Orders History
Use Case ID Date Created Scope Primary Actor Description UC-15 Use Case Name Orders History 5th October 2011 Date Last Updated 5th October 2011 E-Grocery Distributor This feature allows distributor to keep track of the orders which have been assigned to him so far. Distributor - Distributor can view all the history of the orders which have been assigned to him so far. y Proper maintenance of orders log. Searching option is there on the website. y Distributor needs to be logged-in to the system. It will show the complete list of orders which have been assigned to him so far. This process will be used whenever Distributor wants to view his order history.
Actors Action Distributor enters URL. Distributor wishes to log-in to the system. Distributor enters his username and Password. Distributor will click on orders history tab to check the orders history i.e. the orders which have been assigned to him so far. Distributor can also search the orders history for a specific date. Exceptions y
Systems Response Lands on the Home page of the website Login page is shown. y Distributor authentication is performed. y Distributor is Logged into the system y Order management interface is shown. y Show the complete list of orders which have been assigned so far to him.
Incorrect Password o Error prompt will be shown asking to re-enter the login information.
3. Revenue Management
3.1. Revenue
Use Case ID Date Created Scope Primary Actor Description UC-16 Use Case Name 4th October 2011 Date Last Updated E-Grocery Distributor To calculate and view earned revenues. Revenue 4th October 2011
Use Cases for GroceryLoots Stake Holders and Interests Pre-Conditions Post Conditions Frequency of Occurrence Main Success Scenario Actors Action Distributor enters URL. Distributor wishes to log-in to the system. Distributor enters ID and Password. Systems Response Lands on the Home page of the website Login page is shown. y y Distributor authentication is performed. Distributor is Logged into the system Distributor- Each distributor will be able to view his earned profits.
20
Distributor needs to be logged-in to the system. Earned revenues table will be shown to the Distributor. This process will be used whenever Distributor wants to view the earned profits/revenues.
Distributor wishes to view revenues earned. Distributor wishes to calculate revenues.
Revenue management interface is shown. System will provide the following calculating options; Day. Week. Month. Year. Overall.
Exceptions y Incorrect Password o Error prompt will be shown asking to re-enter the login information.
Use Cases for Customer View

1. Sign-Up
Use Case ID Date Created Scope Primary Actor UC-17 4th October 2011 E-Grocery Use Case Name Date Created Sign-Up 4th October 2011
Description Stake Holders and Interests Pre-Conditions
User(Customer) Distributor Administrator It will allow users to become the member of the website. User- He will be able to commit and manage his purchases. y Access to the internet y User has filled the registration form properly and all the information he has provided is valid.
21
Upon logging in, registered users can perform desired operations. First time user will use this feature in order to get complete access.
Actors Action User enters URL. User wishes to register. User clicks on sign-up button and enters desired details which includes username, password, address etc. Exceptions y
Systems Response Lands on the Home page of the website Registration page is shown. y Availability is checked. y Proper Validation and Verification of the fields. y User is registered onto the website.
Incomplete/Incorrect Details o In case of incomplete/incorrect information customer will be prompted to re-enter the information. Unavailable/Occupied ID o Customer will be asked to choose a different ID.
2. Login
Use Case ID Date Created Scope Primary Actor UC-18 4th October 2011 E-Grocery Use Case Name Date Last Updated Login 4th October 2011
Description Stake Holders and Interests
Pre-Conditions Post Conditions Frequency of Occurrence
Administrator Customer Distributor It deals with the detailed login procedure of GroceryLoots. Administrator He 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. Provision of valid and authenticated ID and Password along with the access to internet. Upon logging in, user can perform desired operations. In order to access the core features user always needs to be logged into the Website.
Main Success Scenario Actors Action User enters URL. User wishes to log into the system. User enters ID and Password Systems Response Lands on the Home page of the website Login page is shown. y User authentication is performed. y User is Logged into the system
Use Cases for GroceryLoots Exceptions y y Incorrect Password o Error prompt will be shown asking to re-enter the login information Un-registered User o User will be asked to sign-up/register to the website
22
3. Forgot Password
Use Case ID Date Created Scope Primary Actor UC-19 4th October 2011 E-Grocery Use Case Name Date Last Updated Login 4th October 2011
Description Stake Holders and Interests Pre-Conditions Post Conditions
Administrator Customer Distributor It will allow a user to reset his/her password. User will reset their passwords from this feature. User is already registered on our website. User will receive an email which would allow him/her to reset his/her password. User will use this feature when he forgets his password and want to reset it.
Main Success Scenario Actors Action User enters URL. User clicks on forgot password button where he enters his email address and username and then he submits the request. Exceptions y y Incorrect Email ID or Username o Error prompt will be shown asking to re-enter the desired information Un-registered User o User will be asked to sign-up/register to the website. Systems Response Lands on the Home page of the website User receives an email which would allow him/her to reset his/her password.
4. Manage Personal Profile

Use Case ID Date Created Scope Primary Actor UC-20 4th October 2011 E-Grocery Administrator Use Case Name Date Created Manage Personal Profile 4th October 2011
Use Cases for GroceryLoots Customer Distributor Actors will be able to manage their personal profile. Admin/Customer/Distributor- Can manage their personal profiles i.e. Update or View profile. User should be logged-in to the system. User will be able to manage the profile. This operation will be used whenever the user wishes to edit/update his personal profile.
23
Description Stakeholders and Interests Pre-Conditions Post Conditions Frequency of Occurrence
Main Success Scenario Actors Action User enters URL. User wishes to log-in to the system. User enters ID and Password. User wishes to manage the profile. User wishes to edit/update the profile. Systems Response Lands on the Home page of the website Login page is shown. y User authentication is performed. y User is Logged into the system Profile will be shown to the user. System will provide the following options; y Editing/Updating Information. y Deactivate the profile.
Exceptions y Incorrect Password o Error prompt will be shown asking to re-enter the login information
Extensions y If user wants to edit his personal details o 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. Deactivating Account o 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 to deactivate.
5. Shopping Cart
Use Case ID Date Created Scope UC-21 4th October 2011 E-Grocery Use Case Name Date Last Updated Shopping Cart 4th October 2011
Use Cases for GroceryLoots Primary Actor Description Stake Holders and Interests Pre-Conditions Customer It will allow customer to manage his/her own cart. Customers- They will use it to manage their carts. Customer has added items in his carts otherwise his carts should be empty. Add/remove of items from the cart and updating of cart. Customers will use this feature whenever he/she wants to order grocery.
24
Post Conditions Frequency of Occurrence
Main Success Scenario Actors Action Customer enters URL. Customer adds/removes grocery items in his carts. He can shop more if they want to, his carts will be updated instantly. Once he is done he can press check out button. Systems Response Lands on the Home page of the website The responses which system would generate include: add/remove of items from the cart and then update the cart.
6. Checkout
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions Post Conditions Frequency of Occurrence UC-22 4th October 2011 E-Grocery Use Case Name Date Last Updated Checkout 4th October 2011
Customer It will allow customers to follow a series of steps for the confirmation of their orders. Customers- They will use this to commit their orders. Customer is logged in. After validating all the information placement of order is completed. Customer will use this feature whenever he/she wants to order grocery.
Main Success Scenario Actors Action Customer enters URL. Customer wishes to log-in to the system. Customer enters ID and Password. Customer has to go through following steps: 1) Delivery Information 2) Billing Information 3) Order Summary 4) placement of order. Systems Response Lands on the Home page of the website Login page is shown. y Customer authentication is performed. y Customer is logged into the system. Validation and verification of information which customer has provided.
Use Cases for GroceryLoots Exceptions y y Incorrect Username or Password/Information: o Error prompt will be shown asking to re-enter the desired information Un-registered User o User will be asked to sign-up/register to the website.
25
7. Purchase History
Use Case ID Date Created Scope Primary Actor Description Stake Holders and Interests Pre-Conditions Post Conditions Frequency of Occurrence UC-23 4th October 2011 E-Grocery Use Case Name Date Last Updated Purchase History 4th October 2011
Customer It will allow customer to check his purchase history. Customers- They will use this feature to check their purchase history. Customer is logged in. Customer views his purchase history Customers will use this feature whenever he/she wants to view his/her purchase history.
Main Success Scenario Actors Action Customer enters URL. Customer wishes to log-in to the system. Customer enters ID and Password. Customer will click on purchase history button to check his purchase history. Exceptions y Incorrect Username or Password: o Error prompt will be shown asking to re-enter the desired information Systems Response Lands on the Home page of the website Login page is shown. y Customer authentication is performed. y Customer is logged into the system. In return the application will show the complete history related to respective customer.
26
Revision History
Name
Date
Reason For Changes
Version

Use Cases For Grocery Loots

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Use Cases For Grocery Loots

Uploaded by

Copyright:

Available Formats

Use Cases for GroceryLoots

October 11, 2011