INDEX

Contents Page No.

Problem Statement …………………………………………………………………………………………………… 01
Process Model ………………………………………………………………………………………………………….. 01
1. Software Requirement Specification …………………………………………………………….. 01
1.1 Overall Description …………………………………………………………………………………. 01
1.1.1 Product Function ……………………………………………………………………………. 02
1.1.2 User Characteristics ……………………………………………………………………….. 02
1.1.3 General Constraints ……………………………………………………………………….. 03
1.1.4 Assumptions and Dependencies …………………………………………………….. 03
1.2 External Interface Requirements
1.2.1 User Interfaces ………………………………………………………………………………. 04
1.2.2 Hardware Interfaces ………………………………………………………………………. 04
1.2.3 Software Interfaces ……………………………………………………………………….. 04
1.3 Functional Requirements ……………………………………………………………………….. 04
1.4 Performance Requirements ……………………………………………………………………. 06
1.5 Design Constraints ………………………………………………………………………………….. 07
2. Data Flow Diagrams ……………………………………………………………………………………… 08
3. Data Dictionary
3.1 Tables …………………………………………………………………………………………………….. 09
3.2 Relationships Between These Entities …………………………………………………….. 10
4. ER Diagram .………………………………………………………………………………………………….. 11
5. Testing : Test Cases ………………………………………………………………………………………. 11

------------------------------- -----------------------------------------------------------

Date Teacher’s Signature

 Problem Statement
Online shopping is a web application which provides all kinds of products
to everyone at their doorstep.

The users living anywhere can connect through internet to get these
services. This web application is more effective and fast in response.

Process Model
The model chosen for our project is 'Waterfall Model'. The requirements
are well known i.e. it is known what all functionalities and behavior
should be there. The technology is understood and well incorporated in the
project. There is no ambiguity in requirements and they are met in the
project. Very less customer interaction is involved during the development
of the product. Once the product is ready then only it can be demoed to the
end users. Thus this model suits the best for project.

1. Software Requirement Specification

This system provides an easy solution for customers to buy the product
without going to the shop and also to seller to sale the product.

This proposed system can be used by any naïve user and it does not
require any educational level, experience or technical expertise in
computer field but it will be of good use if user has the good knowledge of
how to operate a computer.

1.1 Overall Description :

The Online Shopping system is an application that enables vendors to set
up online shops, customers to browse through the shops, and a system
administrator to approve and reject requests for new shops and maintain
lists of shop categories.
Also the developer can design an online shopping site to manage the items
in the shop and also help customers to search and purchase them online
without visiting the shop physically. The online shopping system will use
the internet as the sole method for selling goods to its consumers.
P a g e 1 | 13
 1.1.1 Product Function :
The online shopping application would have the following basic functions:

Display all the categories available for shopping on the system’s

main page.

Display all the items linked to each category listed on the main page.

Allow the administrator to add new items to the existing list of

available items.

Allow administrator to remove items.

Allow the administrator to modify the price of each item.

Allow the administrator to update the description about each item.

Allow the administrator to view and edit information about

each user that checkouts the items from the system.

1.1.2 User Characteristics

The users of the online shopping application, based on their roles, are
Customers (users) and the Administrator (owner).

Admin: The administrator is the person who handles this online

shopping application. One must have a basic understanding of
computers and the internet as well as prior knowledge for operating
Java programming languages. The administrator is responsible for
maintaining all the documents required for the system. The
administrator can perform the following functions:

Assign or update the price of the items, update the items in the list,
and delete the items.

Assign sales tax for different states at the time of

checkout.

View the list of customers who purchased the items.

P a g e 2 | 13
 Users: The users of this online shopping application are all
customers who would shop. These users are anyone with shopping
experience and the know-how to browse through a shopping
application. The users should be able to perform the following
functions using this system:

 View, browse, and select a category on the home page.

 View, add, and update items in the cart.

 Sign-in/login using a username and password.

 Place the order by completing the

