Software Requirements

Specification
for

online shopping system

Prepared by shikha chaudhary

KIET Group of Institutions

06-october-2021

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Product Scope.................................................................................................................................1
1.3 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective.........................................................................................................................2
2.2 User Classes and Characteristics.....................................................................................................2
2.3 Operating Environment...................................................................................................................2
2.4 Design and Implementation Constraints.........................................................................................2
2.5 Assumptions and Dependencies......................................................................................................3
2.6 Specific requirements.....................................................................................................................3

3. External Interface Requirements...........................................................................................3

3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces.............................................................................................................3
4. functinal requirements

5. Non-functional Requirements...................................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose

The purpose of this project is to provide a very comfortable service for its customers, by being able
to save the item in the personal shopping cart and buy it later. Shopping through the Web simply
works for people with a valid credit card, a debit card or an internet bank account. Selling direct
online increases your reach.

1.2 Product Scope

Online Shopping System is designed to provide quality service to the customers and to allow new
online store owners a quick and easy means to setup and perform sales and other core business over
the internet. The system requires Internet connection and has to be designed with a database capable
of maintaining inventory details up-to-date. All payments will be through cash during the delivery
or shipping of items. It needs to have 3 key features:
- User friendly for computer illegitimate.
- Easy to maintain by administrators.
- Only accessible by registered users.

1.3 References

Idea of online shopping system:

Online shopping - definition and meaning - Market Business ...
https://marketbusinessnews.com › financial-glossary › o...

