Semester Project

Software Engineering

Submitted To

Sir Naveed Anwar Butt

Submitted By

Mr. FAISAL MEHMOD (16201519-124)

Mr. Adil Shehzad (16131519-002)

Section C

Due Date

Tuesday, June 4, 2019

Department of Computer Science

Faculty of Computing and Information Technology
University of Gujrat, Hafiz Hayat Campus
 System Requirement Specification

1 Introduction:

The purpose of this document is to present a detailed description of an online shopping

store, eStore . It will explain the purpose and features of the web application, the interfaces
of this application, what the web application will do, the constraints under which it must
operate and how the web application will react to external entities.

1.1 Systems Specifications

The following are the clauses that must be included while describing the system
specifications.

Introduction
 Our system is a client-based project.
 Our client wants to develop an easy to use online store which will fulfill his needs.
 This online shopping store which will facilitate its customers to buy products of any
category they want.
 It will display all the products of all categories like
 fashion & beauty,
 home appliances,
 kitchen products,
 sports & wear etc.
 Users can buy products by making payment online as well as cash on delivery.
 They can create their Wishlist for future.
 While the administration can check the weekly, monthly and yearly progress report
which will help them to improve their business in future.

Our application will provide following to the customers of web application:

 Sign up & sign in

 Provide information about various products
 Provide facility to user to buy products
 Online Payment/Cash on Delivery
 Easy Returns/Refund
 Generate weekly, monthly, yearly Reports
 Quick chat facility
Existing System
As our client is managing his work manually and selling his products by posting on
different Facebook groups and posting on some classified ad website like “olx.com”. Using
excel sheet to manage records of orders and sales, he faced data loss problems without
having a proper system to sell products and managing records.

Organizational Chart
We are three members in our group. We are not much experienced that one of us lead us
towards the project tasks. We are working together in all tasks like managing the timetable,
gathering requirements, making design documents, completing documentations and
developing the system. So, we all are managers, requirement engineers, designers,
developers and testers at the same time.
At the same time, we have to learn how the organizational works go. So, our organizational
chart is as follows:

Organizational Chart Fig no. 1

Scope of the System

This application provides a facility to a customer to search about a product they need and can
order products of daily life. The customer will have the ability to create their wish list of desired
products. The key goals of this project are to boost the eStore business globally, to facilitate the
online customers, to generate more revenue, to keep record of sales and to maintain the record
of customers.

Summary of Requirements: (Initial Requirements)

The initial requirements of our application are as follows:

1. This system will allow all users to use the services like search an item and add it
into Wishlist. But each user must have to register himself for ordering a product.
The web application shall provide an interface to the user to register himself. Then
for registered users, the system shall provide an interface to login to the application
via email and password. If a user forgets his password, the system shall provide an
interface to recover user’s account.
2. Our system will display all the products with their price and description to users, if
they want the product, they can add to Wishlist to buy in future or they can add to
cart and proceed shopping. Our system will also provide an interface to users to
remove something from their shopping cart or Wishlist. Our system will get
delivery information from users and proceed the order. User have to select payment
method either online payment via a debit or credit card or cash on delivery.
3. Our system will allow users to manage their accounts by editing information about
them, by editing their carts & Wishlist.
4. Whenever user place order he/she should be informed about the unique order
number via email. User can use this order number to track his/her order status. A
user will have the facility of refunding and order replacement of order in case of
faulty product.
5. Our system will have option of email subscription. When the user subscribes this
then he/she will be informed about latest products and seasonal sales.
6. Our system will have a chat option, so that user can chat with admin.
7. Our system will have a module to manage products. An admin can manage
categories, sub categories, brands and products.
8. Product description fields include name, product details, additional details, list
price, shipping charges and more.
9. An admin can add, delete, update and search product. An admin can also add
discount codes and promotions.
10. Our system will have the module for managing customer account. Admin can search
customer with their name or search with their order number. Admin can view
customer previous orders and his reviews. And admin can delete customer or reset
his/her password.
11. Our system will have the module for managing customers’ orders. Admin can
search for specific order. Admin can manage and update order status, can check
delivered orders, pending orders, declined orders etc. Admin will receive email
whenever new order will place.
12. Our system will have the option to manage sales. Interface will have been shown
 to admin about daily, weekly, monthly, and yearly sales.
1.2 Identifying External Entities
The Identification of External Entities is done in two phases.
Over Specify Entities from Abstract:

On the basis of the Abstract, the entities are:

 User/Customer  Product Categories
 Mail Subscriptions  Add to Cart
 Customer Record  Admin
 Sales Record  User Authentication
 Subscription Alerts  Sign in
 Chat Group  Sign up
 Wishlist  Order
 Online Payment  Order management
 Cash on delivery  Checkout

Perform Refinement:
After over specifying the entities, we must refine them on the basis of our Business Logic.
For example, we found the following entities more related to our Business Logic;
 User  Online Payment
 Subscription Alerts  Add to Cart & Wishlist
 Chat Group  User Authentication
 Order

1.3 Context Level Data Flow Diagram:

Context Level Data Flow Diagram Fig no.1
 1.4 Capture "shall" Statements:

Para Initial Requirements

#
1.0 The application “shall” provide a user friendly interface to the user to register
himself.
1.0 Then for registered users, the system “shall” provide a user friendly interface to
login to the website via email and password.
1.0 If a user forgets his password, the system “shall” provide an interface to recover
user’s account.
2.0 Our system “shall” provide facility to users to update their profile.
2.1 Our system “shall” provide an interface to customer to manage his/her account.
2.0 Our system “shall” provide an interface to the user to browse product efficiently.
2.0 Our system “shall” provide an interface to the user to view product easily.
2.0 Our system “shall” provide interface for zoom in and zoom out facility for picture.
2.0 Our system “shall” provide search facility to search product with category name.
2.0 Our system “shall” provide search facility to search product with product name.
2.0 Our system “shall” allow the user to add desired products to Wishlist so that he/she
can use it in future.
2.0 Our system “shall” provide an interface to user to manage his/her Wishlist.
3.0 Our system “shall” provide an interface to user to add product to Shopping Cart to
shop them later.
3.0 Our system “shall” provide an interface to user to view his/her Shopping Cart.

3.0 Our system “shall” provide an interface to user to edit quantity in his/her Shopping
Cart.
4.0 Our system “shall” provide a simple interface to user to buy a product i.e. proceed to
checkout.
4.0 Our system “shall” provide an interface to users to buy product via credit or debit
card payment.
4.0 Whenever someone place an order. Our system “shall” send a unique order number
to his/her email id.
4.0 Our system “shall” allow the customers to track their order via an order number.
5.0 Our system “shall” provide Chat facility to the customers with admin.
5.0 Our system “shall” provide an interface to the user to claim Refund.
5.0 Our system “shall” provide an interface to admin to approve refund request.
5.0 Our system “shall” provide facility of Email Subscription.
5.0 Our system “shall” provide an interface to users to give feedback about product after
purchasing.
5.0 Our system “shall” provide an interface to admin to manage feedback of user’s.
6.0 Our system “shall” provide an interface to admin to manage customers’ account.

6.0 Our system “shall” provide an interface to admin to manage Orders.

6.0 Our system “shall” provide an interface to admin to manage sales.

7.0 Our system “shall” provide an interface to admin to add products.

7.0 Our system “shall” provide an interface to admin to delete products.

7.0 Our system “shall” provide an interface to admin to update products.

7.0 Our system “shall” provide an interface to admin to search products.

7.0 Our system “shall” provide an interface to admin to manage discounts and
promotions.
7.0 Our system “shall” provide an interface only to the admin to generate sales report.

1.5 Allocate Requirements:

Para Initial Requirements Use Case Name

#
1.0 The application “shall” provide a user friendly UC_Sign Up
interface to the user to register himself.
1.0 Then for registered users, the system “shall” UC_Login
provide a user friendly interface to login to the
website via email and password.
1.0 If a user forgets his password, the system UC_Forgot_Password
“shall” provide an interface to recover user’s
account.
2.0 Our system “shall” provide facility to users to UC_Update_Account
update their profile.
2.0 Our system “shall” provide an interface to UC_Manage_Account
customer to manage his/her account.
2.0 Our system “shall” provide an interface to the UC_Browse_Product
user to browse product easily.
2.0 Our system “shall” provide an interface to the UC_View_Product
user to view product easily.
2.0 Our system “shall” provide interface for zoom UC_View_Product
in and zoom out facility for picture.
2.0 Our system “shall” provide search facility to UC_Search_by_ProductName
search product with product name.
2.0 Our system “shall” provide search facility to UC_Search_by_CategoryName
search product with category name.
3.0 Our system “shall” allow the user to add desired UC_Add_to_Wishlist
products to Wishlist so that he/she can use it in
future.
3.0 Our system “shall” provide an interface to UC_Manage_Wishlist
user to manage his/her Wishlist.
3.0 Our system “shall” provide an interface to UC_Add_to_Cart
user to add product to Shopping Cart.
3.0 Our system “shall” provide an interface to UC_View_Cart
user to view his/her Shopping Cart.
3.0 Our system “shall” provide an interface to UC_Edit_Quantity
user to edit quantity in his/her Shopping Cart.
4.0 Our system “shall” provide a simple interface UC_CheckOut
to user to buy a product i.e. proceed to
checkout.
4.0 Our system “shall” provide an interface to users UC_Payment_via_Credit_card
to buy product via credit or debit card payment.

4.0 Whenever someone place an order. Our system UC_Order_Number

“shall” send a unique order number to his/her
email id.
4.0 Our system “shall” allow the customers to UC_Track_Order
track their order via an order number.
5.0 Our system “shall” provide Chat facility to the UC_Chat
customers with admin.
5.0 Our system “shall” provide an interface to the UC_Claim_Refund
user to claim Refund.
5.0 Our system “shall” provide interface to admin UC_Approve_refund
to approve refund request made by user.
5.0 Our system “shall” provide facility of Email UC_Email_Subscription
Subscription.
5.0 Our system “shall” provide an interface to users UC_Give_Feedback
to give feedback about product after
purchasing.
5.0 Our system “shall” provide an interface to UC_Manage_Feedback
admin to manage feedback of user’s.
6.0 Our system “shall” provide an interface to UC_Manage_Customer
admin to manage customers’ account.
6.0 Our system “shall” provide an interface to UC_Manage_Order
admin to manage Orders.
6.0 Our system “shall” provide an interface to UC_Manage_Sales
admin to manage sales.
7.0 Our system “shall” provide an interface to UC_Add_product
admin to add products to system.
7.0 Our system “shall” provide an interface to UC_Delete_Product
admin to delete products from system.
7.0 Our system “shall” provide an interface to UC_Update_Product
admin to update products in system.
7.0 Our system “shall” provide an interface to UC_Search_Product
admin to search products in system.

1.6 Prioritize Requirements:

Para Rank Initial Requirements UseCase Use Case Name

# ID
3.0 Highest Our system “shall” provide an UC_6 UC_Add_to_Cart
interface to user to add product
to Shopping Cart
3.0 Highest Our system “shall” provide an UC_7 UC_View_Cart
interface to user to manage
his/her Shopping Cart.
4.0 Highest Our system “shall” provide an UC_15 UC_payment_via_credit_card
interface to users to buy
product via credit or debit card
payment.
5.0 Highest Our system “shall” provide UC_16 UC_Chat
Chat facility to the customers
with admin.
6.0 Highest Our system “shall” provide an UC_22 UC_Manage_Customer
interface to admin to manage
customers’ account.
6.0 Highest Our system “shall” provide an UC_25 UC_Manage_Order
interface to admin to manage
Orders.
6.0 Highest Our system “shall” provide an UC_24 UC_Manage_sales
interface to admin to manage
sales.
7.0 Highest Our system “shall” provide an UC_28 UC_Add_Product
interface to admin to add
products to system.
7.0 Highest Our system “shall” provide an UC_29 UC_Delete_Product
interface to admin to delete
product in system.
7.0 Highest Our system “shall” provide an UC_30 UC_Search_Product
interface to admin to search
products in a system.
7.0 Highest Our system “shall” provide an UC_31 UC_Update_Product
interface to admin to update
products in a system
2.0 Medium Our system “shall” provide an UC_11 UC_Browse_product
interface to the user to browse
product easily.
2.0 Medium Our system “shall” provide an UC_12 UC_View_Product
interface to the user to view
product easily.
2.0 Medium Our system “shall” provide UC_14 UC_ View_Product
interface for zoom in and
zoom out facility for picture.
2.0 Medium Our system “shall” provide UC_9 UC_Search_by_ProductName
search facility to search
product with product name.
2.0 Medium Our system “shall” provide UC_10 UC_
search facility to search Search_by_categoryName
product with category name.
3.0 Medium Our system “shall” provide an UC_8 UC_Edit_Quantity
interface to user to edit
quantity in his/her Shopping
Cart.
3.0 Medium Our system “shall” allow the UC_13 UC_Add_to_Wishlist
user to add desired products to
Wishlist so that he/she can use
it in future
3.0 Medium Our system “shall” provide an UC_19 UC_Manage_Wishlist
interface to user to manage
his/her Wishlist.
4.0 Medium Our system “shall” provide a UC_14 UC_Checkout
simple interface to user to buy
an product i.e. proceed to
checkout.
4.0 Medium Whenever someone place an UC_20 UC_Send_Order_Number
order. Our system “shall” send
a unique order number to
his/her email id.
4.0 Medium Our system “shall” allow the UC_19 UC_Track_Order
customers to track their order
via an order number.
5.0 Medium Our system “shall” provide UC_17 UC_Email_Subscription
facility of Email Subscription.
5.0 Medium Our system “shall” provide an UC_23 UC_Manage_Feedback
interface to admin to manage
feedback of user’s.
5.0 Medium Our system “shall” provide an UC_26 UC_Claim_Refund
interface to the user to claim
Refund.
5.0 Medium Our system “shall” provide an UC_27 UC_Approve_Refund
interface to the admin to
approve Refund.
1.0 Lowest The application “shall” UC_1 UC_SignUp
provide an interface to the user
to register himself.
1.0 Lowest Then for registered users, the UC_2 UC_Login
system “shall” provide an
interface to login to the
application via email and
password.
1.0 Lowest If a user forgets his password, UC_3 UC_Forgot_Password
the system “shall” provide an
interface to recover user’s
account.

