Software Requirement Specification (SRS)

For

Online Shopping System

Boardway Infosys

Shree Ganesh Chowk

Tinkune,Kathmandu

Submitted by:

Supriya Shrestha

Submitted to:

Bishal Karki
 Table of Contents

1. Introduction

1.1 Purpose

1.2 Document Conventions

1.3 Intended Audience

1.4 Scope

1.5 References

2. General Description

2.1 Product Perspective

2.2 Product Features

2.3 User Classes and Characteristics

2.4 Operating Environment

2.5 Constraints

2.6 Assumptions and Dependencies

2.7 User Documentation

3. System Requirements

3.1 Functional Requirements

4. External Interface Requirements

4.1 User Interfaces

4.2 Hardware Interfaces

4.3 Communications Interfaces

4.4 Software Interfaces

5. Non-Functional Requirements

5.1 Performance Requirements

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

6. Diagrams

6.1 Use Case Diagram

6.2 DFD Diagram (Context Level and Level 1)

6.3 ER Diagram
1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description about the functional and non-
functional requirements of the Online Shopping System.It aims to define how the system will
enable customers to purchase products online and administrators to manage the system
efficiently.

1.2 Document Conventions

The IEEE template for System Requirement Specification Documents was used to create this
document .

1.3 Intended Audience

This document is intended for:

➢ Development team
➢ Quality assurance team
➢ Project managers
➢ End-users

1.4 Scope

The Online Shopping System facilitates:

1. Customers: Product browsing, purchase, feedback and order tracking.

2. Administrators: Product management, sales tracking and feedback analysis.

1.5 References

➢ IEEE Template for System Requirement Specification

https://goo.gl/nsUFwy
➢ Existing e-commerce system documentation
2. General Description

2.1 Product Perspective

This system serves as a digital platform for online shopping, offering end-to-end solutions for
users to manage purchases and orders and for administrators to maintain backend operations.
2.2 Product Features
➢ User authentication for customers and administrators.
➢ Product browsing and filtering.
➢ Shopping cart and payment integration.
➢ Feedback system for customer satisfaction.
➢ Daily sales and feedback report generation for administrators.

2.3 User Classes and Characteristics

1. Customers:

➢ Browse and purchase products.

➢ Submit feedback.

2. Administrators:

➢ Manage product data and track sales.

2.4 Operating Environment

➢ For Web Application:Any browser and operating system

➢ For Mobile Application:All version

2.5 Constraints

➢ Real-time payment integration requires stable internet.

➢ The system must comply with local privacy laws.

2.6 Assumptions and Dependencies

 ➢ All users have a stable internet connection.
➢ Payment gateway services are available.
2.7 User Documentation
➢ User manuals, online help files, and FAQs will be provided for both administrators and
customers.

3. System Requirements
3.1 Functional Requirements
➢ Login and authentication for both administrators and customers.
➢ Product management for administrators including adding, editing, and deleting products.
➢ Cart management for customers.
➢ Order tracking and delivery status.
➢ Feedback system for customers.

4. External Interface Requirements

4.1 User Interfaces
➢ Intuitive web and mobile interfaces for customers and administrators.
4.2 Hardware Interfaces
➢ Server: 16 GB RAM, SSD storage, high-speed internet connection.
4.3 Communications Interfaces

➢ HTTP/HTTPS protocols for secure data transfer.

4.4 Software Interfaces

Database: MySQL/PostgreSQL.

Backend: Node.js with Express.js.

5. Non-Functional Requirements

5.1 Performance Requirements

➢ Should support 1000+ concurrent users.

➢ Response time for critical operations must be <2 seconds.

5.2 Safety Requirements

➢ Daily database backups must be performed.

5.3 Security Requirements

➢ Passwords should be encrypted using secure algorithms.

5.4 Software Quality Attributes

➢ High maintainability and scalability

➢ Availability
6. Diagrams

6.1 Use Case Diagram

6.2 DFD Diagram

ONLINE
ADMIN CUSTOMER
SHOPPING
SYSTEM

6.2.1 Context-Level DFD

6.2.2 Level 1 DFD

