Vous êtes sur la page 1sur 6

Use Cases

Online Order Application


Version 1.0

Prepared by Pranay Dharamshi

11/02/2017
Use Case for Online Ordering Application Page 1

Use Case List

Primary Actor Use Cases


User 1
User 2
Use Case for Online Ordering Application Page 2

Use Case - 1
Use Case ID: UC-001
Use Case Name: Registered User login functionality
Created By: Pranay Dharamshi Last Updated By: Pranay Dharamshi
Date Created: 11/02/2017 Date Last Updated: 11/02/2017

Actors: Registered Users

Description: This use case will capture the information and the interaction
between registered user and Online Ordering Application for Login
functionality

Trigger: User needing to order food online

Pre-conditions: 1. Online Ordering Application must be up and running


2. User must be a registered user
3. User account must be active

Post conditions: 1. User shall be directed to Pizza order page upon successful login
2. User shall be exited out of the App upon unsuccessful login

Normal Flow: 1. User shall open Online Ordering Application on a


laptop/smartphone/tablet
2. User shall enter valid user id
3. User shall enter valid password
4. Online Ordering Application shall authenticate valid user id and
password
5. User is directed into the Online Ordering Application

Alternative Flows: Scenario 1 (Invalid User Id):


1. User shall open Application
2. User shall enter invalid username
3. User shall enter valid password
4. Application shall authenticate invalid user id and valid
password
5. Application shall display the following error: “The user id
or password you entered is incorrect.”

Scenario 2 (Invalid Password):


1. User shall open Application
2. User shall enter valid username
3. User shall enter invalid password
4. Application shall authenticate valid user id and invalid
password
5. Application shall display the following error: “The user id
or password you entered is incorrect.”

Scenario 3 (Invalid User id and invalid Password):


Use Case for Online Ordering Application Page 3

1. User shall open Application


2. User shall enter invalid username
3. User shall enter invalid password
4. Application shall authenticate invalid user id and invalid
password
5. Application shall display the following error: “The user id
and password you entered is incorrect.”

Scenario 4 (Invalid User id up to 6 times):


1. User shall open Application
2. User shall enter invalid user id for 6 times
3. User shall enter invalid password
4. Application shall authenticate invalid user id and valid
password
5. Application shall generate a security code and display it

Scenario 7 (Forgot user id):


1. User shall open Application
2. User shall click “Forgot user id?”
3. Application shall prompt to enter email id associated with
the account
4. Application shall send an email
5. Email shall prompt the user to choose a new user id.

Scenario 8 (Forgot password):


1. User shall open Application
2. User shall click “Forgot password?”
3. Application shall prompt Security Question
4. User shall enter Security answer
5. App shall validate the response
6. App shall prompt the user to choose a new password.

Exceptions: Scenario 1 (Invalid user id up to 12 times):


1. User shall open Application
2. User shall enter invalid user id for 12 times
3. User shall enter valid password
4. Application shall authenticate invalid user id and valid
password
5. App shall display the following error: “We do not
recognize your username. Please try again after 24
hours.”

Scenario 2 (Invalid password up to 12 times):


1. User shall open Application
2. User shall enter valid user id
3. User shall enter invalid password for 12 times
4. Application shall authenticate valid user id and invalid
password
5. App shall display the following error: “We do not
recognize your password. Please try again after 24
Use Case for Online Ordering Application Page 4

hours.”
Includes: None
Priority: High
Frequency of Use: High (every time the registered user wants to Order Online with the
help of application they should successfully login into their account)
Business Rules: 1. The user account should be locked after 12 failed attempts
2. The user account should be locked for 24 hours
Special Requirements: None
Assumptions: None
Notes and Issues: None

Use Case - 2
Use Case ID: UC-002
Use Case Name: Online Ordering Application Functionality
Created By: Pranay Dharamshi Last Updated By: Pranay Dharamshi
Date Created: 11/02/2017 Date Last Updated: 11/02/2017

Actors: Registered User


Description: This use case will capture the information and the interaction
between registered user and Online Ordering Application for food
ordering functionality
Trigger: User needs to order food
Pre-conditions: 1. Online Ordering Application must be up and running
2. User account must be active
Post conditions: 1. User shall be directed to payment page after confirming and
placing order
Normal Flow: 1. User shall open Online Ordering Application on a
laptop/smartphone/tablet
2. User shall Login to account
3. User shall choose service type (Delivery or Pick up)
4. User shall choose items from menu
5. User shall review and confirm order
6. User shall place the order
7. User shall be directed to the payment page
Use Case for Online Ordering Application Page 5

Alternative Flows: Scenario 1 (User orders from already defined menu):


1. User shall open Online Ordering Application on a
laptop/smartphone/tablet
2. User shall Login to account
3. User shall choose Delivery or Pick up
4. User shall choose order from previously saved orders
5. User shall review and confirm order
6. User shall place order
7. User shall be directed to the payment page
Scenario 2 (User creates own combinations):
1. User shall open Online Ordering Application on a
laptop/smartphone/tablet
2. User shall Login to account
3. User shall choose Delivery or Pick up
4. User shall choose “Build own order” option
5. User shall review and confirm order
6. User shall place order
7. User shall be directed to the payment page
Exceptions: Scenario 1 (Delivery Order is less than $30):
1. User shall open Online Ordering Application on a
laptop/smartphone/tablet
2. User shall Login to account
3. User shall choose Delivery
4. User shall choose items
5. User shall review and confirm order
6. User shall place order
7. App shall display the following error: “Error: Minimum
Amount for Delivery is $30”
Includes: Login Functionality
Priority: High
Frequency of Use: High (every time the user wants to order online food)
Business Rules: 1. Minimum Order $30 for Delivery
Special Requirements: None
Assumptions: None
Notes and Issues: None

Revision History

Name Date Reason For Changes Version