2.0 Lowest Our system “shall” provide UC_4 UC_Update_Account

facility to users to update their
profile.
 2.0 Lowest Our system “shall” provide an UC_5 UC_Manage_Account
interface to customer to
manage his/her account.
5.0 Lowest Our system “shall” provide an UC_18 UC_Give_Feedback
interface to users to give
feedback about product after
purchasing.

1.7 Requirements Trace-ability Matrix:

Sr # Para # Initial Requirements Build Use Case Name Category

1 1.0 The application “shall” B1 UC_SingUp Business
provide a user friendly
interface to the user to
register himself.
2 1.0 Then for registered users, B1 UC_Login Business
the system “shall” provide
an interface to login to the
application via email and
password.
3 1.0 If a user forgets his B1 UC_Forgot_Password Business
password, the system
“shall” provide an interface
to recover user’s account.
4 2.0 Our system “shall” provide B1 UC_Update_Profile Business
facility to users to update
their profile.
5 2.0 Our system “shall” provide B1 UC_Manage_Account Business
an interface to customer to
manage his/her account.
6 2.0 Our system “shall” provide B1 UC_Browse_Product Business
an interface to the user to
browse product easily.
7 2.0 Our system “shall” provide B1 UC_View_Product Business
an interface to the user to
view product easily.
8 2.0 Our system “shall” provide B1 UC_View_Product Business
interface for zoom in and
zoom out facility for
picture.
9 2.0 Our system “shall” provide B1 UC_Search_by_ProductNa Business
search facility to search me
product with product name.
10 2.0 Our system “shall” provide B1 UC_Search_by_CategoryNa Business
search facility to search me
product with category
name.
11 3.0 Our system “shall” allow B1 UC_Add_to_Wishlist Business
the user to add desired
products to Wishlist so that
he/she can use it in future.
12 4.0 Our system “shall” provide B1 UC_Manage_Wishlist Business
an interface to user to
manage his/her Wishlist.
13 3.0 Our system “shall” provide B1 UC_Add_to_Cart Business
an interface to user to add
product to Shopping Cart.
14 3.0 Our system “shall” provide B1 UC_View_Cart Business
an interface to user to view
his/her Shopping Cart.
15 3.0 Our system “shall” provide B1 UC_Edit_Quantity Business
an interface to user to edit
quantity in his/her Shopping
Cart.
16 4.0 Our system “shall” provide B1 UC_CheckOut Business
a simple interface to user to
buy a product i.e. proceed to
checkout.
17 4.0 Our system “shall” provide B1 UC_Payment_via_Credit_ Business
an interface to users to buy Card
product via credit or debit
card payment.
18 4.0 Whenever someone place B1 UC_Order_Number Business
an order. Our system “shall”
send a unique order number
to his/her email id.
19 4.0 Our system “shall” allow B1 UC_Track_Order Business
the customers to track their
order via an order number.
20 5.0 Our system “shall” provide B1 UC_Chat Business
Chat facility to the
customers with admin.
21 5.0 Our system “shall” provide B1 UC_Claim_Refund Business
an interface to the user to
claim Refund.
22 5.0 Our system “shall” provide B1 UC_Approve_Refund Business
interface to admin to
approve refund request
made by user.
23 5.0 Our system “shall” provide B1 UC_Email_Subscription Business
facility of Email
Subscription.
24 5.0 Our system “shall” provide B1 UC_Give_Feedback Business
an interface to users to give
feedback about product
after purchasing.
25 5.0 Our system “shall” provide B1 UC_Manage_Feedback Business
an interface to admin to
manage feedback of user’s.
26 6.0 Our system “shall” provide B1 UC_Manage_Customers Business
an interface to admin to
manage customers’
account.
27 6.0 Our system “shall” provide B1 UC_Manage_Orders Business
an interface to admin to
manage Orders.
28 6.0 Our system “shall” provide B1 UC_Manage_Sales Business
an interface to admin to
manage sales.
29 7.0 Our system “shall” provide B1 UC_Add_Product Business
an interface to admin to add
products to system.
30 7.0 Our system “shall” provide B1 UC_Delete_Product Business
an interface to admin to
delete products in system.
31 7.0 Our system “shall” provide B1 UC_Update_Product Business
an interface to admin to
update products in a system.