srs:
How to Write a Software Requirements Specification (SRS ...
https://www.perforce.com › blog › alm › how-write-sof...

23-Oct-2018 — How to Write an SRS Document · 1. Crea

Software Requirements Specification for <Project> Page 2

2. Overall Description

2.1 Product Perspective

The product is a web-based system that allows the customer to shop virtually using the Internet and
allow customers to buy the items of their desire from the store. It is aimed towards the vendors who
want to reach out to the maximum cross-section of customer and common people who can be
potential customer. It should be user-friendly, ‘quick to learn’ and reliable application for the above
purpose.

2.2 User class and Characteristics

There are three types of users in this software:

1.General public
2.Customers
3.Administrator

General public can use the system to see the product, their prices and quantity available. General
user cannot buy the products.

Customers are using for viewing and buying the products. They can also write feedbacks for
products and services.

Administrator can add, edit & remove products and provide services to the customer. Administrator
can see daily sale, feedbacks given by the customer.

2.3 Operating Environment

A full internet connection is required and any operating system and a browser like google chrome,
Mozilla Firefox, etc.

2.4 Design and Implementation Constraints

Memory: Device will have 2gb internal storage. Software and database cannot exceed this amount.
Internet: A full internet connection is required.
Operating system: Software doesn’t require any specific operating system.

2.5 Assumptions and Dependencies

1.Working of OSS need Internet Connection.

Software Requirements Specification for <Project> Page 3

2. Users and the administrator are accustomed to the paper-based system and would require
training to use the online shopping-cart application.
3. This system will use third-party software, and it is assumed that system users are familiar
with the software.

2.6 Specific requirements

This section contains details about all the software that is required for designers to create a system
to satisfy the users’ requirements and for testers to test the given requirements. This section contains
the interface description of each GUI for the different system users. These sections also give
descriptions about all the system inputs, all the functions performed by the system, and all the
system output (responses)

3. External Interface Requirements

3.1 User Interfaces

The user interface shall be web-based, allowing users to remotely access the system via several
applications. Users will be able to use the software through applications such as Microsoft Internet
Explorer, Mozilla, et al. Each part of the user interface intends to be as user friendly as possible.
The fonts and buttons used will be intended to be very fast and easy to load on web pages. The
pages will be kept light in space so that it won’t take a long time for the page to load. The starting
page will be a home page regarding the store and a number of buttons with the specific category of
the products sold. The customer will be given an option to search a product or a category through
the search engine provided in the website. In adding product to his/her cart, the customer will only
have to drag the desired product to be purchased and drop it to the cart. While in removing the
product, he/she will select the item in the cart, and specify quantity of items to be removed and
clicks the button ‘Remove Item’. There will be buttons added for the managing of accounts of the
customer and the administrator.

3.2 Hardware Interfaces

Since the application must run over the internet, all the hardware shall require to connect internet
will be hardware interface for the system. As for e.g. Modem, WAN – LAN, Ethernet Cross-Cable.
Software Requirements Specification for <Project> Page 4

3.3 Software Interfaces

During our system development, we have to design both static and dynamic website
interfaces, create website functions and a database system, edit photos and pictures, and
print out reports, so its has a set of software requirements. The following are needed
requirements. Web browser –
 Chrome
 PHP
 MySQL Database server

3.4 Communications Interfaces

The system shall use the HTTP protocol for communication over the internet.

4. Functional requirements
Use case 1- Customer’s Use Case: Register account
Diagram:

Description: Register a new customer account with the system.

Steps:
1. Customer first clicks on the button or link to initiate registration process.
2. System prompts the customer to fill out his/her first name, last name, billing address, shipping
address, email address, and their password.
3. Customer enters fields.
4. System validates the customer's information.
5. System creates a new account for the Customer.
6. System displays an account home page to Customer.

Use Case: Log-in account

Diagram:
Software Requirements Specification for <Project> Page 5

Description: Login to a customer account with the system.

Steps:
1. Customer clicks on the button or link to initiate the login process.
2. System prompts the customer for his/her email and password.
3. System verifies the information.
4. System displays account home page to the Customer.

Use Case: Log-out account

Diagram:

Description: Logout the customer account on the system.

Steps:
1. Customer clicks the button or link in order to initiate logout process.
2. System displays the home page.

Use Case: Manage account

Diagram:
Software Requirements Specification for <Project> Page 6

Description: Edit the customer account details.

Steps:
1. Customer clicks the button or link to initiate the process to edit the account.
3. Customer clicks the button or link in order to edit the account details.
4. System verifies the changes.
5. System stores new account information.

Use Case: Search Product

Diagram:

Description: Customer searches the desired product.

Steps:
1. Customer enters a category or name of the product in the search engine.
2. System searches the matching product.
3. System displays the results.

Use Case: Add item to cart

Diagram:

Description: Customer adds item(s) in the cart.

Steps:
1. Customer specifies the quantity of item(s) to be ordered.
2. System checks the availability of the product.
3. Customer drags the desired item and drops it to the cart.
4. System adds the item(s) to the cart.
Software Requirements Specification for <Project> Page 7

5. Customer confirms the items in the cart.

6. Customer returns to product listings.

Use Case: Remove item from cart

Diagram:

Description: Customer removes item(s) in the cart.

Steps:
1. Customer selects the item in the cart and clicks the button to initiate the deletion of item(s).
2. System prompts the customer to specify quantity of items to remove from cart.
3. Customer confirms the number of items to remove.
4. System removes the item(s) from the cart.

Use Case: Confirm order

Diagram:

Description: Customer places and confirms an order.

Steps:
1. Customer clicks the button or link to initiate the confirmation process.
2. System calculates order of items in the shopping cart.
3. System presents the customer with the account details.
4. Customer confirms account details.
5. Customer confirms order.
6. System stores order confirmation and order details.
7. System sends email confirmation to the Customer.
Software Requirements Specification for <Project> Page 8

Administrator:
Use Case: Log-in account

Diagram:

Steps:
1. Administrator clicks button or link to initiate login process.
2. System prompts the Administrator for email and password.
3. System verifies information.
4. System displays account home page to Administrator.

Use Case: Logout account

Diagram:

Description: Logout the Administrator account on the system.

Steps:
1. Administrator clicks button or link to initiate logout process.
2. System displays home page.

Use Case: Add product

Diagram:
Software Requirements Specification for <Project> Page 9

Description: Add product to the system.

Steps:
1. Administrator clicks the button or link to initiate Add Product process.
2. System prompts the Administrator to fill out product name, product id, product description,
product price, upload a product image, number of items in inventory, and availability of product.
3. System validates the new product information.
4. System creates a new product page for the new product.
5. System displays the newly created product page.

Use Case: Delete product

Diagram:

Description: Remove product to the system.

Steps:
1. Administrator clicks the button or link to initiate Remove Product process.
2. System prompts the Administrator to select a product by searching or viewing a list of products.
3. System validates the product information.
4. System removes the product page and product information from the system.
5. System displays the newly created product page.

Use Case: Update product

Diagram:
Software Requirements Specification for <Project> Page 10

Description: Update Product attributes within the system.

Steps:
1. Administrator clicks the button or link to initiate Update Product Attributes process.
2. System prompts the Administrator to select a product by searching or viewing a list of products.
3. System displays all of the product attributes and allows Administrator to update the product
name, product id, product description, product price, update the product image, product availability,
and/or the number of items in the inventory.
4. System validates the product information.
5. System updates the product page and product information within the system.
6. System displays the newly updated product page

5. Other Non-functional Requirements

Following Non-Functional Requirements will be there in the insurance to the internet:
(i) Secure access to consumer’s confidential data.
(ii) 24X7 availability.
(iii) Better component design to get better performance at peak time.
(iv) Flexible service based architecture will be highly desirable for future extension. non-
Functional Requirements define system properties and constraints.
Various other Non-Functional Requirements are:
 Security
 Reliability
 Maintainability
 Portability
 Extensibility
 Reusability
 Compatibility
 Resource Utilization

5.1 Performance Requirements

Maximum possible quick response to the orders is required, also should provide fast updating of
records. The changes if any made should be reflected automatically in the next screens.

5.2 Security Requirements

The application is password protected and also any updating of new product entries and order
processing is done by only privileged users.