Vidyavardhini’s College of Engineering & Technology

Department of Computer Engineering

Experiment No.: 4
To develop SRS for selected project in IEEE format
Date of Performance:
Date of Submission:

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

Software Requirements
Specification
For

E-Commerce Website

Prepared by

26_Anish Patil

28_Divya Patil

33_Aditi Sawant

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. Overall Description
3. Specific Requirements
3.1 Functionality
3.1.1 Sell Configured to Ordered Products.
3.1.2 Provide comprehensive product details.
3.1.3 Detailed product Categorizations
3.1.4 Provide Search facility.
3.1.5 Maintain customer profile.
3.1.6 Provide personalized profile
3.1.7 Provide Customer Support.
3.1.8 Email confirmation.
3.1.9 Detailed invoice for customer.
3.1.10 Provide shopping cart facility.
3.1.11 Allow multiple payment methods.
3.1.12 Online Purchase of products.
3.2 Usability
3.2.1 Graphical User Interface
3.3 Performance
3.4 Security
3.4.1 Data Transfer
3.4.2 Data Storage
3.5 Supportability
3.5.1 Configuration Management Tool
3.6 Interfaces
3.6.1 User Interfaces
3.6.2 Hardware Interfaces
4. Supporting Information
4.1 Vision document for E-commerce
4.2 Use case analysis
4.3 Structural models
4.4 Behavioural models
4.5 Non-functional requirements model
4.6 Details of Hardware & Software

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

Software Requirements Specification

1. Introduction
The Software Requirements Specification (SRS) introduction gives a general overview of the
SRS, including its purpose, scope, definitions, acronyms, abbreviations, references, and more.
The purpose of this work is to compile, examine, and provide a thorough understanding of the
entire E-Commerce Website by precisely articulating the problem description. While
describing high-level product features, it also focuses on the capabilities needed by
stakeholders and their needs. This is a list of the specific criteria for an E-Commerce Website.

1.1 Purpose
The document's goal is to compile and evaluate all of the various suggestions that have been
made for defining the system and its consumer-related requirements. In order to better
understand the project, we will also define concepts that may be developed later and record
ideas that are being explored but may be abandoned as the product develops. Additionally, we
will forecast and organize how we expect this product will be used.
This SRS document's main goal is to give readers a thorough overview of our software product,
including all of its features and objectives. This document outlines the project's user interface,
hardware, and software requirements as well as its intended audience.
Because of the advent of online business, the fashion industry's traditional marketing and
management are suffering. Organizations have been able to use the Online to reduce expenses
associated with buying, supervising supplier connections, smoothing out operations and stock,
and generating a competitive edge and successful execution of business re-designing since the
emergence of internet commerce. Traditional marketing requires customers to interact with one
another in stores and wander around different shopping racks, as well as store owners to stock,
display, and move the things that customers expect. Dealing with these tasks necessitates effort
and presence.

1.2 Scope
This SRS is intended to help in the selection of both internal and external software products,
as well as in defining the specifications of the software that needs to be built. The standard can
be applied directly to the creation of software requirements specifications or used as a template
for defining a standard that is unique to a project or group. It doesn't specify a particular
technique, instrument or nomenclature for creating an SRS.
Web-based companies have grown throughout time and are one of the fastest growing areas
on the internet.
There were numerous concerns about online purchasing at its inception, but people have
increasingly come to trust E-commerce for all kinds of shopping needs.
Sellers can increment and broaden their span to far past their urban communities - they can get
clients from in a real sense anyplace in the world, provided they are willing to ship.
Indeed, even small businesses can expand their deals and develop by selling on the web.

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

1.3 Definitions, Acronyms, and Abbreviations

Configuration It means a product which is available / Selected from a catalogue can be
customized.
FAQ Frequently Asked Questions
CRM Customer Relationship Management
Checkout The process a customer goes through to purchase an Item
Customer A person that is a user of the system but has created an account
Shopping An object that lists a customer’s selected Items, their applied promotions
Cart and gives them an option to check out

1.4 Overview
The subsequent sections of this paper give a basic description of the project, the product,
hardware, and functional and data requirements. They also include information about the users
of this project. Section 2 of this document discusses a general description of the project.
The functional requirements, data needs, limitations, and assumptions considered while
building the E-Commerce are presented in Section 3. It also gives the user viewpoint of the
product. The particular specifications for the product are also provided in Section 3. The
external interface requirements are also covered in Section 3, which also provides a thorough
overview of the functional requirements. Information in support is in Section 4.

2. Overall Description
The problem statement for the current system, which is impeding the company's growth
prospects, is contained in this paper. A list of the stakeholders and users of the suggested
solution is also included. Additionally, it demonstrates the stakeholder needs and desires that
were noted during the brainstorming session during the requirements workshop. It also includes
a list of the key characteristics of each proposed system as well as a brief description of each.
The detailed product viewpoint from many stakeholders is included in the SRS that follows. It
offers user characteristics permitted limitations, assumptions, and dependencies, as well as
required subsets, for the specific product functions.

