USE CASES
Over-clocked Developers
Last Updated: December 8, 2012
Table of Contents
Use Cases: / Title: / Page:UC 1 / Create an Account / 4
UC 2 / Log In / 6
UC 3 / Log Out / 8
UC 4 / Recover Password / 10
UC 5 / View Purchase History / 13
UC 6 / View Account Profile / 15
UC 7 / Edit Account Profile / 17
UC 8 / View About Us / 19
UC 9 / Search For Products / 21
UC 10 / View Product Information / 23
UC 11 / Purchase a Product / 25
UC 12 / List a Product / 27
UC 13 / Update a Listed Product / 29
UC 14 / View Inventory Levels / 31
UC 15 / Track Sales / 33
UC 16 / Contact a Seller / 35
UC 17 / Login with Facebook / 37
UC 18 / View Wish List / 39
UC 19 / View BuyBox Estimated Price / 41
UC 20 / Review System / 43
UC 21 / Add Product to Wish List / 45
UC 22 / Cancel My Account / 47
UC 23 / Share Product on Facebook / 49
UC 24 / Generate QR Code / 51
Use Case Status Key
Priority:
0 / Completed1 / Highest Priority, Vital to application
2 / High Priority
3 / Implement if given time
Progress Status:
Planning / Use case is being planned.Designing / Use case is being designed with the team.
Developing / Use Case is being implemented with the team.
Testing / Use case is being tested with the team and potential outside sources.
Completed / Use case is fully implemented and functioning.
Deferred / Development of use case is on hold.
Use Case #1: “Create an Account”
Description:
The user shall be able to create a personal account by inputting a username, password.
Actors:
Buyers and Sellers
Desired Outcome
The system shall create a personal account and profile on the website for the user using the information provided during registration.
User Goals:
The user wants to create an account on the website.
Dependent Use Cases:
N/A
Involved Requirements:
SRS_01 – SRS_06
SRS_27
SRS_32
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
N/A
Post-conditions:
The system shall redirect the user to the homepage and send the user a verification email after registration is complete.
Trigger:
The user shall select the “Register” button on the home page.
Workflow:
1. The user shall open website.
2. The user shall select the “Sign In” link from the top of the home page.
3. The user shall select the “Sign Up Now !”.
3. The user shall be redirected to the account creation page.
4. The user shall enter first name, last name, password and password confirmation.
5. The user shall click the “Sign Up” button.
6. The system shall store the user’s account information in the website’s database.
Alternate Paths:
1. The user shall enter invalid user information, causing the system to redirect the
user back to step 4.
Options:
N/A
Use Case #2: “Log In”
Description:
The user shall be able to login to the website with register email and password. They shall also have the options to save his or her password and automatically login.
Actors:
Buyers and Sellers
Desired Outcome
The system shall log the user into his or her account.
User Goals:
The user wants to be able to log in to his or her account on the website to access his or her personal data. The user may also want to either purchase or sell a product.
Dependent Use Cases:
Use Case #1: “Account Creation”
Involved Requirements:
SRS_01 – SRS_06
SRS_27
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
The user shall have valid user credentials.
Post-conditions:
The system shall sign the user in.
The system shall redirect the user to the page that he or she was viewing before log in.
The system shall tailor the website to the user’s preferences.
Trigger:
The user shall select the “Log In” button at the top of any of the website’s pages.
Workflow:
1. The user shall open the website.
2. The user shall select the “Sign In” button at the top of the page.
3. The system shall redirect the user to the “Sign In” page.
4. The user shall enter his or her email and password.
5. The system shall access the user’s account information from the website’s
database.
6. The system shall tailor the website to the user’s preferences.
7. The system shall redirect the user to the page viewed before log in.
Alternate Paths:
1. The user shall enter invalid user credentials, causing the system to redirect the
user to the “Log In” page and to inform the user of the error.
2. The user shall select the “Remember Me” option, causing the system to store the
enteredemail and password to use during future session.
Options:
N/A
Use Case #3: “Log Out”
Description:
The user shall be able to log out of his or her account on the website, returning the user main page.
Actors:
Buyers and Sellers
Desired Outcome
The system shall clear the session and cookies,then log the user out of his or her account.
User Goals:
The user wants to be able to log out of his or her account.
Dependent Use Cases:
Use Case #1: “Account Creation”
Use Case #2: “Log In”
Involved Requirements:
SRS_01 – SRS_03
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
The user shall be logged in to his or her account.
Post-conditions:
The system shall sign the user out.
The system shall redirect the user to the main page.
Trigger:
The user shall select the “SignOut” button at the top of any of the website’s pages.
Workflow:
1. The user shall view the website.
2. The user shall select the “Sign Out” by clicking on their name on the top right.
3. The system shall clear the session and required cookies.
4. The system shall redirect the user to main page.
Alternate Paths:
N/A
Options:
N/A
Use Case #4: “Recover Password”
Description:
The user shall be able to recover forgotten password associated with his or her account.
Actors:
Buyers and Sellers
Desired Outcome
The system shall send the forgotten password to the email account associated with the user’s profile.
User Goals:
The user wants to be able to recover a forgotten password
Dependent Use Cases:
Use Case #1: “Account Creation”
Involved Requirements:
SRS_01
SRS_02
SRS_04 – SRS_06
Details:
- Priority Level: 2
- Status: Planning
Pre-conditions:
The user shall have valid user credentials.
Post-conditions:
The system shall send the user’s password and username to the email account associated with the user’s profile.
The system shall return the user to the “Sign In” page.
Trigger:
The user shall select the “Forgot Your Password?” button at the Sign In page.
Workflow:
1. The user shall view the website.
2. The user shall visit login page
3. The user shall select the “Forgot Your Password?” button on the page.
4. The system shall enter their email and click “Send me reset password instruction”.
5. The system shall send an email to the user with ways they can change their
password.
Alternate Paths:
1. The user shall enter invalid user information, causing the system to redirect the
user back to the “Password Recovery” page.
2. The user shall decide to cancel the password recovery process by clicking the
BuyBox logo on the top left.
Options:
N/A
Use Case #5: “View Purchase History”
Description:
This use case outlines the ability for the user to view date ordered, price, identification number, and payment information, associated with his or her previously purchased products.
Actors:
Buyers
Desired Outcome
The system shall display information about the user’s previously purchased products.
User Goals:
The user wants to be able to view information about his or her previously purchased products.
Dependent Use Cases:
Use Case #1: “Account Creation”
Use Case #2: “Log In”
Involved Requirements:
SRS_07
Details:
- Priority Level: 2
- Status: Planning
Pre-conditions:
The user shall be logged in to his or her account.
Post-conditions:
The system shall display a list of products the user previously purchased on the “Purchase History” page.
Trigger:
The user shall select the “Purchase History” button at the top of any of the website’s pages.
Workflow:
1. The user shall view the website.
2. The user shall select the “Purchases” button at the top of the page.
3. The system shall access information about the user previously purchased
products from the database.
4. The system shall display the “Purchase History” page with a list of products the
user previously purchased, including price, OrderID, category, product
information and seller name.
Alternate Paths:
N/A
Options:
N/A
Use Case #6: “View Account Profile”
Description:
This use case outlines the ability for the user to view the name, address, phone number, email address, and payment information, associated with his or her account.
Actors:
Buyers and Sellers
Desired Outcome
The system shall display the personal information associated with the user’s account.
User Goals:
The user wants to be able to view the personal information associated with his or her account.
Dependent Use Cases:
Use Case #1: “Account Creation”
Use Case #2: “Log In”
Involved Requirements:
SRS_08
SRS_09
SRS_26
SRS_27
SRS_30
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
The user shall be logged in to his or her account.
Post-conditions:
The system shall display the personal information associated with the user’s account on the “My Profile” page.
Trigger:
The user shall select the “ProfileSettings” by clicking on their name on the top right.
Workflow:
1. The user shall view the website.
2. The user shall select the “Profile Settings” by clicking on their name on the top
right.
3. The user shall select “Account Information” on the navigation bar.
4. The system shall access the user’s personal information from the website’s
database.
5. The system shall display the user’s personal information on the “Account
Information” page.
Alternate Paths:
N/A
Options:
N/A
Use Case #7: “Edit Account Profile”
Description:
This use case outlines the ability for the user to edit the name, address, phone number, email address, and payment information, associated with his or her account.
Actors:
Buyers and Sellers
Desired Outcome
The system shall upload the user’s edited personal information to the website’s database.
User Goals:
The user wants to be able to edit the personal information associated with his or her account.
Dependent Use Cases:
Use Case #1: “Account Creation”
Use Case #2: “Log In”
Involved Requirements:
SRS_08 – SRS_11
SRS_32
Details:
- Priority Level: 2
- Status: Planning
Pre-conditions:
The user shall be logged in to his or her account.
The user shall be on the “My Profile” page.
Post-conditions:
The system shall display the personal information associated with the user’s account on the “My Profile” page.
Trigger:
The user shall select the “Profile Setting” by click on their name on the top right.
Workflow:
1. The user shall view the “Account Settings” page.
2. The system shall allow the user to edit the personal information displayed on the
“Account Settings” page.
3. The user shall click the “Update your Profile” button on the “Account Settings”
page.
4. The system shall save the user’s modified personal information to the website’s
database.
5. The system shall display the user’s personal information on the
“Account Information” page.
Alternate Paths:
N/A
Options:
N/A
Use Case #8: “View About Us Page”
Description:
This use case outlines the ability for the user to view the website’s creation date and developers’ contact information and mission statement.
Actors:
Buyers and Sellers
Desired Outcome
The system shall display information about the website and its developers.
User Goals:
The user wants to be view information about the website and its developers.
Dependent Use Cases:
N/A
Involved Requirements:
SRS_12
SRS_13
Details:
- Priority Level: 2
- Status: Planning
Pre-conditions:
N/A
Post-conditions:
The system shall display information about the website and its developers on the “About Us” page.
Trigger:
The user shall select the “About Us” on the bottom of any of the website’s pages.
Workflow:
1. The user shall view the website.
2. The user shall select the “About Us” button.
3. The system shall display information about the website, about the team, FAQ,
Privacy Policy, Term of Use and Contact Us
Alternate Paths:
N/A
Options:
N/A
Use Case #9: “Search for Products”
Description:
This use case outlines the ability for the user to search for products on the website using a search bar.
Actors:
Buyers
Desired Outcome
The system shall display a list of products related to the terms the user entered into the search bar.
User Goals:
The user wants to be able to find products on the website using the search bar.
Dependent Use Cases:
N/A
Involved Requirements:
SRS_14
SRS_15
SRS_18
SRS_28
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
N/A
Post-conditions:
The system shall display a list of products related to the terms the user entered into the search bar.
Trigger:
The user shall click on Search at the top of any of the website’s pages.
Workflow:
1. The user shall view the website.
2. The user shall click on Search on top of the page.
3. The user shall type any term in the search box on the left navigation and select
the “Search” button.
4. The system shall search the website database for products related to the terms
the user entered into the search bar.
5. The system shall display a list of products related to the terms the user entered
into the search bar.
Alternate Paths:
N/A
Options:
N/A
Use Case #10: “View Product Information”
Description:
The user shall be able to view product name, price, description, picture and seller’s profile, associated with a selected product.
Actors:
Buyers
Desired Outcome
The system shall display a page containing information about the selected product.
User Goals:
The user shall be able to view information about a selected product.
Dependent Use Cases:
Use Case #9: “Search for Products”
Involved Requirements:
SRS_16 – SRS_18
SRS_26
SRS_28
SRS_30
SRS_33
SRS_34
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
The user shall have searched for an item using the search bar.
Post-conditions:
The system shall display a page containing information about the selected product.
Trigger:
The user shall select a product from the list of those related to the terms the user entered into the search bar.
Workflow:
1. The user shall view the list of products related to the terms the user entered into
the search bar.
2. The user shall select one of the listed products.
3. The system shall search the website database for information related to the
selected product
4. The system shall display information related to the selected product like name,
price, description, picture and seller’s profile.
Alternate Paths:
N/A
Options:
N/A
Use Case #11: “Purchase a Product”
Description:
The user shall be able to purchase a selected product.
Actors:
Buyers
Desired Outcome
The system shall add the user’s purchase to the website’s database and send a confirmation to the email address associated with the user’s profile.
User Goals:
The user shall be able to purchase a selected product.
Dependent Use Cases:
Use Case #1: “Account Creation”
Use Case #2: “Log In”
Use Case #9: “Search for Products”
Use Case #10: “View Product Information”
Involved Requirements:
SRS_11
SRS_16 – SRS_18
SRS_26
SRS_28
SRS_30
SRS_31
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
The user shall be logged in.
The user shall have viewed information about a product.
Post-conditions:
The system shall add the user’s purchase to the website’s database.
The system shall send a confirmation to the email address associated with the user’s profile.
Trigger:
The user shall select the “Buy” button on the product information page.
Workflow:
1. The user shall view the information about a product.
2. The user shall select the “Buy” button on the product information page.
3. The system shall ask the user for confirmation about buying the product.
4. If the user accepts, he or she will be redirected to the order confirmation page.
3. The system shall add the user’s purchase to the website’s database and update
the user’s purchase history and update the seller’s sold history.
Alternate Paths:
N/A
Options:
N/A
Use Case #12: “List a Product”
Description:
This use case outlines the ability for the user to list a product on the website and provide a price, picture, description, and inventory level, associated with that product.
Actors:
Sellers
Desired Outcome
The system shall add the user’s listed product to the website’s database.
User Goals:
The user wants to be able to list a product on the website.
Dependent Use Cases:
Use Case #1: “Account Creation”
Use Case #2: “Log In”
Involved Requirements:
SRS_19 – SRS_25
SRS_29
Details:
- Priority Level: 1
- Status: Planning
Pre-conditions:
The user shall be logged in.
The user shall be viewing his or her “My Listed Products” page.
Post-conditions:
The system shall add the listed product to the website’s database.
The system shall return the user to the “My Listed Products” page.
Trigger: