Software Requirements Specification for Online Book Shopping

Online Book Shopping Software Requirements Specification
Software Requirements Specification
Project name: Online Book Shopping
Application name:
Customer:
Version:0.0
Date:........
Status: Draft/final
Page 1 of 37

Online Book Shopping Software Requirements Specification
For more information Customer contact
Name: .......... Name: .........
Project Manager Project Sponsor
e-mail: e-mail:
Telephone: Telephone:........................
Revision History:
Version Date Author(s) Change Description
0.1 First draft.
Page 2 of 37

Online Book Shopping Software Requirements Specification
Table of Contents
Contents
1 Project overview...................................................................................................................................... 5
1.1 Definitions & Acronyms..................................................................................................................... 5
1.2 Referenced Documents from other sources or Notes.......................................................................5
1.3 Name of the Project.......................................................................................................................... 5
1.4 System Overview.............................................................................................................................. 5
1.5 System Objectives............................................................................................................................ 6
1.6 Support............................................................................................................................................. 6
1.7 Stakeholders..................................................................................................................................... 7
1.8 System Context................................................................................................................................ 7
1.9 Acceptance Criteria.......................................................................................................................... 7
1.10 Evaluating Success........................................................................................................................ 7
2 Overall Description of the Project............................................................................................................ 7
2.1 Overall Functionalities of the Product............................................................................................... 7
2.2 User Characteristics......................................................................................................................... 8
2.3 Assumptions and Dependencies...................................................................................................... 9
2.3 Viewpoint of the Product................................................................................................................... 9
2.4.1 Analysis of User Interfacing........................................................................................................ 9
2.4.2 System Constraints.................................................................................................................. 13
2.4.3 Operations................................................................................................................................ 14
2.5 User Base....................................................................................................................................... 14
2.6 General Design Constraints............................................................................................................ 14
2.7 Project Feasibility............................................................................................................................ 14
3 Requirements........................................................................................................................................ 15
3.1 Functional Requirements.......................................................................................................... 15
3.2 Non-functional Requirements................................................................................................... 22
3.3 Software Development Life Cycle................................................................................................... 22
3.3.1 Site Map............................................................................................................................... 25
3.4 Database Requirements................................................................................................................. 26
3.4.1 Entity-Relationship Diagram..................................................................................................... 26
3.8 Extra Quality Requirements...................................................................................................... 27
3.8.1 Requirement Verification Process............................................................................................ 27
3.8.2 Software Testing and Acceptance Criteria...............................................................................28
4 References........................................................................................................................................ 29
5 Appendixes....................................................................................................................................... 31
4.1 Appendix A – Use Case diagram.................................................................................................... 31
4.2 Appendix B - Context diagram........................................................................................................ 31
4.3 Appendix C - Class diagram........................................................................................................... 32
4.4 Appendix D – Activity Diagram....................................................................................................... 33
4.4 Appendix D - Sequence Diagram................................................................................................... 34
Page 3 of 37

Online Book Shopping Software Requirements Specification
5 Sign-off.................................................................................................................................................. 35
5.1 Client Sign-off................................................................................................................................. 35
5.2 Team Sign Off................................................................................................................................. 35
Page 4 of 37

Online Book Shopping Software Requirements Specification
1 Project overview
The design overview of the proposed project is provided in this segment.
.
1.1 Definitions & Acronyms
To make easy understanding of this SRS document for both
development team members and client or end user, they can refer this
section. It consists of technical short form term throughout this document.
Terms Meaning
Admin Administrator
Client End user of the proposed system
DFD Data Flow Diagram
SDD Software Design Document
SPMP Software Project Management Plan Document
SRS Software Requirements Specification
PM Project Manager
1.2 Referenced Documents from other sources or Notes
Serial Number of the
Document/ Taken From/
URL of the source
Description about the Reference/Name of
the source
1.3 Name of the Project
Online Book Shopping
1.4 System Overview
The SRS document (Software Requirements Specification) is intended to
report and portray the understanding between the client and the software engineer
with respect to the detail of the product item asked. Its main role is to give an
unmistakable and enlightening "proclamation of client necessities" that can be
utilized as a source of perspective in advance improvement of the product
Page 5 of 37

