Online Book Shopping Application: Software Requirements Specification

This document presents a Software Requirements Specification (SRS) for an online book shopping application. It outlines the project's overview, including definitions, system objectives, stakeholders, and acceptance criteria. The report details the overall functionalities, user characteristics (administrator, customer, vendor), assumptions, and system context. It further elaborates on functional and non-functional requirements, software development life cycle, database requirements, and quality requirements. Use cases, including login and other functionalities, are described. The document also includes diagrams like use case diagrams, context diagrams, class diagrams, activity diagrams, and sequence diagrams, and concludes with references and sign-off sections. This SRS serves as a comprehensive guide for the development of the online book shopping application, ensuring clarity and consistency between the client and the development team.

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 35

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 35

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 35

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 35

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
framework. This record is broken into various segments used to sensibly isolate the product
prerequisites into effortlessly referenced sections.
Page 5 of 35

Online Book Shopping Software Requirements Specification
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].
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
Page 6 of 35

Online Book Shopping Software Requirements Specification
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
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
Page 7 of 35

Online Book Shopping Software Requirements Specification
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:
The purchasers are the essential clients of this application. The guests are the auxiliary clients of this
application.
3. Vendor:
The Vendors book their shop to offer their items through site. He will settle the offer
and rebates on items
2.3 Assumptions and Dependencies
The presumptions are noted below.
• The proprietor and administrator can't be a client.
• The administrator accounts username and secret key might be hard coded.
• There is no requirement for anybody to have the capacity to arrange in excess of a one
duplicate of a book in a solitary exchange.
Page 8 of 35

Online Book Shopping Software Requirements Specification
• Any client can't alter their record data.
2.3 Viewpoint of the Product
2.4.1 Analysis of User Interfacing
2.4.1.1 Use Cases
A use case addresses a unit of accommodation gave by the structure. The vital clarification
behind the use case graph is to help change clusters picture the profitable necessities of a framework,
including the relationship of "performing experts" (individuals who will collaborate with the structure)
to basic approach, and moreover the relationship among various utilize cases. Utilize case outlines
everything considered show social events of use cases — either all use cases for the entire framework,
or a breakout of a specific party of use cases with related accommodation (e.g., all security affiliation
related use cases). To display a use case on plot, pull in an oval the point of convergence of the outline
and put the name of the use case in the purpose of joining of, or underneath, the oval. To draw an on-
screen character (showing a framework client) on a usage case graph, we pull in a stick individual to the
opposite side or right of the blueprint (and just in the event that we're thinking about, a few people
draw prettier stick individuals than others).
The reason behind this chart is to demonstrate how request will cooperate with online book
shopping and guide out the basic handiness of the framework. The going with is a synopsis of the parts
that you will find in the chart on the going with page too what is joined into the usage case plans that
take after.
Actors
Appeared in the chart as stick figures with a name underneath. They address parts that will be
plainly teaming up with the framework.
Extends
Lines that interface the performing specialists with the varying Use Cases.
Collaboration
These demonstrate that there is some sort of direct participation between the performing
skilled worker and that particular esteem.
Use Cases
Oval shapes that have their names in the centre. These address arrange helpfulness inside the
system that must be executed.
Includes
Page 9 of 35

Online Book Shopping Software Requirements Specification
Contaca ted lines named "<<include>>" that accomplice two utilize cases and have a shock
pointing towards one. This surmises the use case without the jar approaches the handiness of the use
case with the shock.
Touched lines named "<<include>>" that partner two use cases and have a jolt pointing towards one.
This infers the use case without the jolt approaches the handiness of the usage case with the jolt.
Use Case Template
Depicts the basic handiness and features of every use case and the can be found in the pages
following the use case chart.
The System Boundary
The broad rectangle that contains the Use Cases. Everything inside the rectangle is the thing
that the system is responsible for executing
Cross Ref
A field in the usage case arranges that states which one of the main necessities that particular
use case satisfies.
Type
A field in the usage case arrange that states paying little heed to whether the use case is clearly
connected with by an on-screen character (Primary) or not (Secondary) and furthermore paying little
respect to whether it is central to having a working structure.
Use Cases
A field in the use case designs that state which other use cases must be executed before that
particular use case.
Use Case 1: Login to the Application
Actors: Administrator or Manager,
Description: Initiated when a customer attempts an action that is constrained. The customer is then
incited to enter in their username and mystery word remembering the ultimate objective to proceed.
Excludes: None
Includes: None
Use Case 2: Logout of the Application
Actors: Manager or Administrator, Client or Customer and System
Primary and fundamental Description: The customer or director will have the decision to logout and if
that customer is sit out of gear for a given measure of time then that customer should be logged out by
the structure thus.
Excludes: None
Page 10 of 35

