Title: Registration and Log In

Actor: Customer, Provider, System

Scenario:

1. Users need to registration first with personal email and password.

2. Users get email and password confirmation.
3. After registration, users need to log in with that personal email and password.
4. Users can view the login page.

Exception:

1. Too many server requests are not controllable for the server.
2. Too much user at a same time can cause server traffic.
3. Handling too many users requests at the same time can slow down server.
4. Incorrect email.
5. Incorrect password.
6. No database connection.

Precondition:

1. Users have devices that support internet service.

2. Users have internet connection.
3. Users are familiar with web browsing and can interact with website.

Post condition:

1. Successful: Users can registration and log in

2. Unsuccessful: Users are unable to access the website after registering or logging in due to
a server issue or high traffic.
3. Unsuccessful: Because of putting wrong password, users might not get access to the web
page.
4. Exception: Reload the page or stay on the same page in case of an error.
Title: View Product
Actor: Customer, Provider, System

Scenario:

1. Users need to registration first with personal email and password.

2. Users get email and password confirmation.
3. After registration, users need to log in with that personal email and password.
4. After log in customer can view product page to purchase product, provider can view
which product he/she add to sell, admin can view from dashboard which product provider
sell.

Exception:

1. Too many server requests are not controllable for the server.
2. Too much user at a same time can cause server traffic.
3. Handling too many users requests at the same time can slow down server.
4. Incorrect email.
5. Incorrect password.
6. No database connection.

Precondition:

1. Users have devices that support internet service.

2. Users have internet connection.
3. Users are familiar with web browsing and can interact with website.

Post condition:

1. Successful: Users can view the required page.

2. Unsuccessful: Because of putting wrong password, users might not get access to the web
page.
3. Exception: Reload the page or stay on the same page in case of an error.
Title: Search Shop
Actor: Customer, Admin

Scenario:

1. In the web page user will be able to see an option for searching shop in their area.
2. The shop list contains all information of shops including shop codes
3. Users can give orders using that shop code.

Exception:

1. Too many server request is not controllable for the server.

2. Too much user at a same time can cause server traffic.
3. User Input error.
4. No database connection.

Precondition:

1. Users can read and write English.

2. Users have devices that support internet service.
3. Users have internet connection.
4. Users are familiar with web browsing and can interact with website.

Post condition:

1. Successful: Users can find shops available in their area and all information of that shop in
the shop list
2. Unsuccessful: User can’t access to the shop list not can find shops available in that area
3. Exception: Reload the page or stay on the same page in case of an error.
Title: Search Product
Actor: Customer

Scenario:

1. Customer has to navigate to the product page to conduct the search.

2. Customer can search by the product name.

Precondition:

1. Customer must be logged in to the web application.

2. Customer must be on the specific page where he can conduct the search.
3. Customer must press the required button for the results to load.

Post condition:

1. Successful: Customer gets the desired search results.

2. Unsuccessful: Customer does not get any results and sees an error message.
3. Exception: Stay on the same page and display all product.

Exception:

1. No database connection.
2. Search button functionality is faulty.
3. Users input error.
Title: Add to Cart
Actor: Customer

Scenario:

1. Customer has to navigate to the product page to add product to the cart.
2. Customer can add product to the cart by filling up the quantity input field and pressing
the add to cart button.
3. Check if the product stock is equal or more than the required quantity or not.

Precondition:

1. Customer must be logged in to the web application.

2. Customer must be on the page.
3. Customer must press the add to cart button after filling the quantity input field.

Post condition:

1. Successful: The page will reload and the product will be added to the cart.
2. Unsuccessful: The page will reload and an error message will be shown (i.e. Product not
available in required quantity).
3. Exception: Stay on the same page and display all product.

Exception:

1. No database connection.
2. Add to cart button is faulty.
3. Too much user at a same time can cause server traffic.
4. Users input error.
Title: Remove from Cart
Actor: Customer

Scenario:

1. Customer has to navigate to the cart page to remove product from the cart.
2. Customer can remove product from the cart by pressing delete button.

Precondition:

1. Customer must be logged in to the web application.

2. Customer must be on the page.
3. Customer must press delete button to delete product.

Post condition:

1. Successful: The page will reload and the product will be deleted from the cart.
2. Unsuccessful: The page will reload and an error message will be shown (i.e. Product not
deleted).
3. Exception: Stay on the same page and display all product.

Exception:

1. No database connection.
2. Delete button is faulty or not working.
3. Too much user at a same time can cause server traffic.
4. Users input error.
Title: Update Quantity
Actor: Customer

Scenario:

1. Customer has to navigate to the cart page to update quantity from the cart.
2. Customer can update quantity from the cart by pressing Update quantity button.

Precondition:

1. Customer must be logged in to the web application.

2. Customer must be on the page.
3. Customer must press update button to update quantity product.

Post condition:

4. Successful: The page will reload and the product quantity will be updated.
5. Unsuccessful: The page will reload and an error message will be shown (i.e. Product not
updated).
6. Exception: Stay on the same page and display all product.

Exception:

5. No database connection.
6. Quantity update button is faulty or not working.
7. Too much user at a same time can cause server traffic.
8. Users input error.
Title: Wishlist Manage
Actor: Customer

Scenario:

1. Customer has to navigate to the product page to add product to the wishlist.
2. Customer can add product to the wishlist from the product by pressing add to wishlist
button.