Online Book Shopping Software Requirements Specification
framework. This record is broken into various segments used to sensibly isolate the
product prerequisites into effortlessly referenced sections.
This Software Requirements Specification (SRS Document) expects to depict
the Attributes, External Interfaces, functionality and Design Constraints forced on
Implementation and execution of the programming framework depicted all through
whatever remains of the record. All through the depiction of the product
framework, the dialect and phrasing utilized ought to unambiguous and predictable
all through the report.
1.5 System Objectives
Fundamental objective is to make the SRS document for online book
shopping and it empower the database segment for this record.
 This task is additionally gone for determining the product prerequisites to be
created and it can be connected to support the book shopping.
 It additionally used to make the particular prerequisites or model to
characterizing the product necessity record for book shopping and this undertaking
is does not recognize the a particular strategy and classification or device for
setting up the product prerequisite archive.
 This document is additionally dealt with the book buy and deals as to
accelerating and rearranging the way toward obtaining, choice and requesting the
books for clients and in addition dealing with a client database and item database
for book shop proprietors.
 The product framework is being created for a client inspired by offering
books by means of the Internet. This framework is intended to provide automatic
support for the way toward putting books available and to be purchased on the
Internet and encouraging the real deal.
 This framework is to a great extent cross-stage and is accessible to
everybody.
 The framework will be keep running on a local server with every client
having a remote UI through a web program to interface with it.
1.6 Support
To maintain the application, Administrator should support this
application. They play main role in organizing the database of user’s
credentials and monitor the process of shopping from ordering to delivering
with updated database [1].
Page 6 of 37

Online Book Shopping Software Requirements Specification
1.7 Stakeholders
Clients: Customers are assuming principle part in this application and who
purchases the items from this site. Merchants additionally utilizing this application
to offer their item. This application centres on creating improved shopping site for
clients [2].
Administrator: The individual who keeps up the private records of clients and
sellers
Super Administrator: The individual who can do endorsements for merchants
and overseeing Administrators.
Product Development Team: The improvement group builds up the application
in highlights centred and settling the issues when it meets any issue of working.
1.8 System Context
The proposed framework will take a report at web server. With the goal that
this shopping application can keep running on any program and work by client to
purchase book items [3].
1.9 Acceptance Criteria
Subsequent to completing the unit testing, framework testing and client
acknowledgment testing, this undertaking will be acknowledged in view of the
Severity 1 and Severity 2. These are given underneath.
Severity 1: The issue will be settled by distinguishing the issue. In the event that
it proceeds in excess of one functionalities or on the off chance that it intrudes on
the buying and instalment process, the group will refactor the code without
influencing the noteworthy capacities.
Severity 2: If the issue influences the client's task, the group will do further and
move this venture into the nearby out period of undertaking [4].
1.10 Evaluating Success
The achievement will be assessed in light of following criteria:
1. The task passes the criteria in client acknowledgment testing
2. Client's Feedback about their shopping background
Page 7 of 37

Online Book Shopping Software Requirements Specification
2 Overall Description of the Project
2.1 Overall Functionalities of the Product
This application lets in sellers to establishment online book shops, clients to
peruse through the stores, and the overseer to endorse and dismiss demands for
seal punishing new book shops and keep up arrangements of keep classifications.
Likewise the designer is planning a web purchasing site page to control the
different books in shop and furthermore help customers to buy them on-line
without venturing to every part of the store physical [5]. The web based shopping
framework will utilize the web as the main technique for elevating items to its
clients.
Display tests
The web architecture in imperative in this application. It ought to be more
alluring and intuitive one for clients. The outline and show highlights will be tried
[6].
Record information
Putting away the data about clients and sellers is something critical in this
venture, for example, their qualification data, requested item data et cetera.
Reviews
Dissecting the web logs and occasion logs is important to think about how
the client carry on towards this site as opposed to others. It enhances the element
of the framework [7].
Organization area
Dealing with the whole book shopping process, approving client's validation
data, manage merchants are basic zones of organization.
Download Data
In the organization territory, they can download the data about client's
enrolment and instalment detail. It is required for the proposed framework.
2.2 User Characteristics
The proposed framework comprises of three kinds of clients that are
demonstrated as follows.
1. Administrator:
The administrator keeps up all back end work, for example, recording information
and keeping the record as a refreshed. He keeps up the two clients and merchants.
2. Customer:
Page 8 of 37