SRS

A software requirements specification (SRS) is a description of

a software system to be developed. It is modeled after business
requirements specification (CONOPS), also known as a
stakeholder requirements specification (StRS). The software
requirements specification lays out functional and non-functional
requirements, and it may include a set of use cases that describe
user interactions that the software must provide.
Software requirements specification establishes the basis for an
agreement between customers and contractors or suppliers on how
the software product should function (in a market-driven project,
these roles may be played by the marketing and development
divisions). Software requirements specification is a rigorous
assessment of requirements before the more specific system
design stages, and its goal is to reduce later redesign. It should
also provide a realistic basis for estimating product costs, risks,
and schedules.Used appropriately, software requirements
specifications can help prevent software project failure.
SRS for online shopping system
Introduction
1.1 Purpose
This document is meant to demarcate the features of OSS, so as to
serve as a guide to the developers on one hand and a software
validation document for the prospective client on the other. The
Online Shopping System (OSS)for furniture shop web application
is intended to provide complete solutions for vendors as well as
customers through a single gate way using the internet. It will
enable vendors to setup online shops, customer to browse through
the shop and purchase them online without having to visit the shop
physically. The administration module will enable a system
administrator to approve and reject requests for new shops and
maintain various lists of shop category.
1.2 Document Conventions
OSS- Online shopping System (for furniture shop)
SRS- Software Requirement Specification
GUI- Graphical User Interface
 
1.3 Intended Audience
Customer, Administrator, Visitor etc.
 
1.4 Product Scope
This system allows the customers to maintain their cart for add or
remove the product over the internet.
 
2.Overall Description
2.1 Product Perspective
In the existing system people have to go the shops to purchase
furniture which consumes a lot of time while in this system people
can buy furniture online from the comfort of their home which
will save their valuable time.
 

 Product Functions
  Registration
 Login
 Changes to cart
 Payment
 Logout
 Report Generation
 

 User Characteristics:
 EDUCATIONAL LEVEL: At least user of the system
should be comfortable with English language
 
2.5 Design and Implementation Constraints Will work on
windows 8 and 10.
2.7 Assumptions and Dependencies
Internet is required to access software.
 
3. External Interface Requirements
3.1 User Interfaces
Various interfaces for the product could be-
1. Login Page
2. Registration Form
3. There will be a screen displaying information about
product that the shop having.
4. If the customers select the buy button then another screen
of shopping cart will be opened.
 5. After all transaction the system makes the selling report as
portable document file (.pdf) and sent to the customer E-
mail address.
 
Login page:
Registration form:
    Product
page:                                                                     
Shopping Cart:
 
 
3.2 Hardware Interfaces
The System 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.
 
3.3 Software Interfaces

 Any window-based operating system with DOS support

are primary requirements for software development
 The systems must be connected to the internet.
 
4. System Features
  Registration– If customer wants to buy the product then
he/she must be registered, unregistered user can’t go to the
shopping cart.
 Login-Customer logins to the system by entering valid
user id and password for the shopping.
 Changes to Cart-Changes to cart means the customer
after login or registration can make order or cancel order
of the product from the shopping cart.
 Payment-For customer there are many types of secure
billing will be prepaid as debit or credit card, postpaid as
after shipping, check or bank draft. The security will
provide by the third party like Pay-Pal etc.
 Logout-After the payment or surf the product the
customer will logged out.
 Report Generation–After all transaction the system can
generate the portable document file (.pdf) and then sent
one copy to the customer’s Email-address and another one
for the system data base to calculate the monthly
transaction.
 
 
5.Other Nonfunctional Requirements
5.1 Performance Requirement (Availability)
The system should be available at all times, meaning the user can
access it using a web browser. In case of a of a hardware failure or
database corruption, a replacement page will be shown and
backups of the database should be retrieved from the server and
saved by the administrator. Then the service will be restarted. It
means 24 X 7 availability.
 
5.3 Security
The system uses SSL (secured socket layer) in all transactions that
include any confidential customer information.
The system must automatically log out all customers after a period
of inactivity.
The system should not leave any cookies on the customer’s
computer containing the user’s password.