33 7.0 Our system “shall” provide B1 UC_Search_Product Business

an interface to admin to
search products in system.
1.8.. High Level Use Case Diagram:

Use Case Diagram Fig no.1

1.9 Analysis Level Use Case Diagram:

Use Case Diagram Fig no.2

Use Case Diagram Fig no.3

Use Case Diagram Fig no.4

Use Case Diagram Fig no.5

 Use Case Diagram Fig no.6

Use Case Diagram Fig no.7

Use Case Diagram Fig no.8

Use Case Diagram Fig no.9

Use Case Diagram Fig no.10

Use Case Diagram Fig no.11

Use Case Diagram Fig no.12

Use Case Diagram Fig no.13

Use Case Diagram Fig no.14

Use Case Diagram Fig no.15

Use Case Diagram Fig no.16

Use Case Diagram Fig no.17

Use Case Diagram Fig no.18

Use Case Diagram Fig no.19

 1.10 Use case Description

Registration
UC ID 1
Use Case Name UC_Register
Primary Actor User
Preconditions User have to visit our website.
1. System will ask the user to register himself.
2. User will provide the required info as email address,
Basic Flow
password, Username etc.
3. System will evaluate the given info and register the user.
Post conditions Registration successful.
Special Requirements Nil
If the user does not provide required information, then system will
Alternative Flow
user to provide the all required information.

Login
UC ID 2
Use Case Name UC_Login
Primary Actor User
Preconditions User must be registered.
1. System will ask the user for email and password.
2. User will provide the required info.
Basic Flow
3. System will evaluate the info.
4. If the info is authentic, system will log in the user.
Post conditions Login Successful.
Special Requirements Nil
1. If the given email and password are wrong, then system will
ask the user to check his/her email and password or re- enter.
2. User will provide the required info.
Alternative Flow 3. System will evaluate the info.
4. If the info is not authentic, system will not log in the user,
and suggest recovering account,
 Forgot Password
UC ID 3
Use Case Name UC_Forgot_Password
Primary Actor User
Preconditions A user must have a registered account.
1. User will request for forgot password.
2. System will confirm his email address.
3. User will provide the info.
Basic Flow 4. System will send a recovery code on that email.
5. User will enter that code to the system.
6. If the recovery code matches, then system will ask the user
for new password.
Post conditions Account Recovered.
Special Requirements Nil
Account will not be recovered in case of wrong recovery code or
Alternative Flow
invalid email address.

1.11 Use Cases

Manage Own Account

UC ID 4
Use Case Name UC-update profile
Primary Actor User
Preconditions A user must be login.
1. A user clicks on manage account.
2. User click on update account, and system provide him/her
interface to update info.
Basic Flow
3. User provide info and system authenticate the information
and update user’s record.

Post conditions Account have been successfully updated

Special Requirements Nil
1. User provide information to update.
Alternative Flow 2. System will authenticate the information if information is
wrong then system ask user to enter correct information.
 Manage account
UC ID 5
Use Case Name UC_Manage_Account
Primary Actor User
Preconditions A user must login.
Assumption User logged into the system.
1. User clicks on delete account button.
2. System will ask the user to enter password.
Basic Flow 3. User enter the password.
4. System authenticate the information and delete the
account.
Post conditions Account deleted successfully.
Special Requirements Nil
1. User enter the password and system check the password, if the
Alternative Flow password does not match than system ask to enter correct
password.

Add to Cart
UC ID 6
Use Case Name UC_Add_to_Cart
Primary Actor User
Preconditions A User must login to system.
1. User clicks on desired product.
Basic Flow 2. User clicks on Add to Cart button.
3. System will add the Product to user’s shopping cart.
Post conditions Product added successfully.
Special Requirements Nil
1. If an unregistered user clicks on add to Cart, then system
Alternative Flow
will ask to please login to system or create account.
 View Cart
UC ID 7
Use Case Name UC_View _Cart
Primary Actor User
Preconditions User must visit our website.
1. User clicks on view cart.
2. System show his/her shopping cart.
Basic Flow
3. User click on delete product from cart.
4. System delete the product.
Post conditions User is redirected to home page.
Special Requirements Nil
1. System will check that if there are only 10 minutes
Alternative Flow remaining before a particular class or not.
2. If not, system will not send any notification to the user.

Edit product quantity

