1.

Specific Requirements
A. Functional Requirements
I. Security Management
Register:
FR-1 Admin and customer can register in website by entering the
information like name, password and Email id.

FR-2 The user name should be unique .

FR-3 Authentication should be provided.

login
FR-4
Admin and customer can use the system by entering the user id
And password.
FR-5 The user id should be unique .

F.R-6 Authentication would be provided and the suitable access of the

system would be given according to the privileges.

II. Owner of website (Admin of website):

Add item:
F.R-7 Website would give facility to admin to add new item with
description.
F.R-8 Admin can add items including item descriptions, images,
pricing, and inventory levels.
F.R-9 The website would update this information.

Update item
F.R1O Website would give facility to admin to update item.

F.R-11 The updating of the item menu would be according to the

product name, price, and deals.

1
 Admin will update the item.
F.R-12 The website would update this information.

Check oder
F.R-13 Admin can view and manage new orders, including processing payments,
updating order status, and generating invoices and shipping labels.
F.R-14 Admin can send order confirmation and shipment notification
emails to customers.
F.R-15 The website would update this information.

Add Category
F.R-16 Website would give facility to admin to add new category with
description.
F.R-17 Admin can add category including item, descriptions, images,
pricing, and inventory levels.
F.R-18 The website would update this information.

III.User Management
Update Profile
F.R-19 Updating of the User would be according to the User-Id.

F.R-20 Customer would be able to update the his/her info .

F.R-21 Website would update the information.

View Profie
F.R-22 Website would give facility to customer to view his/her
information .
SRS-23 Customer can open his profile..

F.R-24 Website would display information.

2
View Item
F.R-25 System would give facility to Customer can view the
products/items.
F.R-26 Customer would be able to check the Product info.

F.R-27 System would display information.

Search and Filter

F.R-28 Customers can search for products by keywords or by using
filters such as size, color, category, and price.
F.R-29 Customers can search for and check the available product.

F.R-30 Website would display information.

Add Item to cart

F.R-31 The website would give the facility to the customer to add items
into the cart.
F.R-32 Customer will add item in cart.
F.R-33 The website would add the items with their description.

View Cart
F.R-34 System would give facility to Customer can view the Cart.
F.R-35 Customer would be able to check the Products in cart.

F.R-36 System would display information.

3
Update Cart
F.R-37 The website would give the facility to the customer to remove
items or update the quantity of item into the cart.
F.R-38 Customer update the cart.

F.R-39 The website would update this information.

Check Out the item

F.R-39 The website would give the facility to customers to check out
the item.
F.R-40 Customers would be able to check out the items,

F.R-41 Website would process the order.

View oder history

F.R-42 System would give facility to Customer can view the order
history(how many order the customer has placed before).
F.R-43 Customer would be able to check the order history .
F.R-44 System would display information.

Payment Processing
F.R-45 The website would give the facility the customer to see the bill
after choosing the item which they want to buy .
F.R-46 Website would display the bill.

F.R-47 Customers can send payments through Easy-paisa, Jazz-cash and

COD .

Cancel Oder
F.R-48 The website would give facility for Customers to cancel orders
in a limited time.
F.R-49 Customer cancel the order.

4
View shipping details
F.R-50 System would give facility to Customer can view the shipping details.

F.R-51 Customer would be able to check the shipping info.

F.R-52 System would display information.

Review and Rating:

F.R-53 The Website would give the facility of Review and Rating After
shopping .
F.R-54 Customers add the review about services.

Customer Support:
F.R-55 The Website would give the facility of customer support for the
customers

F.R-56 Customers can access customer support through a chat-bot,

email, Whats-app, or phone, with responsive and helpful
representatives to answer their questions and resolve any issues.

Logout
F.R-57 Customer can logout of the site after purchasing products.

2.Non Functional Requirements:

I.Performance Requirements:
The website will be fast and responsive, with minimal load times and high availability. This
includes optimizing the website for different devices and screen sizes, and ensuring that it
can handle high traffic volumes during peak periods.

5
1 Usability:
The website will be easy to use. The website will be a simple and attractive interface that
will be given components arranged logically so that the users of the system will not have any
problems handling the system. The overall experience of the usage will be satisfactory.
2 Reliability:
The website will be reliable with redundant systems and backup procedures in place to
prevent data loss or service disruption.
3 Availability:
The website shall be available, up and running 24*7 throughout the year except due to the
routine maintenance activities.

II. Security Requirements:

i. The website will be secure, with strong encryption and authentication measures in place to
protect customer data and prevent unauthorized access.
ii. The system will use a secured database
iii.Normal users can just read information but they cannot edit or modify anything except
their personal and some other information.
iv.System will have different types of users and every user has access constraints.

1 Error handling:
Website shall handle expected and non-expected errors in ways that prevent loss in
information and long downtime period.

2 Resource Required
HARDWARE Minimum Requirements Recommended
Requirements
CPU Dual-core 1.6 GHz Quad-core 2.4 GHz

RAM RAM 2 GB or higher 8 GB or higher

Hard Drive Hard-drive 20 GB *As Required

C.External Interface Requirements

6
1 User interface:
The user interface will allow users to interact with the website, browse products, add items
to their cart, and complete purchases. The user interface will be easy to use, and search
functionality.
2 Hardware interface:
The website will interact with the mobile and computer if the user wants to buy a product
and place an order.
3 Software interface:
Component Description

Frontend Graphical user interface for customer

Backend Administrative interface for website

Management.
Database Stores website information such as product
details and orders.
Payment Gateway interface for secure online
payments.
Shipping interface for calculating rates and tracking
Orders.

Use Case Diagram:

7
Fully Dressed Use Case:

8
UC 1: User Sign-Up:
Field Details
UseCase User-login
Name
Actors New User System
Involved
Description Allows user to log in to their account.
Precondition - User has access to the system.
s - User should log-in.
Main Flow 1. User access the log in page.
2. User submits the form.
3. System verifies and registers the user.
4. User is confirmed and log in.
Post - User successfully log in.
conditions

UC 2: Add Category:
Field Details
UseCase Add category
Name
Actors -Admin User (Primary actor)--
Involved
-System (Secondary actor)
Descriptio This use case allows an admin user to add a new category to a product
n catalog or content management system. Categories help organize products
or content, making it easier for users to navigate and find related items.
Pre- -The admin user must be logged into the system.
Conditions
-The admin user must have permission to manage categories.

-The system must be functioning correctly, with the ability to create new
categories
Main Flow 1. Admin navigates to the "Categories" section.
2. 2.System displays the "Add Category" form.

3.Admin enters category details (name, description, parent category)

9
 4.Admin submits the form.

5.System validates the input (checks for duplicates, required fields).

6.System saves the category and displays a success message.

7.New category appears in the category list.

Post- A new category is added to the system.
Conditions

UC 2: Add Item:
Field Description
UseCase Add Item
Name
Actors Admin
Involved
Description The Admin adds a new product to the website, providing details such as
product name, description, price, and images for customers to view and
purchase.
Pre Admin must be logged into the website's admin panel.
Conditions
The website must be up and running.
Main Flow 1. Admin logs into the website’s admin panel.
2. Admin navigates to the "Add Product" section.
3. System prompts for product details (name, description, price, category,
images).
4. Admin enters the product information.
5. Admin clicks "Save" or "Publish."
6. System saves the product and displays it on the website
7. System confirms that the product is successfully added to the site.

Post The new product is visible to customers on the website.

Conditions

UC 2: Manage Item:
Field Description

10
UseCase Manage Item
Name
Actors Admin
Involved
Description The Admin manages (updates or removes) an existing product on
the website. This includes editing product details like price,
description, or availability or removing the product.
Pre Admin must be logged into the website's admin panel.
Conditions
Main Flow 1.Admin logs into the website’s admin panel.

2.Admin navigates to the "Manage Products" section.

3.Admin selects the product to update or remove.

4.System displays current product details.

5.Admin updates product information (e.g., price,description, stock).

6.Admin can choose to remove the product.

