User Stories

This Wiki includes information on user stories for the e-commerce website.

~ Admin User Stories

A1 - Approving/Blocking User Accounts: As an admin, I want to be able to approve/block user accounts, so that I can remove unwanted users from the site.

Task Breakdown:

1. Admin requests to review a user.
2. Request data of user to review.
3. If user data is valid, navigate the admin to the user's information page. Otherwise, display an error to the admin and prompt the admin to either change the provided information or abort.
4. Admin requests to block user.
5. If action is successful, display success to the admin. Otherwise, display an error to the admin.

Acceptance Testing:

1. User registers as a seller.
2. User awaits approval from admin.
3. User can begin selling.

A2 - Approving/Removing Products: As an admin, I want to be able to approve/remove a seller's products, so that I can remove unwanted products from the site.

Task Breakdown:

1. Admin requests to review a seller catalogue.
2. Request data of seller catalogue to review.
3. If seller catalogue data is valid, navigate the admin to the user's information page. Otherwise, display an error to the admin and prompt the admin to either change the provided information or abort.
4. Admin requests to remove item from catalogue.
5. If item is valid (exists), remove the item from the catalogue and display success to the admin. Otherwise, display an error to the admin.

Acceptance Testing:

1. User posts and item for sale as a seller.
2. User awaits approval of said item.
3. User can begin selling that item if approved.

A3 - Overseeing User Actions: As an admin, I want to oversee user actions (such as checking out), so that I can know when a user is committing an unwanted action.

Task Breakdown:

1. Admin requests to review a user.
2. Request data of user to review.
3. If user data is valid, navigate the admin to the user's information page. Otherwise, display an error to the admin and prompt the admin to either change the provided information or abort.
4. Admin requests to view user activity.
5. If action is successful, display the user's activity to the admin. Otherwise, display an error to the admin.

Acceptance Testing:

1. User uses the site as normal and accomplishes different tasks.
2. If a user commits a forbidden task, an admin can override that action.

~ Customer User Stories

B1 - Account Creation: As a customer, I want to create an account, so that I can use the site.

Task Breakdown:

1. Prompt the user to fill in data for a new account.
2. If the data is both valid AND not already present in the database, create the account (populate database with new information).
3. Display success to the user and prompt them to log in.

Acceptance Testing:

1. The user opts to create an account.
2. The user fills out the necessary information.
3. If any information is invalid or left blank, the user is asked to fix it.
4. If all information is valid, the user may become a customer/seller.

B2 - Log-in/Log-out: As a customer, I want to be able to log-out and log-in of the site, so that I am not always logged in.

Task Breakdown:

1. Prompt the user for their information (account name and password).
2. If the data is a valid pair, then allow the user to continue to the site.

Acceptance Testing:

1. The user enters their information into the login fields.
2. If any information is invalid, the user is asked to reenter the correct information.
3. If the user does not exist, the user is asked to register a new account.
4. When the user successfully logs in, they may log out any time they like.

B3 - Shopping Cart: As a customer, I want to add items to my shopping cart, so that I can review what I am ordering and checkout.

Task Breakdown:

1. User requests to access cart.
2. User requests to add an item.
3. Request the item identifier.
4. If the item identifier is valid, add the item to the cart. Otherwise, display an error to the user and request that the user enter a new value or abort.

Acceptance Testing:

1. User browses the store and adds chosen items to cart.
2. User navigates to cart and reviews order.
3. User completes the order and checks out.

B4 - 'Save for Later:' As a customer, I want to be able to save items for later, so that I can easily see which items I want without having those items in my shopping cart.

Task Breakdown:

1. User requests to view items.
2. Return the item catalogues from the product database.
3. User requests to view an item.
4. If the item exists, return the item data. Otherwise, display an error to the user.
5. User requests to save the item.
6. If the action processes successfully, display success to the user. Otherwise, display an error to the user.

Acceptance Testing:

1. User navigates to cart.
2. User decides to not purchase an item.
3. If applicable, user may select item to save for later, rather than deleting.

B5 - Editing User Information: As a customer, I want to edit my user information, so that I can change my username and password.

Task Breakdown:

1. User requests to edit account information.
2. Request new information.
3. If new information is valid, is different than the old information, and does not already exist in the database, display success to the user. Otherwise, display an error explaining the reason the action failed (invalid, no change, or duplicate) to the user.

Acceptance Testing:

1. User navigates to profile.
2. User selects field of information to edit.
3. User edits the information.
4. If any information is invalid or blank. the user is asked to reenter the information.
5. Information is then edited.

~ Seller User Stories

C1 - Posting/Removing Products: As a seller, I want to be able to post/remove products to/from my page.

Task Breakdown:

1. User requests to edit their catalogue.
2. Return user catalogue data.
3. User adds a new item.
4. If the new item is valid (valid information and all necessary fields filled), display success to the user and add the item to their catalogue. Otherwise, display an error to the user and return them to the add item page, with a message stating what data needs to be fixed/added.
5. User removes an item.
6. If the item is valid (exists), display success to the user and remove the item from their catalogue. Otherwise, display an error to the user and return them to the remove item page, with a message stating what data needs to be fixed/added.

Acceptance Testing:

1. Seller has item they wish to add.
2. Seller navigates to their store to add product.
3. Seller enters necessary information into fields.
4. If any information is invalid/blank, the seller is asked to reenter the information.
5. The item is posted to the store.
6. If seller has item they wish to remove, they can navigate to their store and remove it.

C2 - Receiving Payments: As a seller, I want to be able to receive payments for my products from customers.

Task Breakdown:

1. Customer purchases items in shopping cart.
2. Customer provides payment information.
3. Transaction information and payment information is passed to the seller database.
4. The payment for the transaction is processed.
5. Funds are transferred to the seller.

Acceptance Testing:

1. Seller awaits purchase.
2. Upon purchase, seller is notified and payment is processed to seller's account.
3. Seller may withdraw from balance at any time.

C3 - Setting Prices: As a seller, I want to be able to set and edit the prices for my prices.

Task Breakdown:

1. User requests to edit their catalogue.
2. Return user catalogue data.
3. User chooses to edit a catalogue item.
4. If the item exists, take the user to the item's page. Otherwise, display an error to the user.
5. User edits item price.
6. If action is successful, display success to the user. Otherwise, display an error to the user.

Acceptance Testing:

1. Seller navigates to their store and views products.
2. Seller selects item they wish to edit price on.
3. Seller edits price field.
4. If price is invalid number or blank, seller is asked to reenter information.
5. Item is edited and updated to store.

C4 - Setting Stock Numbers: As a seller, I want to be able to edit the amount of a product that is currently in stock.

Task Breakdown:

1. User requests to edit their catalogue.
2. Return user catalogue data.
3. User chooses to edit a catalogue item.
4. If the item exists, take the user to the item's page. Otherwise, display an error to the user.
5. User edits item stock.
6. If action is successful, display success to the user. Otherwise, display an error to the user.

Acceptance Testing:

1. Seller navigates to their store and views products.
2. Seller selects item they wish to edit quantity of.
3. Seller edits quantity field.
4. If quantity is invalid number or blank, seller is asked to reenter information.
5. Item is edited and updated to store.