UC ID 8
Use Case Name UC_Edit_Quantity
Primary Actor User
Preconditions User must have to log in to the system.
1. User will request to add an assignment.
2. System will ask the user for the assignment name, topic and
its deadline.
Basic Flow
3. User will provide the required info.
4. System will check if the assignment already exists or not.
5. If not, system will add the assignment to the system.
Post conditions Assignment Added Successfully.
Special Requirements Nil
 1. User will request to add an assignment.
2. System will ask the user for the assignment name, topic and
its deadline.
Alternative Flow 3. User will provide the required info.
4. System will check if the assignment already exists or not.
5. If the assignment exists, system will send a message to the
user that the assignment has not been added.

Search Catalog
UC ID 9
Use Case Name UC_Search_by_ProductName
Primary Actor User
Preconditions User must visit our website.
1. User will click on search button.
2. System ask to enter product name.
Basic Flow 3. User provide product name and click search button.
4. System will check if the product exists or not.
5. If yes, system will show a particular product to user.
Post conditions Product found Successfully.
Assumption User login to system
Special Requirements Nil
1. User will click on search button.
2. System ask to enter product name.
3. User provide product name and click search button.
Alternative Flow
4. System will check if the product exists or not.
5. If not, then system show a message that product does not
exist, please enter right spelling or search another product.

Search Catalog
UC ID 10
Use Case Name UC_ Search_by_CategoryName
Primary Actor User
Preconditions User must visit our website.
Assumption User in logged into the system.
 1. User will click on search button.
2. System ask to enter category name.
Basic Flow 3. User provide information and click search button.
4. System will check if the searched category exists or not.
5. If yes, system will show a particular category to user.
Post conditions Result found.
Special Requirements Nil
1. User will click on search button.
2.System ask to enter category name.
3.User provide required information and click search button.
Alternative Flow 4.System will check if the category exists or not.
5.If not, then system show a message that searched category does
not exist, please enter right spelling or search another category
of product.

Browse Product
UC ID 11
Use Case Name UC_Browse_Product
Primary Actor User
Preconditions User visit our website.
Assumption User logged into the system.
1. User visit our site.
2. System will show him products
Basic Flow
3. User will click on next page.
4. System will open the next page and so on.
Post conditions Show a pop up message to user to login or create account.
Special Requirements Nil
Alternative Flow

View Product
UC ID 12
Use Case Name UC_View_Product
Primary Actor User
Preconditions User visit our website.
Assumption User logged into the system.
 5. User will click on the product.
6. System will open a page showing detail of product like
picture, price quantity color and description etc.
Basic Flow
7. User can zoom in and zoom out the product picture, select
color, quantity or can read product description, can add to
Cart, add to Wishlist or can buy the product.
Post conditions User prompt to home page.
Special Requirements Nil
Alternative Flow 1. .

Add to Wishlist
UC ID 13
Use Case Name UC_Add_to_Wishlist
Primary Actor User
Preconditions Quiz must login to the system.
1. User will click on the product.
Basic Flow 2. User will click on add to Wishlist button.
3. System will add the product to Wishlist of user.
Post conditions Product added to Wishlist successfully.
Special Requirements Nil
1. If the unregistered user clicks on add to Wishlist, then
Alternative Flow
system will ask to please login to system or create account.

Buy Product
UC ID 14
Use Case Name UC_CheckOut
Primary Actor User
Preconditions A user maybe registered or unregistered.
 1. User clicks on buy button.
2. System will open a new interface asking for login or to
create account.
3. User will create account or will login to system.
4. System will ask for delivery information.
5. User will enter his/her information like, phone#, email,
Basic Flow
address.
6. System will authenticate the information.
7. Then system will ask to payment method either cash on
delivery or via a credit card.
8. User will choose his/her desired payment method and click
on place order.
Post conditions Order placed successfully.
Special Requirements Nil
1. If the user does not provide all required detail, then system
Alternative Flow
will ask to fill all fields.

Credit card payment

UC ID 15
Use Case Name UC_payment-via-credit-card
Primary Actor User
Preconditions User should be logged into the system
1. User clicks on pay via credit card.
2. System will prompt user to payment gateway provide.
3. It will ask user to enter bank detail.
Basic Flow
4. User will enter the details and clicks on pay button.
5. Payment will verify the card.
6. If it has sufficient balance, then it will deduct the amount.
Post conditions Payment have been deducted from your account.
Special Requirements Nil
1. User clicks on pay via credit card.
2. Payment gateway system will authenticate the balance.
3. If user don’t enter correct information, then it will show a
Alternative Flow message to enter correct bank detail.
4. If user don’t have enough balance to shop the product then
system will show you a message that you don’t have a
sufficient balance.
 Chat