7.Admin clicks "Save" (for updates) or "Delete" (to remove the(product).

8.System confirms the changes or removal

Post The product details are updated, or the product is removed from the
Condition website.

UC 4: Manage Order:
Field Description
UseCase Manage Order
Name
Actors Admin
Involved
Description This use case involves an admin reviewing and processing customer
orders, updating order statuses, and ensuring fulfillment.
Pre -Admin has access to the admin dashboard and is logged in.
Condition

11
 -Orders are placed by customers and visible in the admin system.
Main Flow 1.Admin logs into the admin dashboard.

2.Admin views the list of new and pending orders.

3.Admin selects an order to review.

4.Admin verifies order details (items, shipping address, payment status).

5.Admin checks inventory to confirm product availability.

6.Admin updates the order status (e.g., "Processing", "Shipped",

"Canceled").

7.System updates the order status and notifies the customer via email.

8.Admin may choose to manually adjust inventory or update the order if

there are issues.

9.Admin can initiate a refund or cancel the order if necessary.

Post The order status is updated (e.g., shipped, canceled, refunded).
Condition

UC 5: Registration:
Field Description
UseCase Registration
Name
Actors User
Involved
Description This use case describes the process of a new user registering for an
account on an online website.
Pre -The customer is not already registered on the website.
Condition
-The registration page is accessible on the website.

-The customer has a valid email address.

Main Flow 1.Customer navigates to the registration page on the website.

12
 2.Customer enters required details (e.g., name, email, password).

3.Customer submits the registration form.

4.System validates the input (e.g., checks for valid email format, strong
password).

5.System creates a new account and stores the customer details securely.

6.System sends a confirmation email to the customer for account

activation.

7.Customer clicks the activation link in the email to confirm the

registration. 8.System activates the account and grants access to the
customer’s new profile.

9.Customer can now log in with their registered credentials.

Post- The customer account is successfully created and activated
Condition

UC 6:View Item:
Field Description
UseCase View Item
Name
Actors User
Involved
Descriptio The user wants to view details of a specific item on the online store. This
n includes seeing the item’s image, price, description, and availability.
Pre- -The user must have access to the website.
Condition
-The user is already on the item listing page or the homepage of the
website.

-The item to be viewed must exist in the store.

Main Flow 1.User navigates to the website.

2.User searches for an item or browses through categories to find the

13
 item they are interested in.

3.User clicks on the item to view its detailed page.

4.The website displays the item’s details, including

-Item image

-Item description

-Price

-Available stock or status (e.g., "In Stock," "Out of Stock")

-Reviews and ratings (if available)

5.The user can either choose to add the item to the shopping cart, continue
browsing, or go back to the homepage.
Post- -The user has viewed the item details.
Condition
-The user can choose to proceed with adding the item to their shopping
cart or continue browsing for other items.

UC 6:Make oder:
Field Description
UseCase Make order
Name
Actors User
Involved
Description This use case describes the process by which a customer (user) places an
order for one or more items in an online store.
Pre- -User is logged into the system.
condition
-User has a product in the shopping car
Main 1.User navigates to the checkout page.
Condition
2.User selects the shipping address.

14
 3.User selects the payment method.

4.User reviews the order summary (products, price, address).

5.User confirms the order.

6.System processes payment and confirms order.

7.System sends an order confirmation to the user (via email or on-site

notification).
Post- -Order is successfully placed
Condition
-Payment is processed

-User receives order confirmation.

-The order is sent to the shipping department for fulfillment.

UC 7:Make Payment:
Field Description
Usecase Make Payment
Name
Actors User
Involved
Description The "Make Payment" use case describes the process where a customer
provides payment details to complete a transaction for their order, and the
system processes the payment and confirms the order.
Pre- -User has added items to their cart and is ready to proceed to checkout.
condition
-User is logged into the system (if required).

-User has provided the necessary payment details (credit card, PayPal,
etc.).
Main Flow 1.User navigates to the payment section during checkout.

2.User selects a payment method (e.g., credit card, PayPal).

15
 3.User enters payment details (e.g., credit card number, expiration date).

4.User reviews the total payment amount.

5.User confirms the payment.

6.System processes the payment request via the selected payment

gateway.

7.System returns a response:

-If successful: The payment is processed, and the order is confirmed.

-If failed: The system prompts the user to re-enter payment details or try a
different method.

8.System sends a confirmation of payment and order completion to the

user

Post- -Payment is successfully processed.

condition
-The order is confirmed, and the user receives a confirmation (email, on-
site notification).

-The transaction is logged in the system for future reference.

-The system updates the order status to "Paid" and triggers the fulfillment
process.

UC 8:Change Password:
Field Description
Usecase Change Password
name
Actors User
Involved
Description The "Change Password" use case describes the process where a user
updates their account password to a new one while verifying their identity
with the current password.

16
Pre- -User is logged into the system.
condion
-User knows their current password.

Main Flow 1.User navigates to the "Change Password" section in the account settings.

2.User enters their current password.

3.User enters a new password and confirms the new password.

4.User submits the password change request.

5.System verifies the current password.

6.If correct, the system updates the password with the new one.

7.System confirms that the password has been successfully changed.

Post- -The user's password is updated in the system.
condition
-The user can log in with the new password.

-The system sends a confirmation notification (email or on-site) to the

user.

17