Precondition:

1. Customer must be logged in to the web application.

2. Customer must be on the page.
3. Customer must press add to wishlist button to add product to the wishlist.

Post condition:

1. Successful: The page will reload and the product will be added to the wishlist.
2. Unsuccessful: The page will reload and an error message will be shown (i.e. Product not
added to the wishlist).
3. Exception: Stay on the same page and display all product.

Exception:
 1. No database connection.
2. Add to wishlist button not working.
3. Too much user at a same time can cause server traffic.
4. Users input error.

Title: Place Order

Actor: Customer

Scenario:

1. Customer has to navigate to the checkout page to place an order.

2. Customer need to full fill address and personal details to place an order.

Precondition:

1. Customer must be logged in to the web application.

2. Customer must be on the page.
3. Customer must press checkout button to place an order.

Post condition:

1. Successful: The page will reload and it will take to address and personal details fill up
form page to place an order.
2. Unsuccessful: The page will reload and an error message will be shown (i.e. Product not
add to the cart).
3. Exception: Stay on the same page.

Exception:

1. No database connection.
2. Checkout button not working.
3. Too much user at a same time can cause server traffic.
4. Users input error.
Title: Check receive orders
Actor: Admin, Customer, Provider

Scenario:

1. Users can check receive orders

Exception:

1. Too many server request is not controllable for the server.

2. Too much user at a same time can cause server traffic.
3. User Input error.
4. No database connection.

Precondition:

4. Users must be logged in to the web application.

5. Users must be on the page.
6. Users have internet connection.
7. Users are familiar with web browsing and can interact with website.

Post condition:

1. Successful: Users can check receive orders

2. Unsuccessful: Due to server problem the users can’t check running orders
3. Exception: Stay on the same page.
Title: Check Orders Status
Actor: Admin, Customer, Provider

Scenario:

1. Customer & provider can see his/her order status list.

2. For admin, they can get access to see all the done order list of this server.
3. Admin, provider can see all the order related information.

Exception:

1. Too much user at a same time can cause server traffic.

2. Users input error.
3. No database connection.

Precondition:

1. Users have devices that support internet service.

2. Users have internet connection.
3. Users are familiar with web browsing and can interact with website.
4. User has register on the system.
5. Customer must be logged in to the web application.
6. Customer must be on the page.

Post condition:

1. Successful: User can get information successfully.

2. Unsuccessful: Due to server problem user can’t request. User can see an error message
and system are asking for try again.
3. Exception: Stay in the same page if possible.
Title: Check personal Information
Actor: User (Admin, Customer, Provider)

Scenario:

1. User can get his/her personal information.

2. Admin can also get own and other personal information.
3. User have to log into the system.
4. Users need to navigate the profile info page.

Exception:

3. Too much user at a same time can cause server traffic.

4. User Input error.
5. No database connection.

Precondition:

1. Users have devices that support internet service.

2. Users have internet connection.
3. Users are familiar with web browsing and can interact with website.
4. Users must be logged in to the web application.
5. Users must be on the page.

Post condition:

1. Successful: User can get personal information.

2. Unsuccessful: Due to server problem user can see an error message and system will ask
for try again.
3. Exception: Stay in the same page if possible.
Title: Update Personal Information
Actor: User (Admin, Customer, Provider)

Scenario:

5. User can update his/her personal information.

6. Admin can also update own and other personal information.
7. User have to log into the system.
8. Users need to navigate the profile info page.

Exception:

6. Too much user at a same time can cause server traffic.

7. User Input error.
8. No database connection.

Precondition:

6. Users have devices that support internet service.

7. Users have internet connection.
8. Users are familiar with web browsing and can interact with website.
9. Users must be logged in to the web application.
10. Users must be on the page.

Post condition:

4. Successful: User can update personal information.

5. Unsuccessful: Due to server problem user can see an error message and system will ask
for try again.
6. Exception: Stay in the same page if possible.
Title: Registration Confirmation
Actor: Admin

Scenario:

1. User have to get access to all registration request list.

2. Then after verification user have to give access to new registered person through their id.
3. User has to be logged into the system.

Exception:

1. Too much user at a same time can cause server traffic.

2. User Input error.
3. No database connection.

Precondition:

1. Users have devices that support internet service.

2. Users have internet connection.
3. Users are familiar with web browsing and can interact with website.
4. Users must be logged in to the web application.
5. Users must be on the page.

Post condition:

1. Successful: User can give access to new user successfully.

2. Unsuccessful: Due to server. User can see an error message and system will ask for try
again.
3. Exception: Stay in the same page if possible.
Title: Payment
Actor: Admin, Customer, Provider

Scenario:

1. Provider and admin can view all order request according to customers need.
2. User can accept order request.
3. Then they can contact with their clients for completing payment.

Exception:

30. Too many server request is not controllable for the server.
31. Too much user at a same time can cause server traffic.
32. No database connection.

Precondition:

32. Provider and seller have to register to the system

33. Admin has to log into their account to receive the request.
34. Admin has to accept the request, able to contact to the provider.

Post condition:

35. Successful: Provider can get the order request and provide it successfully.
36. Unsuccessful: Admin can’t get the request for server problem. User can see an error
message and ask for try again.
37. Exception: Stay in the same page if possible.