This Level 1 DFD illustrates how the admin interacts with the system to manage products, view
customer feedback, track sales, and handle delivery information. Each process is linked to
appropriate data stores, ensuring smooth data flow within the system.
Components of the DFD

1. Actor:

➢ Admin: The primary actor who interacts with the system by logging in and performing
various administrative tasks.

2. Processes:

Login:

Verifies the Admin's ID and Password.

If not matched, access is rejected.

Valid data is sent to the Login Table for verification.

Add Products:

Admin adds new products with details like category and product information.

Data is stored in the Product Table.

Edit Products:

Admin edits existing product details.

Updates the Product Table.

Delete Products:

Admin removes products.

Updates the Product Table.

View Daily Sell:

Retrieves and displays daily sales data.

Data comes from the Sell Table.
View Feedback:

Displays customer feedback.

Data is fetched from the Feedback Table.

View Customer Detail:

Retrieves information about customers.

Data comes from the User Table.

Add and View Delivery Report:

Allows adding and viewing delivery details.

Data is managed in the Store Table.

3. Data Stores:

Login Table: Stores admin login credentials for verification.

Product Table: Maintains information about all products.

Sell Table: Stores details of daily sales.

Feedback Table: Holds customer feedback.

User Table: Contains customer information.

Store Table: Stores delivery details.

4. Data Flow:

Input Data: Admin provides login credentials, product details, and delivery details.

Output Data: Verified login, updated product details, sales reports, customer feedback, and
delivery reports.
 PRICE
PRO_ID QUANTITY
PRODUCT
BUY PRODUCT

This Level 1 DFD illustrates how customers interact with the system to log in, browse products,
make purchases, and provide feedback. Data flows between the customer, processes, and data
stores to ensure smooth operations within the online shopping system.
Components of the DFD
1. Actor:
➢ Customer: The primary user interacting with the system to browse, purchase, and manage
orders.
2. Processes:

Login:

Verifies the customer's ID and password against the Login Table.

If credentials are invalid, access is rejected.

Valid credentials allow access to other functionalities.

Buy Products:

Allows the customer to select products from the Product Table.

If a product is unavailable, the system rejects the request.

If available, selected items are stored temporarily in the Temp Table.

See Selected Items:

Displays products that the customer has added to their cart.

Data comes from the Temp Table.

Make Payment:

Processes the payment and calculates the total bill.

Payment details are stored in the Account Table.

View Delivery Report:

Displays delivery details to the customer.

Data is retrieved from the Store Table.

Add Feedback:

Allows the customer to provide feedback.

Feedback is stored in the Feedback Table.

3. Data Stores:

Login Table: Stores customer credentials for login verification.

Product Table: Contains all product details (availability, price, etc.).

Temp Table: Temporarily holds selected items in the cart.

Account Table: Records payment details and billing information.

Store Table: Stores delivery details and order status.

Feedback Table: Contains feedback provided by customers.

4. Data Flow:

Input Data: Customer's login credentials, product selection, and feedback.

Output Data: Verified login, product availability, cart details, payment confirmation, delivery
status, and feedback acknowledgment.
6.3 ER Diagram

An Entity-Relationship (ER) Diagram for an Online Shopping System, and it includes the
following key elements and relationships:
Entities and Attributes

1. Customer Details:

Attributes:

USER_ID: Unique identifier for the customer.

USER_NA: Name of the customer.

DOB: Date of birth of the customer.

PHONE_N: Contact number.

GENDER: Gender of the customer.

EMAIL: Email address.

ADDRESS: Physical address

2. Product:
Attributes
PRO_ID: Unique identifier for the product.
PROD_NAME: Name of the product.
PRICE: Cost of the product.
QUANTITY: Available quantity of the product.
3. Buy Product (Relation):
➢ Represents the purchase action between Customer Details and Product.
4. Delivery:
➢ Represents the delivery action linked to the customer.
5. Feedback:
➢ Represents customer feedback related to their purchase.
6. Make Payment:
➢ Represents the payment action associated with buying products
Relationships
1. A Customer can "Buy Products" from the Product entity, establishing a connection between
the two entities.
2. After buying a product, a customer can:
➢ Provide Feedback about the product.
➢ Make a Payment to complete the transaction.
➢ Receive Delivery details for their purchased products.

Thank You