Software Requirements Specification FOR

SOFTWARE REQUIREMENTS
SPECIFICATION
FOR
ONLINE SHOPPING SYSTEM
04/02/2019
CREATED BY-AMAN DIXIT
APPROVED BY-Ms. SWASTI SINGHAL

1. Introduction
This Software Requirements Specification specifies the requirements of the software in which people or users can upload
or download multimedia presentations, lectures video, notes pdf, images and slides. This websites will support all popular
web browsers.
Virtual education is an emerging concept. Software has a special library with a focused collection of digital objects that
include text, pdf, videos lectures, images, notes and assignment
It signifies the platform on which this whole idea is. So basically we are building a portal or interface where users can
simply login to upload or download files regarding to their concerns
1.1 Purpose
This document is meant to delineate 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 get 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 Scope
This system allows the customer’s to maintain their cart for add or remove the product over the
internet.
1.3 References
The references for the above software are as follows:-
i. www.google.co.in
ii. www.wikipedia.com
IEEE. Software Requirements Specification Std. 830-1993
2. The Overall Description
2.1 Product Perspective
This product aimed toward a person who don’t want to visit the shop as he might don’t get time for
that or might not interested in visiting there anddealing with lot of formalities.
2.2 Product Functions
OSS should support this usecase:

2.3 User Characeristics:
User should be familiar with the terms like login,register,order system etc.
2.4 General Constraints:
A full internet connection is required for OSS.
3. External Interface Requirements
3.1.1 User Interface Requirements
This section provides requirement overview ofthe system.

Various functional modules that can be implemented by the system will be -
 Registration
o If customer wants to buy the product then he/she must be
o registered, unregistered user can’t go to the shopping cart.
 Login
o Customer logins to the system by entering valid user id and password for the shopping.
 Changes to Cart
o Changes to cart means the customer after login or registration can make order or cancel
order of the product from the shopping cart.
 Payment
o In this system we are dealing the mode of payment by Cash.We will
o extend this to credit card,debit card etc in the future.
 Logout
 After ordering or surfing for the product customer has to logout.
3.1.2 Hardware Interface Requirements
Hardware requirements for insurance on internet will be same for both parties which are as follows:
 Processor: Dual Core
 RAM:2 GB
 Hard Disk:320 GB
 NIC: For eachparty
3.1.3 Software Interface Requirements
In order to perform various different functions, this software needs to interact with various other softwares. So there
are certain software interface requirements that need to be fulfilled which are listed as follows:-
 The transaction management software used to manage the transaction and keep track of resources shall be BMS
version 2.0.
 The card management software used to verify pin no and login shall be CMS version 3.0.
 LINUX based OS for security purpose

 The database used to keep record of user accounts shall be Oracle version7.0.
3.1.4 Communication Interface Requirements
 The machine needs to communicate with the main branch for each session for various functions such as
login verification, account access etc. so the following are the various communication interface requirements
that are needed to be fulfilled in order to run the software successfully:-
 The system will employ dial-up POS with the central server for low cost communication.
 The communication protocol used shall be TCP/IP and Protocol used for data transfer shall be
FileTransferProtocol.(FTP)
Validity Checks
 In order to gain access to the system, the user is required to enter his/her correct user ID/pin.
 The user can access only one account at a time and can enter only one id at a time.
 Also if the user is an administrator, he is required to enter his login id in order to access and change the
facilities provided by the system.
5 Other Non-functional Requirements
Following Non-Functional Requirements will be there in the insurance to the internet:

 Secure access to consumer’s confidential data.
 24X7 availability.
 Better component design to get better performance at peak time.
 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
 Compatibility
5.1 Performance Requirement
In order to maintain an acceptable speed at maximum numberof uploads allowed from a

particular customer as any number of users can access to the system at anytime.
Also the connections to the servers will be based on the attributes of the user like his location and
server will be working 24X7 times.
5.2 Technical Issues
This system will work on client-server architecture. It will require an internet server and which will
be able to run PHP application. The system should support some commonly used browser such as IE,
mozzila firefox,chrome etc.
5.2 Software System Attributes
5.2.1 Reliability
 The data communication protocol shall be such that it ensures reliability and quality of data and
voice transmission in a mobile environment. For example, CDMA.
 The memory system shall be of non-volatile type.
5.2.2 Availability
 The product will have a backup power supply in case of power failures.
 Any abnormal operations shall result in the shutting down of the system.
 After abnormal shutdown of the server, the system shall have to be manually restarted by a
maintenance personnel.
 There should be no inconsistency introduced in the account during whose transaction the system is
abnormally shut down.
5.5.3 Security
 The system shall be compatible with AIMS security standards.
 The Encryption standard used during pin transmission shall be triple DES.
 The password shall be 6-14 characters long.
 Passwords shall not contain name of customers as they are easy to be hacked.
5.2.4 Maintainability
 The system components i.e. modem, memory, disk, drives shall be easily serviceable without
requiring access to the vault.
 The system should have the mechanism of self-monitoring periodically in order to detect any
fault.
 The system should inform the main branch automatically as soon as it detects any error. The kind
of fault and the problem being encountered should also be mentioned by the system automatically.

Software Requirements Specification FOR

Uploaded by

Copyright:

Available Formats

Software Requirements Specification FOR

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements Specification FOR

Uploaded by

Copyright:

Available Formats

SOFTWARE REQUIREMENTS

ONLINE SHOPPING SYSTEM

CREATED BY-AMAN DIXIT

APPROVED BY-Ms. SWASTI SINGHAL

The references for the above software are as follows:-

2. The Overall Description

2.1 Product Perspective

2.2 Product Functions

OSS should support this usecase:

2.4 General Constraints:

A full internet connection is required for OSS.

3. External Interface Requirements

3.1.1 User Interface Requirements

This section provides requirement overview ofthe system.

3.1.2 Hardware Interface Requirements

3.1.3 Software Interface Requirements

 LINUX based OS for security purpose

3.1.4 Communication Interface Requirements

Following Non-Functional Requirements will be there in the insurance to the internet:

Various other Non-Functional Requirements are:

5.1 Performance Requirement

In order to maintain an acceptable speed at maximum numberof uploads allowed from a

5.2 Technical Issues

5.2 Software System Attributes

 The password shall be 6-14 characters long.

You might also like