order form.

1.1.3 General Constraints

Hardware Limitations: The minimum hardware requirement for
the system is 400-MB of RAM and a 150-MB Hard-Disk drive.

Accessibility: Initially, the software should be available as a

desktop application for a small set of users to test.

Others: The application should be built using Java and JavaScript

inscribed in HTML, and it should, initially, be accessible through
the eclipse IDE and later published on a server when the
application passes the test from small set of users.

1.1.4 Assumptions and Dependencies

Users and the administrator would require training to use the online
shopping.

The system is dependent on the availability of an Apache Tomcat

Server to run.

We assume that system users adhere to the system’s minimum

software and hardware requirements.

P a g e 3 | 13
1.2 External Interface Requirements

1.2.1 User Interfaces :

The users will work on a graphical user interface.

All the required steps for the user to perform must me specified
on each page so that it is easy for users to understand the
procedure to perform. The steps must be brief so that the content
is not a trouble.

There must be a search bar on every page for basic queries.

Limited feedbacks and reviews should be there on main page.

The screen should be formatted in such a way so that

instructions and messages always get displayed in a general
area.

The user must not be taken forward without correcting the error.

The system user should never get any operating system failure
or any fatal error.
1.2.2 Hardware Interfaces:
Hardware requirements for insurance on internet will be same for both
parties which are as follows:
 Processor: Quad Core
 RAM: 2 GB
 Hard Disk: 32 GB

1.2.3 Software Interfaces:

The system shall make use of the operating system calls to the file
management system to store and retrieve files.

1.3 Functional Requirements

FR 1 :
Description : View the categories of items on home page .
P a g e 4 | 13
FR 2 :
Description : View items in different categories.

FR 3 :

Description : To enter into this site user has to register

himself first.
Input : User Details.
Output : Filled Registration Details and user successfully registered .

FR 4:

Description : The System provides facility to login into the

system.
Input : Enter username and password.
Output : User Profile page get opened.

FR 5 :

Description : Add items to the cart.

Input : Select items to be added.
Output : Items added to the cart.

FR 6 :

Description : Search specific item or category name.

Input : Item name or Category name.
Output : Item or List of items in Category.

FR 7 :
Description : View items that are added in the cart.

FR 8 :

Description : Delete the items in the cart.

Input : Name of the items to be deleted.
Output : Items get deleted.

P a g e 5 | 13
FR 9 :
Description : The users shall place an order by completing the information
in the order form.
Input : Item name and Fill up of order form.
Output : Order Placed of the item.

FR 10 :
Description : The administrator shall be able to add new items to the list of
shopping items.
Input : Items to be added.
Output : Items added.

FR 11 :
Description : The administrator shall be able to delete items from the items file.
Input : Name of the items to be deleted.
Output : Items get deleted .

FR 12 :

Description : Administrator can view history of user.

FR 13 :

Description: Admin can refund if customer cancels the order.

Input : Cancel Order.

Output: Refund done.

1.4 Performance Requirements

The users shall be able to add an item to the cart in fewer than 7
seconds.

The users shall be able to view information about an item in fewer

than 7 seconds.

The navigation between pages shall take fewer than 10 seconds.

The application shall be able to do a validation check on the

P a g e 6 | 13
 information provided in the user-authentication form and the place-
order form to avoid false or incomplete information.

Number of users must be at most 1000 and the number of files in

the database must be no more than 10,000.

1.5 Design Constraints

All the languages and database format must be according to the
software requirements listed below ---

Hardware Requirements :
Intel or AMD processors with speed minimum 2 GHz.
2 GB RAM.
Accelerated Graphics Card.
Minimum 32 GB Hard Disk.
Better performance with 82 KB and above Cache Memory.
15’’ colour Monitor.
Keyboard with 105 keys.