Online Book Shopping Software Requirements Specification
Includes: None
Use Cases: User almost certainly completed the Log In use case.
2.4.1.2 Context Diagrams
The Context Diagram displays the structure under thought as a particular surprising state process and
after that exhibits the relationship that the framework has with other outer segments (structures, true
blue get-togethers, outside information stores, and so on. Another name for a Context Diagram is a
Context-Level Data-Flow Diagram or a Level-0 Data Flow Diagram. Since a Context Diagram is a
particular contrast in Data-Flow Diagram, seeing to some degree about Data-Flow Diagrams can be
beneficial.
A Data-Flow Diagram (DFD) is a graphical impression of the development of information
through a data framework. DFDs are one of the three central parts of the oversaw structures
examination and structure framework (SSADM). A DFD is process driven and plots 4 focal parts [23].
• Procedures (circle)
• Outside Entities (square shape)
• Information Stores (two level, parallel lines or a piece of the time and circle)
• Information Flows (twisted or straight line with sharpened stone displaying stream course)
Each DFD may indicate distinctive philosophy with information spilling into and out of each
framework. In the event that there is a need to exhibit more detail inside a specific structure, the
framework is disintegrated into various all the more little methods in a lower level DFD. In like way, the
Content Diagram or Context-Level DFD is implied a "Level-0 DFD" while the running with level of decay
is named a "Level-1 DFD", the running with is named a "Level-2 DFD", and so on. Setting Diagrams and
Data-Flow Diagrams were made for structures examination and plan. Regardless, almost as other
examination contraptions they have been utilized for different purposes. For instance, they can in like
way be utilized to get and offer the affiliations and stream of information between business diagrams.
Thusly, they ought not to be obliged to structures examination [22].
2.4.1.3 Class Diagrams
The explanation behind this graph is to demonstrate how challenges inside the structure will
speak in light of each other keeping the ultimate objective to achieve the helpfulness required by the
Use Case plot. The accompanying is an once-over of what you will discover in the diagram itself and
what's more the class depictions that take after.
Use Cases: None
Use Case: Logout
Actors: Manager or Administrator, Customer, Application System
Page 11 of 35

Online Book Shopping Software Requirements Specification
Description: The client or director will have the choice to logout and if that client is latent for a given
measure of time then that client ought to be logged out by the framework naturally.
Use Cases: User more likely than not finished the Log In utilize case.
2.4.1.4 Activity Diagram
Activity diagrams display the procedural development of control among no beneath class
contraptions even as managing an Activity. Advance diagrams can be used to uncover more noteworthy
substantive blend venture strategy at the considerable unit level, or to show low-level internal
greatness works out [21]. To the degree I can advise, advance diagrams are best used to demonstrate
additional fundamental blend lodging, as an example, how the association is at remaining getting
nearby business, or how it should need to work together. That is by means of feelings of change
diagrams are "less exact" in appearance, segregated from design structures, and venture confined
individuals have a tendency to appreciate them the majority of the all the more suddenly [20].
The Activity characterize's documentation set takes after that used as to some recognition a
country plot diagram. Like a country chart diagram, the other arrange begins with a strong float related
with the basic side interest. The advance is appeared by methods for drawing a rectangular shape with
balanced edges, encasing the leisure activity's name. Brandishing occasions might be connected with
one of a kind wearing exercises through trade follows, or to inclination shows that interface undeniable
games checked by methods for conditions of the decision factor. Activities that end the exhibited
system are related with an end factor (moreover as in a kingdom chart plot). Practically, the physical
amusements might be assembled into swim ways that are connected to display the demand that truly
performs out the movement.
2.4.1.5 Sequence Diagram
Arrangement charts exhibit a point by point stream for a specific use case or even basically part
of a specific use case. They are generally undeniable; they exhibit the calls between the assorted
challenges in their sequence and can show up, at an unmistakable level, particular calls to different
things [19].
A sequence diagram has estimations: The vertical estimation acclaimed the course of
development of messages/procures the time plan that they show up; the even estimation
demonstrates the request examples to which the messages are sent.
A sequence graph is incredibly simple to pull in. Over the most quickened reason for our
diagram, perceive the class occurrences (things) with the guide of putting each class event internal a
case (see observe four). Inside the compartment, put the wonderfulness case call and class name
detached by a space/colon/space " : ". In the event that a class occasion builds up an association on
Page 12 of 35

Online Book Shopping Software Requirements Specification
each other wonderfulness case, draw a line with an open sharpened stone demonstrating the tolerant
class event; situated the name of the message/procedure over the street. On the other hand, for
straightforward messages, we can draw a specked line with a sharpened stone demonstrating restored
the begin gloriousness event; name the touchdown respect over the contacted line. Checking an
arrangement diagram is to a stupendous degree coordinate. Begin on the upper left niche with the
"main thrust" greatness occasion that begins the movement. Through then convey after each message
down the diagram [18].
2.4.2 System Constraints
The specific constraints of this project are listed below.
 To give the framework necessity that ought to be construct utilizing the database model by
utilizing the MS Access.
 The book shopping project does not require memory necessity and the PCs ought to be
outfitted with database segment.
 The item should be put away in, for example, simple way that permits the customer simple
access to it.
 It doesn't require longer investment to reaction time for stacking the items.
The database stores passwords in plain substance and there ought not to be a watchword
recuperation choice envelop nor lockout after different invalid login tries. In this way, the system may
not sketches viably in circumstances while security is a stress [17]. These occurrences contain those
recorded above despite nonattendance of a mixed connection while sending passage allow data and
obliging clients to use "solid" passwords. A vigorous secret word is a riddle word that meets various
conditions that are establishment with the aim that supporter's passwords can't be adequately
hypothesized by methods for an attacker. For the most extreme part, these standards incorporate
ensuring that the mystery scratch joins a satisfactory assortment of characters and conveys lowercase
letters and additionally capitals, numbers, and at times, photographs.
2.4.3 Operations
The creating framework kept up by Administrator. In the event that any client task
functionalities required or not required, the improvement group and support group will include or
expel the element. The new managers required some preparation before dealing with the support
work.
2.5 User Base
This incorporates the constraints of the framework. The client who couldn't know how to work
the essential tasks, at that point it is excessively troublesome, making it impossible to utilize [9].
Page 13 of 35

Online Book Shopping Software Requirements Specification
2.6 General Design Constraints
Response Time
At the point when the client ask for any data with respect to the items, it ought to be reacted
quickly by the executive. At the point when the framework has issues in client's activities it ought to be
comprehended in a snappy way.
Ease of use
The web architecture ought to be more intuitive and alluring. The new highlights included the
site ought to be simple for clients. The instalment procedure ought to in a much secured way.
2.7 Project Feasibility
The Feasibility checking is a valuation procedure of deciding the conceivable best answers for
an inconvenience and a counsel on the wonderful probability. It can decide if or not a way be done with
the guide of a facade route programming advancement item additional effectively than the overcoming
one.
The feasibility review need to lookout 3 foremost areas;
- Market problems,
- Technical and authoritative requirements,
- Financial survey.
The impacts of this have an investigation are utilized to choose whether or never again to
safeguard with the task, or table it. In the event that it unquestionably prompts a task being authorize,
it's going to - sooner than the real fine art of the work which will be begun in proposed work - be
utilized to check the chance of the errand's prosperity.
The feasibility can be resolved in light of the measurements record and its reliance with joined
alongside existing methodology expressed out on actualities by the specialists in the public arena.
Certainty is considered as something essential in development of society and it contributes an
imperative part in customary valuable helpful guide. Data suppliers intends to achieve this objective. In
our lives, data has been developing one and it is something critical which should be had even as
needed. The Information specialist organizations has been making different instruments and
procedures to encourage their clients with legitimate and proper data.
In the advancement of new kind of library contributions, the insights innovation usage is
requested inside the libraries. In the wake of executing IT inside the library, advanced library specialist
organization has been developed. In computerized libraries, data phase is something imperative on the
grounds that, the information should be altered effectively and additionally the qualities of records
Page 14 of 35

Online Book Shopping Software Requirements Specification
inside the library. In decades, couple of years have seen prominent adjustments in library because of
actualities time. As the improvement in data innovation, a supportable and fruitful impact on library
record. With the goal that human exertion isn't required inside library. With the goal that the
specialized effect can be found on record upkeep, offering et cetera [16].
Operational Impact
Associations which may be lean of their suitable competition are social orders who the best of
their tasks in strategies which is without a doubt genuinely adjusted with their purposeful objectives.
This lets in them to expand the operational impact of their system and to increase nonstop outrageous
general act.
Economic Impact
The 'money related impact' of an essential occasion refers to the full amount of more
noteworthy outpouring created inward a very much characterized region, as a momentary end result of
acting the outcome. For most extreme occasions, spending over site activity in the close-by territory
(and especially on settlement) is the greatest fundamental segment in creating money related impact;
yet, spending by utilizing event coordinators is each unique indispensable consideration. Monetary
effect look into for the most part scanning for to establishment the net substitute in excess of a couple
of money related framework - in particular terms, cash entries and releases are estimated to build up
the web outcome.
Social Impact
Social impacts aren't more than likely to show with the guide of hazard and need to be
accomplished in the event that they're to emerge. The district to begin in passing on unequivocal social
impacts is for a case to have basically assumed goals and purposes that characterize the transportation
instruments through which the moderate impacts will emerge.
3 Requirements
3.1 Functional Requirements
As expressed by the client, security isn't a worry of this venture. All things considered, it is past
the extent of this framework to encode individual client information, scramble charge card data,
anticipate unapproved login endeavours, or some other worry of this nature. Furthermore, the
framework isn't in charge of the accompanying:
• Verifying that charge card data is substantial
• Verifying the email address gave by a client
• Storing extra data about a book past basically the title, name of creator, and cost
Page 15 of 35

Online Book Shopping Software Requirements Specification
• Allowing clients to alter their record points of interest (username, secret key, postage information,
and so on)
• Allowing clients to arrange various duplicates of a book in a solitary request
• Providing singular item pages (one page for each thing in the stock)
• Allowing the administrator to restore the login approvals or other data about the administrator
Also, the framework may need to later be reached out to give extra capacities.
One such case is included help for outwardly impeded clients. By and large a screen reading
program is utilized and guaranteeing that page-format peruses from upper left to base right in a
coherent way would be required.
Restrictions
Restrictions in this project are listed below.
1.1. End User side or Client side
1.1.1. Software Requirements
1.1.1.1. The browser such as Mozilla Firefox, Chrome or Internet Explorer is needed
1.1.2. Hardware Requirements
1.1.2.1. Keyboard, Monitor, Mouse, Printer
1.2. Developer side requirements
1.2.1. Software Requirements
1.2.1.1. Platform to develop Web-based application (IDE) is required.
1.2.1.2. Database Engine is required for storage purpose.
Database Structure requirement
2. Data Structure
2.1 Authors table has the following attributes
Name of the author
Country of Birth
Date of Birth
2.2. Books table has the following attributes
Isbn Number
Name of Author
Title of Book
Name of the publisher
Year of the publication
Page 16 of 35

Online Book Shopping Software Requirements Specification
2.3 Customers table has the following attributes
Name of the Customer
First name of the Customer
Last name of the customer
Street name of the customer
City name of the customer
State name of the customer
Zip code of the customer
Phone number of the customer
Email ID of the customer
2.4 Orderlines table has the following attributes
Number of the order
Isbn number
Quantity of the product
Cost of each product
Cost line of the product
Shipped items
2.5 Orders table has the following attributes
Number of the order
Number of the customer
Date of the order
Number of the credit card
Number of filled orders
Expiry date of the credit card
2.5 publishers table has following attributes
Name of the publisher
2.6 Sources table has the following attributes
Number of Source
Name of the Source
Street name of the source
Page 17 of 35

Online Book Shopping Software Requirements Specification
City name of the source
State name of the source
Zip code of the source
Phone number of the source
System, functional and non- functional Requirement
3. System analysis and requirements
3.1. Browsing the Inventory system
3.1.1. Organization of elements
3.1.1.1. Book Items Listed in one page
3.1.1.2. Book details shown in the tabular column format
3.1.1.3. Each book details has following
3.1.1.3.1. Title of the book
3.1.1.3.2. Name of Author
3.1.1.3.3. Price details
3.1.1.4. Listing the books as in the sorted order of the title
3.1.2. System Object Interaction
 Each book Item has checkbox to make a selection for the product
 Single button is enabled to add all selected items to the Shopping Cart
3.2. Searching the Inventory system
 Search option is available and based on only by Title of book
 Search is done while exact-match only
3.3 Create, Retrieve, Update and Delete (CRUD) Functionality is used
 The administrator can only authorized to access inventory system
 Managers or Administrators have an authorization to:
 They can create a new book entry details
 They can update an exist book details
 They can update the details about stock or quantity of the specified book
 They can create a new information
 They can review the present inventory system
 Using the same interface to browse inventory as described in
 The administrator has an additional accessibility option that he can edit the items in the book
details
 He is authorized to perform CRUD operation on all book items
 They can manage all the details from inventory system
3.4. Adding the books into Shopping Cart System
Page 18 of 35

Online Book Shopping Software Requirements Specification
3.4.1. Authorized should be logged in
 The end user can choose their product (book) and add them to cart
 If the chosen book item is not available in the stock, then the message will be displayed to
inform the user to try again later
 The end user can order any number and not limited to quantity
 If the shopping cart is available then the user can start the new checkout process
 When the user is not Logged In to the system the can just add the book items into their cart
 Before continuing the checkout procedure, they should login
3.4.2.2. Client required to login before they may start Checkout method
3.5. Checkout method
 Client should effectively utilize shopping basket before starting this system
 Checkout page comprises of
 A content box for advancement entering
 A diagram of the buy
 A content box to hold the Mastercard number
 A catch to finish the request
 Request subtle elements sent through email after the checkout has finished
 On arrange consummation the stock is decremented in light of things obtained by client
3.6. Validation System
3.6.1. Client Levels
 Chief (single, hardcoded client, no requests)
 Client (boundless, open creation, boundless requests)
3.6.2. Record Creation
 Everybody is permitted to make a record
 Required Information
 Recorded in segment 2.2
3.6.3. Account Modification
 Clients are not ready to alter any part of their record after creation
3.6.4. Login and Logout
 There is no lost-secret word recuperation
 Signing in enables one to logout
 Signing in permits checkout
Page 19 of 35

Online Book Shopping Software Requirements Specification
 There is a 30-minute session time out after which a signed in client will be logged out
consequently.
3.7. Advancements
3.7.1. Details
 Applies to whole request
 Rate off sort advancement (x% off whole request)
 Termination happens at chief determined date
 Various coupons can't be connected to same request
 Non-part clients can't have any significant bearing advancements to arrange
3.7.2. Creation
 Advancement made by supervisor
 Every advancement has a one of a kind distinguishing number (can be auto created)
 Email containing advancement sent to all part clients of the BECS framework
 Erasure
 Advancements are auto-erased when the lapse date has passed
3.8. Mechanized Reorder
3.8.1. Particulars
 Supervisor sets reorder limit on a for each thing premise
 In the event that thing achieves the reorder edge, an email is sent illuminating the
administrator of the thing's status and the framework consequently reorders the thing
 In the event that the thing has a stop-arrange connected to it, it won't naturally reorder until
the point when the director expels it.
 A chief may build the supply of a thing utilizing the director's record
3.9. Request Logging
3.9.1. Determinations
 Required Information:
 Recorded in area 2.4
 A supervisor can see every past exchange from all clients
 The framework, utilitarian and non - practical necessity incorporates the, following.
Page 20 of 35

Online Book Shopping Software Requirements Specification
Browse stock
The check stock prerequisite is utilized to List the things on single page, Shows the thing in
forbidden configuration, List the thing contains the title, cost and creator name. It additionally recorded
the things by rising request and it doesn't have singular thing pages. It likewise has the single catch to
add every chosen thing to shopping basket [15].
Search stock
The hunt stock is utilized to look through the accessible just by book title and correct matches
as it were.
Create, refresh and annihilate usefulness
The usefulness of CRUD is open for supervisor that is permitted to change the stock. The
supervisors are having the interface to make, refresh the book passage, make another advancement,
refresh the amount and supply of a specific book, erase the things from the stock and survey the
present stock.
Shopping Cart
On the off chance that signed in, shopping basket is utilized to add the things to truck and client
can just buy the one of everything. If not signed in, shopping basket is utilized to add the things to truck
and client must be login before look at the strategy.
Checkout Procedure
In checkout strategy, the client should effectively utilize the shopping basket before begin this
methodology and it comprises of following exercises, for example, a content box for hold the charge
card number, another content box for advancement entering, a catch to finish the request and another
catch to outline the buy. The registration method likewise finishes the request and it decremented the
things in light of acquired in stock.
Authentication framework
The verification framework is including the accompanying angles, for example, client levels,
account creation, login and log out and account adjustment. In client levels, the verification must be
done by administrator and client. In account creation, each client must be permitted to make a record
and give the full data about the client. In account adjustment, the clients don't have the authorization
to alter their record in the wake of finishing the record creation. In login and log out, there no secret
word recuperation, logging forms in permits to look at the stock and signing in enables one to logout
[14].
Promotions
The advancements incorporate the accompanying particulars like lapse happens at director
indicated date, rate off sort advancement, it applies to whole request and numerous coupons can't be
Page 21 of 35

Online Book Shopping Software Requirements Specification
connected to same request. The making of advancement is finished by supervisor and it has remarkable
recognizing number. The advancements are auto erase when date is terminated.
Automated reorder
The computerized reorder additionally has the particular, for example, the chiefs are increment
the supply of the thing by utilizing the supervisor account and the administrator are sets the reorder
edge on for everything premise.
Order logging
The request logging requires the client data to logging the record and director can be see the all
past exchange from all clients.
3.2 Non-functional Requirements
• Security
• Reliability
• Portability
3.3 Software Development Life Cycle
One of the fundamental considerations of the item progression process is SDLC models which
stays for Software Development Life Cycle models. SDLC – is a constant strategy, which starts from the
event, when it's settled on a decision to dispatch the endeavour, and it closes at the present time of its
full remove from the abuse. There is no one single SDLC illustrate. They are divided into principal social
occasions, each with its features and inadequacies [24].
Creating from the first and most prepared "waterfall" SDLC appear, their arrangement basically
broadened. The SDLC models better than average assortment is predestined by the wide number of
thing forms – starting with a web application change to a brain boggling remedial programming. In
addition, if you take one of the SDLC models indicated underneath as introduced – in any case, it should
be changed as per the features of the thing, undertaking, and companions. The most used, standard
and fundamental SDLC models are given underneath [25]:
1. Waterfall model
2. Agile model
3. Spiral model
4. Iterative model
5. V-shape model
Notwithstanding what sort of the models has been picked, each one of them has fundamental
stages which are used by every item progression association [13]. We ought to research those stages as
Page 22 of 35

Online Book Shopping Software Requirements Specification
this is fundamental for the understanding of the each one of SDLC models and the differences between
them. Steps did in the SDLC procedure are given beneath.
Stage 1. Planning and Requirement gathering
Every product development life cycle demonstrate begins with the investigation, in which the
partners of the procedure examine the necessities for the last item. The objective of this stage is the
itemized meaning of the framework prerequisites. Additionally, it is expected to ensure that all the
procedure members have unmistakably comprehended the undertakings and how every prerequisite
will be actualized. Frequently, the dialog includes the QA masters who can meddle the procedure with
increments notwithstanding amid the improvement arrange on the off chance that it is fundamental.
Stage 2. Designing the architecture of Software Product
At the second period of the product development life cycle, the engineers are really outlining
the design. All the diverse specialized inquiries that may show up on this stage are examined by every
one of the partners, including the client. Additionally, here are characterized the advancements utilized
as a part of the task, group stack, impediments, time allotments, and spending plan. The most suitable
task choices are made by the characterized prerequisites.
Stage 3. Product development and coding
After the necessities endorsed, the procedure goes to the following stage – real advancement.
Software engineers begin here with the source code composing while at the same time remembering
already characterized necessities. The framework managers change the product condition, front-end
software engineers build up the UI of the program and the rationales for its connection with the server.
The programming without anyone else's input expect four phases
o Development of Algorithm
o Writing the Source code
o Program Compilation
o Testing and debugging
Stage 4. Testing
The testing stage incorporates the investigating procedure. All the code blemishes missed amid
the improvement are distinguished here, recorded, and gone back to the designers to settle. The
testing procedure rehashes until the point that all the basic issues are expelled and programming work
process is steady.
Page 23 of 35

Online Book Shopping Software Requirements Specification
Stage 5. Deployment
At the point when the program is concluded and has no basic issues – the time has come to
dispatch it for the end clients. After the new program rendition discharge, the technical support group
joins. This division gives client input [14]; counsel and bolster clients amid the season of misuse. In
addition, the refresh of chosen parts is incorporated into this stage, to ensure, that the product is up
and coming and is safe to a security break.
Choosing suitable SDLC Model
Based on the analysis, Waterfall approach has been chosen to develop this online book
shopping project. The main reasons to choose waterfall approach is given below.
 The requirements are decisively archived
 Product definition is steady
 The innovations stack is predefined which makes it not dynamic
 No questionable prerequisites
 The project is small
The steps carried out in Waterfall approach of SDLC is given below.
Page 24 of 35

Online Book Shopping Software Requirements Specification
Waterfall – is a bearing SDLC uncover, wherein change framework takes after the move,
moving very much arranged through the times of exam, expecting, affirmation, testing, usage, and help.
This SDLC demonstrate fuses steady execution of each level totally. This framework is totally chronicled
and predefined with features expected that could each length of this item change life cycle appear.
3.3.1 Site Map
Page 25 of 35

Online Book Shopping Software Requirements Specification
3.4 Database Requirements
In all book, the details are presented such as, title, ISBN, year and cost. The store additionally
keeps the writer and distributer for any book. For creators, the database keeps the name, address and
the URL of their landing page. For distributers, the database keeps the name, address, telephone
number and the URL of their site. The store has a few distribution centres, every one of which has a
code, address and telephone number. The distribution center stocks a few books. A book might be
loaded at various distribution centers. The database records the quantity of duplicates of a book loaded
at different distribution centers. The book shop keeps the name, address, email-id, and telephone
number of its clients.
A client claims a few shopping bin. A shopping cart is recognized by a unique ID of checkout
and contains a few books. Some shopping cart may contain in excess of one duplicate of same book.
The database records the quantity of duplicates of each book in any shopping cart. To plan an ER graph
for such a book shop we are NOT required to distinguish keys or limitations for this issue.
3.4.1 Entity-Relationship Diagram
The element relationship outline is utilized to show the book shopping and it utilized for software
design prerequisite determination. The Entity relationship outline has following tables, for example,
Books, Orders, arrange line, distributers, sources, clients and writers. The Order tables comprises of
Order_numb, customer_numb, order_date, credit_card-number, order_filled and charge card exp date.
The order_numb is essential key and customer_numb is the outside key. The orderlines table
comprises of order_numb, isbn, amount, cost_each, cost_line and sent. Here, the order_numb is the
essential key. The Atuhors table comprises of author_name, nation of birth and information of birth.
Page 26 of 35

Online Book Shopping Software Requirements Specification
The author_name is the essential key. The publichers tables contains the distributer name and it is the
essential key. The client tables comprise of Name of the Customer, First name of the Customer, Last
name of the customer, Street name of the customer, City name of the customer, State name of the
customer, Zip code of the customer, Phone number of the customer, Email ID of the customer. Here,
the customer_numb is the essential key. The source table contains, Name of the Source, Street name of
the source, City name of the source, State name of the source, Zip code of the source, Phone number
of the source. Here, the source_numb is the primay key. The Book tables contains the isbn,
author_name, title, publisher_name, publication_year, authoritative, source_numb, retail cost and
number_on hand. Here, isbn is the primay key. The publisher_name and source_numb is the outside
key. The element relationship graph is associated with each other. It gives the powerful database
framework and it extremely helpful the product prerequisite determination report.
3.7.2.2 Database Assumptions
• In the above Entity Relationship Diagram, Bold qualities are essential key of the table.
• The qualities with checked are likewise essential key of the table.
3.8 Extra Quality Requirements
3.8.1 Requirement Verification Process
The following are confirmed and approved with client requirement.
Check out
The checking out capacity is attempted, the customer comes and interest for the checking out
of their books as this is one of the basic limit of this structure, as it is a bit of your system with which
the customer will associate, it can be seen that the customer purposes of Activity are entered precisely
endorsement are done genuinely, saving status is shown properly and the customer are all around
instructed [12].
Placing the Order
This limit is the inside bit of the cabin structure as it is used just by the delegate of the book
shop, this limit is confirmed that the customer gives the sustenance organize and the demand is taken
fittingly as the time factor is basic in this in this limit with respect to the movement of the demand.
Stock Management
Stock organization is moreover the inside bit of the system as it is dealt with by the stock
manager, this limit is confirmed the inflow and overflowing of the data to check the thing level, to give
the status of the stock.
Bill Generation
Page 27 of 35

Online Book Shopping Software Requirements Specification
The Clerk handles this limit as he delivers the bill for the customer. This limit is endeavoured to
see that the when the bill is delivered data related to the bill comes suitably to the partner when then
data is process the bill is made really [8].
Reports
As the overseer dept. handle this limit, to check the reports of the extensive number of
divisions, this is checked keeping in mind the end goal to see that when the reports are delivered each
one of the data of the related office goes to the chairman truly with the objective that the report made
are correct [9].
3.8.2 Software Testing and Acceptance Criteria
Testing is crucial to the accomplishment of the framework. Framework testing makes a sensible
suspicion that if every one of the parts of the frameworks are right, the objective will be effectively
accomplished. Deficient testing prompts blunders that may not show up until some other time. This
makes two issues [10]:
 The time slack between the reason and the presence of the issue
 The impact of framework blunders on documents and records inside the framework. A little
framework blunder can possibly detonate into a significantly bigger issue. Powerful testing
ahead of schedule in the process makes an interpretation of straightforwardly into long haul
cost investment funds from a lessened number of mistakes [11].
Another purpose behind framework testing is its utility as a client situated vehicle before usage. The
best program is useless on the off chance that it doesn't meet the client needs. Tragically, the client's
requests are frequently endangered by endeavors to encourage program or plan productivity as far as
handling time or memory use. Regularly the PC specialist and the client have correspondence
obstructions because of various foundations, interests, needs and maybe dialects. The framework
analyzer (originator, software engineer or client) who has built up some PC authority can connect this
obstruction
Testing Techniques
Both the Black Box testing and White Box testing procedures will be connected to the proposed
venture for approving the product interface and to specifically guarantee that the inside working of the
product is right. The information will be approved with the goal that the right yield is delivered. The
checks for consistence of the database will be legitimately assessed. The technique of the framework
will be checked for the intelligent ways and for particular arrangement of conditions, circles and so on.
1. Every one of the ways inside module will be practiced at any rate once
2. The legitimate choice will be practiced for genuine or false sides
Page 28 of 35

Online Book Shopping Software Requirements Specification
3. Entire code will be confirmed for the sentence structure blunders
4. The inner information structure will be approved for information consistency
5. The graphical UI will be checked for specific occasion
6. The total application will be tried after the coordination of all modules and sub modules
Testing Strategies
Unit testing will be connected to every one of the modules of the undertaking. Every one of the
modules of the task will be tried with White Box and Black Box testing to finish unit testing.
Coordination Testing will likewise be connected to confirm that every one of the interfaces work in co-
appointment with each other. The Data Flow between distinctive modules will be confirmed for the
consistency of the framework. The Bottom Up approach of mix will be connected to the proposed
venture. The alpha testing of the venture has been finished by the colleagues. The beta testing will be
finished by the representatives of Supply Department
Test Data
The example information will be set up to guarantee the correct working of the product and
approve every module. In the wake of testing the proposed venture with this example information the
normal outcomes will be contrasted and the yields got and from that point additionally steps will be
taken if fundamental.
Acceptance Phase
In this stage, in view of the pre-characterized acknowledgment criteria, we have directed
acceptance testing for the venture. For the situation the acknowledgment criteria are the satisfaction
of the considerable number of prerequisites recognized amid the prerequisite investigation stage.
4 References
[1]M. Khalifa and V. Liu, "Online consumer retention: contingent effects of online shopping habit and
online shopping experience", European Journal of Information Systems, vol. 16, no. 6, pp. 780-792,
2007.
[2]M. NA, "Online Shopping Behaviours on Apparel Products in a Cameroon Context: Understanding the
Relationships between Shopping Orientations, Gender, Online Information Search and Online
Purchase Behaviour", Journal of Accounting & Marketing, vol. 06, no. 02, 2017.
[3]R. Alsharief, "Saudi Consumers Attitudes Towards Online Shopping", International Journal of Online
Marketing, vol. 7, no. 1, pp. 16-36, 2017.
[4]D. Frederick, "Online Shopping – a New Shopping Trend (an Opinion Study)", Indian Journal of
Applied Research, vol. 3, no. 11, pp. 60-62, 2011.
Page 29 of 35

Online Book Shopping Software Requirements Specification
[5]M. Pilik, P. Klimek, E. Jurickova and P. Palka, "Comparison Shopping Agents and Czech Online
Customers’ Shopping Behaviour", International Journal of Entrepreneurial Knowledge, vol. 4, no. 2,
2016.
[6]"NOVEL DATAMINING TECHNIQUE FOR ONLINE SHOPPING", International Journal of Recent Trends
in Engineering and Research, vol. 3, no. 4, pp. 1-5, 2017.
[7]L. Wu, Y. Cai and D. Liu, "Online shopping among Chinese consumers: an exploratory investigation of
demographics and value orientation", International Journal of Consumer Studies, vol. 35, no. 4, pp.
458-469, 2011.
[8]S. Kim and B. Martinez, "Fashion consumer groups and online shopping at private sale
sites", International Journal of Consumer Studies, vol. 37, no. 4, pp. 367-372, 2012.
[9]Y. Qinghe, "The online shopping change the retail business model: A survey of the people use online
shopping in China.", IOSR Journal of Business and Management, vol. 15, no. 5, pp. 77-110, 2013.
[10]S. Wu and H. Tsai, "A Comparison of the Online Shopping Behavior Patterns of Consumer Groups
with Different Online Shopping Experiences", International Journal of Marketing Studies, vol. 9, no.
3, p. 24, 2017.
[11]S. Mahendra and M. Yoshiki, "A Bibliometric Analysis on Online Shopping", International Journal of
e-Education, e-Business, e-Management and e-Learning, vol. 5, no. 2, pp. 55-61, 2015.
[12]F. Morath and J. MMnster, "Online Shopping and Platform Design with Ex Ante Registration
Requirements", SSRN Electronic Journal, 2014.
[13]W. Solis, Defense logistics. Washington, DC: U.S. Govt. Accountability Office, 2011.
[14]M. Müller, Essentials of inventory management. New York: AMACOM, 2011.
[15]D. Krier, Speculative Management. Albany, N.Y.: State University of New York Press, 2005.
[16]P. LAPLANTE, WHAT EVERY ENGINEER SHOULD KNOW ABOUT SOFTWARE ENGINEERING. [S.l.]: CRC
PRESS, 2017.
[17]M. Treiber and A. Kesting, Traffic flow dynamics. Heidelberg: Springer, 2013.
[18]M. Swink, Managing operations across the supply chain. New York: McGraw-Hill Irwin, 2011.
[19]M. Thomsett, The little black book of project management. New York: American Management
Association, 2010.
[20]T. Luckey and J. Phillips, Software Project Management For Dummies. Hoboken: John Wiley & Sons,
Inc., 2011.
[21]T. Luckey and J. Phillips, Software Project Management For Dummies. Hoboken: John Wiley & Sons,
Inc., 2011.
[22]P. Taylor, Lazy project manager. Infinite Ideas, 2015.
[23]P. Taylor, Lazy project manager. Infinite Ideas, 2015.
Page 30 of 35

Online Book Shopping Software Requirements Specification
[24]V. Kellen, The effects of diagrams and relational complexity on user performance in conditional
probability problems in a non-learning context. 2012.
[25]K. Vermeulen and A. Copestake, Algebras, diagrams, and decisions in language, logic, and
computation. Stanford, Calif.: CSLI, 2001.
5 Appendixes
4.1 Appendix A – Use Case diagram
4.2 Appendix B - Context diagram
Page 31 of 35

Online Book Shopping Software Requirements Specification
4.3 Appendix C - Class diagram
Page 32 of 35

Online Book Shopping Software Requirements Specification
4.4 Appendix D – Activity Diagram
Page 33 of 35

Online Book Shopping Software Requirements Specification
4.4 Appendix D - Sequence Diagram
Page 34 of 35

Online Book Shopping Software Requirements Specification
5 Sign-off
5.1 Client Sign-off
5.2 Team Sign Off
Name: Date: / /
Name: Date: / /
Name: Date: / /
Name: Date: / /
Page 35 of 35