UC ID 16
Use Case Name UC_Chat
Primary Actor User, admin
Preconditions Both login to system.
1. User click on “message” button.
2. System will open our Facebook messenger page.
Basic Flow 3. User will type message and send to admin.
4. If Admin is online, he/she will read message and reply to
user.
Post conditions Message sent.
Special Requirements Nil
1. If the user doesn’t have messenger id, then system ask to
contact us via email.
Alternative Flow
2. If admin is online, he will reply to user instantly, otherwise
admin will send to user when he will be online.

Subscribe via Email

UC ID 17
UC_ Subscribe_via _Email
Use Case Name

Primary Actor User

Preconditions User must visit our website.
1. User click on subscribe email button.
2. System will ask to enter email id.
Basic Flow
3. User will enter email id.
4. System will store it in database.
Post conditions Successfully subscribed.
Special Requirements Nil
1. If the email is not according to email format system will
Alternative Flow
ask to enter valid email.

Feedback
UC ID 18
Use Case Name UC_Give_feedback
Primary Actor User
Preconditions User login to system.
1. User click on leave feedback button.
2. System will ask user to enter his/her feedback.
Basic Flow
3. User will enter feedback in feedback section.
4. System will store the feedback of customer.
Post conditions System will prompt the user to home screen.
Special Requirements Nil
1. If the user the user feedback section empty and click on submit
Alternative Flow feedback button, then system will ask user to please enter
feedback.

Track order
UC ID 29
Use Case Name UC_Track_Order
Primary Actor User
Preconditions User must login to system.
1. User click on track order button.
2. System will ask to enter order number.
Basic Flow 3. User will enter order number.
4. System will check order number, if yes then system will
show the order status like shipped, pending or delivered.
Post conditions Prompt user to back screen.
Special Requirements Nil
1. System will order number if No then system ask to enter
correct order number.
Alternative Flow
2. Order status will not be shown unless user provide correct
order number.

Send Order Number

UC ID 20
Use Case Name UC_Send_Order_Number
Primary Actor System
Preconditions Email of user must be valid.
1. User click on place order button.
2. System will send him/her a unique order number on
Basic Flow
his/her email id.
 System show a message of “Order number have been sent to your
Post conditions
email.”
Special Requirements Nil
Alternative Flow .

Generate Reports
UC ID 21
Use Case Name UC_Generate_Reports
Primary Actor Admin
Preconditions Admin must login to system.
1. Admin click on generate report.
2. System will show him an option to generate report daily,
Basic Flow weekly, monthly, annually.
3. User click on one from above report types.
4. System will generate the particular report.
Post conditions Report generated.
Special Requirements Nil
Alternative Flow .
Manage Customer Account
UC ID 22
Use Case Name UC_Manage_Customer
Primary Actor Admin
Preconditions Admin must be login to system.
1. User will click on manage customer button.
2. System shows multiple options like delete customer’s
account, approve customer account, reset password
Basic Flow 3. Admin click on delete customer account
4. System asks to enter customer email.
5. Admin will enter customer email and press delete button.
6. System will delete customer account.
Post conditions Customer account deleted successfully.
Special Requirements Nil
If the entered email do not exist in the system, system will show
Alternative Flow
an error message and asks for a valid email.

Manage Feedbacks
UC ID 23
Use Case Name UC_Manage_Feedback
Primary Actor admin
Preconditions Admin must be logged into the system.
1. Admin click on manage feedback.
2. System shows him the feedback of user.
Basic Flow
3. Admin click on delete feedback.
4. System delete the feedback of user.
Post conditions Deleted successfully.
Special Requirements Nil
Alternative Flow 1. .

Manage Sales
UC ID 24
Use Case Name UC_Manage_Sales
Primary Actor Admin
Preconditions Admin must login to system.
1. Member will type a message and send that message in chat
group.
2. Every member including admin will receive that message.
Basic Flow OR
1. Admin will type a message and send that message in chat
group.
2. Every member will receive that message.
Post conditions Message Sent.
Special Requirements Nil
Alternative Flow -

Manage orders
UC ID 25
Use Case Name UC_Manage_Orders
Primary Actor Admin
Preconditions Admin must login to system.
 1. Admin will click on manage orders.
2. System will show him multiple option like total order,
pending order, shipped orders, check availability, cancelled
Basic Flow ordered, and completed order.
3. Admin click on one of them.
4. System will show the detail of orders.
5. Same as above admin can check all of options.
Post conditions System prompt admin to back screen.
Special Requirements Nil
Alternative Flow .