Software Requirements :
Database: MS SQL Server 2022 with Microsoft SQL Desktop Engine
installed.
Framework: .NET Framework 4.8
Server: Apache Tomcat Server.
Technology: ASP.NET
Browser: Microsoft Edge
Operating System: Windows 11
JAVA Development Toolkit.
Database JDBC Driver: MySQL Connector/J 9.0.0

Reliability and Fault Tolerance :

All the users must be backed up.
The Database must be updated regularly and must be properly
maintained.
Users are authenticated.
In case of Forgot Password, immediately a mail must be sent with a
link to reset his Password.

P a g e 7 | 13
Security :
The access to all the Databases is available only to admin.
A log of all activities must be stored.

2. Data Flow Diagrams

0-level DFD :

1-level DFD :

P a g e 8 | 13
 2-level DFD :

3. Data Dictionary :
3.1 Tables :
1. Product: prod_id (Primary Key) + prod_name +
prod_price + prod_status
2. Product_category: Category_id (Primary Key) +
Category_name
3. Order: Order_no (Primary Key) + Order_date +
Order_amount
P a g e 9 | 13
 4. Tracking_Detail: Tracking_no (Primary Key) +
Courior_name
5. Supplier: Supplier_id (Primary Key) + Supplier_name +
Supplier_address
6. Customer: customer_id (Primary Key) +
customer_name + customer_address + customer_contact
7. Admin: admin_id (Primary Key) + admin_name +
Admin_role
8. Online_Shopping_Website: Website_url (Primary Key)
+ website_name + Contact_no

3.2 Relationships Between These Entities :

1. Product – Product_Category Relationship: This is a
Many-to-one relationship.
2. Customer - Order Relationship: This is a one-to-
many relationship.
3. Tracking Detail – Order Relationship: This is a
Many-to-one relationship.
4. Order - Product Relationship: This is a Many-to-one
relationship.
5. Supplier - Product Relationship: This is a Many-to-
one relationship.
6. Admin – Online_Shopping_Website Relationship:
This is a Many-to-Many relationship.
7. Online_Shopping_Website – Product_category
Relationship: This is a Many-to-one relationship.

P a g e 10 | 13
4. ER Diagram

5. Testing : Test Cases

Here are some test cases for an online shopping management software:
User Registration and Login:
1. Successful registration with valid details.
2. Registration with invalid details (missing fields, incorrect format).
3. Login with valid credentials.
4. Login with invalid credentials (wrong password, non-existent user).
5. Password recovery with valid email.
6. Password recovery with invalid email.

P a g e 11 | 13
Product Management:
1. Add new product with valid details.
2. Add product with invalid details (missing fields, incorrect format).
3. Edit existing product.
4. Delete product.
5. View product details.
6. Search products by name, description, category.

Order Management:
1. Place order with valid details.
2. Place order with invalid details (missing fields, incorrect format).
3. View order history.
4. Cancel order.
5. Update order status (pending, shipped, delivered).
6. View order details.

Payment Management:
1. Successful payment with valid details.
2. Payment with invalid details (expired card, insufficient funds).
3. Payment processing with different gateways (PayPal, G-pay, PhonePe).
4. View payment history.
5. Refund payment.

Inventory Management:
1. Update product inventory levels.
2. View product inventory levels.
3. Low stock notification.
4. Out of stock notification.
P a g e 12 | 13
Shipping Management:
1. Calculate shipping costs.
2. Select shipping options.
3. Track order shipping status.
4. Update shipping address.

Search and Filtering:

1. Search products by name, description, category.
2. Filter products by price, brand, rating.
3. Sort products by price, popularity, rating.

Security and Performance:

1. Password encryption and storage.
2. Protection against SQL injection and Cross-site Scripting (XSS).
3. Performance under heavy traffic and large datasets.

User Roles and Permissions:

1. Administrator privileges (product management, order management).
2. Customer privileges (view order history, track order status).
3. Guest privileges (browse products, search).

Error Handling:
1. Error handling for invalid user input.
2. Error handling for payment processing errors.
3. Error handling for inventory management errors.

P a g e 13 | 13