3. Specific Requirements
The specific requirements are –

3.1 Functionality
Introduction –
The suggested web application will help business workers to launch their entire business using
it, increasing their online market reach by a big number of times over what they already have.
It will enable a variety of online retailers to market their wares. The item on the board in the
framework will be completed in a category structure. Data security is a core requirement of the
framework, and it will be addressed accordingly.

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

3.1.1 Sell Configured to Ordered Products.

3.1.1.1 The system shall display all the products that can be configured.
3.1.1.2 The system shall allow user to select the product to configure.
3.1.1.3 The system shall display all the available components of the product to
configure
3.1.1.4 The system shall enable user to add one or more component to the configuration.
3.1.2 Provide comprehensive product details.
3.1.2.1 The system shall display detailed information of the selected products.
3.1.2.2 The system shall provide browsing options to see product details.
3.1.3 Detailed product Categorizations:
The system shall display detailed product categorization to the user.
3.1.4 Provide Search facility.
3.1.5 Maintain customer profile.
The system shall allow user to create profile and set his credential.
The system shall authenticate user credentials to view the profile.
The system shall allow user to update the profile information.
3.1.6 Provide personalized profile
The system shall display both the active and completed order history in the customer
profile.
The system shall allow user to select the order from the order history.
The system shall display the detailed information about the selected order.
The system shall display the most frequently searched items by the user in the profile.
The system shall allow user to register for newsletters and surveys in the profile.
3.1.7 Provide Customer Support.
The system shall provide online help, FAQ’s customer support, and sitemap options for
customer support.
3.1.8 Email confirmation.
The system shall maintain customer email information as a required part of customer
profile.
The system shall send an order confirmation to the user through email.
3.1.9 Detailed invoice for customer.
The system shall display detailed invoice for current order once it is confirmed.
The system shall optionally allow user to print the invoice.
3.1.10 Provide shopping cart facility.
The system shall provide shopping cart during online purchase.
The system shall allow user to add/remove products in the shopping cart.
3.1.11 Allow multiple payment methods.
The system shall display available payment methods for payment.
The system shall allow user to select the payment method for order.
3.1.12 Online Purchase of products.
The system shall allow user to confirm the purchase.
The system shall enable user to enter the payment information.

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

3.2 Usability
3.2.1 Graphical User Interface
The system shall provide a uniform look and feel between all the web pages.
The system shall provide a digital image for each product in the product catalog.
The system shall provide use of icons and toolbars.

3.3 Performance
The product shall be based on web and has to be run from a web server.
The performance shall depend upon hardware components of the client/customer.

3.4 Security
3.4.1 Data Transfer
The system shall automatically log out all customers after a period of inactivity.
The system shall confirm all transactions with the customer’s web browser.
The system shall not leave any cookies on the customer’s computer containing the
user’s password.
The system shall not leave any cookies on the customer’s computer containing any of
the user’s confidential information.
3.4.2 Data Storage
The customer’s web browser shall never display a customer’s password. It shall always
be echoed with special characters representing typed characters.
The customer’s web browser shall never display a customer’s credit card number after
retrieving from the database. It shall always be shown with just the last 4 digits of the
credit card number.

3.5 Supportability
3.5.1 Configuration Management Tool
The source code developed for this system shall be maintained in configuration
management tool.

3.6 Interfaces

3.6.1 User Interfaces

The user interface for the software shall be compatible to any browser such as Internet
Explorer, Mozilla or Netscape Navigator by which user can access to the system.
The user interface shall be implemented using any tool or software package like Java
Applet, MS Front Page, EJB etc.
3.6.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.

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

4. Supporting Information
Please refer the following document:
4.1. Vision document for E-commerce.

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

4.2. Use case analysis.

4.3. Structural models.

Level - 0 DFD

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

Level - 1 DFD

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

Level - 2 DFD

4.4. Behavioral models.

CSL501: Software Engineering Lab

 Vidyavardhini’s College of Engineering & Technology
Department of Computer Engineering

4.5. Non functional requirements model.

• Security
• Logging
• Storage
• Reliability
• Scalability
• Reusability
• Configuration
• Performance
• Cost
• Interoperability
• Flexibility
• Disaster recovery
• Accessibility

4.6. Details of Hardware & Software :

Software Specifications:
• Operating system: Microsoft Windows 10
• Integrated Development Environment: PyCharm
• Django framework and SQLite database
• Programming language: Python

Hardware Specifications:
• System type: x64-based processor, 64-bit operating system.
• Memory (RAM) installed: 8.00 GB (7.34 GB Usable)
• Total size of Hard disk: 1 TB

CSL501: Software Engineering Lab