Claim refund
UC ID 26
Use Case Name UC_Claim_Refund
Primary Actor User
Preconditions User must login to system
1. User goes to his/her order and clicks on refund.
2. System will ask him reason of refund.
3. User will enter reason and submit it.
Basic Flow
4. Request will be added to system.
5. Admin will refund if it is according to terms and
conditions of website.
Post conditions Request have been successfully added.
Special Requirements Nil
1. Admin will request to add a member in the group.
2. System will ask admin for the user name.
Alternative Flow 3. Admin will provide the required info.
4. System will check if that user exist is the system or not.
5. If not, system will not add that user in chat group.

Approve Refund
UC ID 27
Use Case Name UC_Approve_Refund
Primary Actor admin
Preconditions admin must login to system
 1. Admin will receive refund request.
2. System will check if customer is authentic via an order
number.
Basic Flow 3. system will check if the request is made within 7 days are
not.
4. If yes admin will approve the refund request and will
contact the user for refund.
Post conditions Prompt admin to back screen.
Special Requirements Nil
If the request made after 7 days, then system will not
Alternative Flow
approve the request. And inform the user.

Add product
UC ID 28
Use Case Name UC_Add_Product
Primary Actor admin
Preconditions Admin must login to system.
1. Admin clicks on add product.
2. System ask admin to select product.
3. Admin select the product he/she want to upload.
4. System provide him fields to enter price, color and
Basic Flow
description of product.
5. Admin enter the required information and click on add
product.
6. System will add the product.
Post conditions Product added successfully.
Special Requirements Nil
1. Admin click on select picture of product.
2. If the selected product has large size or have different format,
then system will show a message to check product size or
Alternative Flow format.
3. Admin write product price, color and description.
4. If the entered price, color and description is not according
to data type then system ask to correct information.

Delete Product
UC ID 29
Use Case Name UC_Delete_Product
Primary Actor Admin
Preconditions Admin must login to system.
 1. Admin clicks on delete product.
2. System will ask the admin for product name.
Basic Flow 3. User will provide the required info.
4. System will check if the product exists or not.
5. If yes, system will delete the product from the system.
Post conditions Product Deleted Successfully.
Special Requirements Nil
1. Admin will request to delete a product.
2. System will ask the admin for the product name.
3. Admin will provide the required info.
Alternative Flow 4. System will check if the assignment already exists or not.
5. If not, system will send a message to the user that the
particular product does not exist in the system so can’t be
deleted.

Search product
UC ID 30
Use Case Name UC_ Search_Product
Primary Actor Admin
Preconditions Admin must login to system.
1. User will click on search button.
2. System ask to enter product name.
Basic Flow 3. User provide product name and click search button.
4. System will check if the product exists or not.
5. If yes, system will show a particular product to user.
Post conditions Product found.
Special Requirements Nil
1. Admin will click on search button.
2. System ask to enter product name.
3. Admin provide product name and click search button.
Alternative Flow
4. System will check if the product exists or not.
If not, then system show a message that product does not
exist, please enter right spelling or search another product

Update Product
UC ID 31
UC_ Update_Product
Use Case Name
Primary Actor Admin
Preconditions User must login to system.
1. Admin click on edit product detail.
2. System will ask admin to enter product name whom do u
want to edit.
3. Admin enter the product name.
Basic Flow 4. System check if the desired product exists or not.
5. If yes, then system will ask to enter product detail which
you want to edit.
6. Admin enter the product detail.
7. System update the product detail.
Post conditions Product detail updated successfully.
Special Requirements Nil
1. System will check if the particular product exists or not.
2. If No, then system show a message that product does not
exist, please enter correct name.
Alternative Flow
3. If the admin leaves some required while updating product
info and click on update button, then system ask him to enter
all fields.

Send Email
UC ID 32
Use Case Name UC_Send_Email
Primary Actor Admin
Preconditions Admin must login to system.
1. Admin will click on send emails button.
2. System ask to enter message.
Basic Flow
3. Admin will enter message and click on send.
4. System will send messages to all store email in database.
Post conditions Email sent successfully.
Special Requirements Nil
Alternative Flow

Change Password
UC ID 33
Use Case Name UC_Change_Password
Primary Actor User
Preconditions User must login to system.
 5. User click on change password button.
6. System will ask to enter previous password
7. User will enter password.
Basic Flow 8. System will authenticate the password.
9. If matches, then system ask to enter new password.
10. User will enter new password and confirm the password.
11. System will update the password.
Post conditions Password change successfully.
Special Requirements Nil
3. If previous password not matches, then system ask to enter
correct password.
Alternative Flow 4. If the new password and confirm password does not match
then system tell that password and new password does not
match, enter same password again.

Bundle of thanks