CHAPTER 2

SYSTEM ANALYSIS

2. SOFTWARE REQUIREMENT SPECIFICATIONS:

A Software Requirement Specification is a description of a software system to be
developed, laying out functional and non-functional requirements, and may include a set
of use cases that describe interactions the user will have with the software. Software
Requirement Specification establishes the basis for an agreement between customers and
contractors. The Software Requirement Specification document enlists enough and
necessary requirements that are required for the project development. To derive the
requirements we need to have clear and thorough understanding the products to be
developed or being developed. This is achieved and refined with detailed and continuous
communications with the project team and customer till the completion of the software.
2.1 INTRODUCTION
The following subsections of Software Requirement Specifications Document should
facilitate in providing the entire overview of the Information system Bookstore
Management System under development. This document aims at defining the overall
software requirements for your end users. Efforts have been made to define the
requirements
2.1.1

of

the

Information

system

exhaustively

and

accurately.

PURPOSE

The main purpose of Software Requirement Specifications Document is to describe in a

precise manner all the capabilities that will be provided by the Software Application
Bookstore Management System. It also states the various constraints which the system
will be abide to. This document further leads to clear vision of the software requirements,
specifications and capabilities. These are to be exposed to the development, testing team
and end users of the software

2.1.2 SCOPE
The web application should be able to remember the preference of a user like
remembering his billing and shipping address.
The web application should tie up with the verified by visa and VeriSign
organizations for far more secure transactions.
The
application
can
be
accessed
2.1.3

2.1.4

by

anyone

anywhere.

DEFINITION, ACRONYMS, ABBREVIATIONS

DFD :
Data Flow Diagram
ER
:
Entity Relationship
PHP :
Hypertext Pre-processor
SRS :
Software Requirements Specification
REFERENCES
www.scribd.com
www.seminarproject.com
www.wikipedia.org
www.google.co.in
Books: Software Engineering book by K.K. Aggarwal , Yogesh Singh

2.1.5 OVERVIEW
The main purpose of this software is to reduce the manual error involved in the online
bookstore process and makes it convenient for the customer to order the books as when
they require such that they utilize this software to make ordering of book, cancel a
particular ordered book, and Download E-books.
The name of the project is Bookstore Management System. This will provides option
for viewing different books available with different categories and provide customers
with the facility to order a book, Download E-books or cancel a particular Book ordered
and also provide the cost of Books. The rest of this SRS document describes the various
system

requirements,

interfaces,

features

and

functionality

in

detail.

2.2 OVERALL DESCRIPTION OF PROPOSED SYSTEM

2.2.1 PRODUCT PERSPECTIVE
The application will be windows-based, self-contained and independent software product.

PHP, CSS, HTML,

JAVASCRIPT

SQL

2.2.1.1 SYSTEM INTERFACES

None
2.2.1.2 INTERFACES
The application will have a user friendly and menu based interface. Following screens
will be provided.
(i)

A Login Screen for entering username, password for Administrator and

customer.

(ii)

Access to different screens will be based upon the role of the user and
administrator as below:

Roles of user:i.

Book Category: User can search different kind of book from book category.

ii.

Add to cart: User can add their selected book to the cart so he/she can use that
book for future purpose like buying the book.

Role of administrator:
i.

Add/Remove Book Details: Administrator can direct interact with the

database so he/she can add or remove the new book from database.

ii.

Update prices: In any case if there are prices to be increased or decreased then
the admin can update it.

iii.

Feedback: Administrator can view all feedbacks about the product given by
the user.

2.2.1.3 HARDWARE INTERFACES

Processor
:
Intel Pentium Duel CPU
PROCESSOR
:
DUAL CORE
RAM
:
4GB
STORAGE CAPACITY
:
500GB
Mouse Standard Mouse
Keyboard Logitech Keyboard
2.2.1.4 SOFTWARE INTERFACES
FRONT-END
:
PHP
BACK-END
:
MY SQL
OPERATING SYSTEM
:
WINDOWS 7//XP/8/8.1/10
Wamp Server 2.2e
2.2.1.5 COMMUNICATION INTERFACES
None
2.2.1.6 MEMORY CONSTRAINTS
At least 1GB RAM and 2GB space on hard disk will be required for running the
application.
2.2.1.7 OPERATIONS
This product will not cover any automated housekeeping aspects of database. The DBA at
client site will be manually deleting old/ non required data. Database backup and
recovery will also have to be handled by DBA.
2.2.1.8 SITE ADAPTATION REQUIREMENT
The terminals at client side will have to support the hardware and software interfaces
specified.

10

2.2.2

PRODUCT FUNCTIONS

The system will allow access only to authorized users with specific roles
(Administrator, Operator). Depending upon the users role, he/she will be able to
access only specific modules of the system. A summary of the major functions that
the software will perform:
i.

Login Facility :Used for the admin and users for login into the program. This provides various
facilities according to the type of user (admin or Customer).

ii.

Booking :This is also an essential function that handles all aspects of ordering the book.

iii.

Administration :This function allows the admin to define system parameters (i.e. Book
categories), manage and maintain any system setting. Another considerable
feature is:
Maintain Books(add/modify/delete)
iv. Users :Users can check and select the different categories of book and add those books
to the cart.

2.2.3

USER CHARACTERISTICS

1. Educational Level: At least graduate and should be comfortable with English language.
2. Technical Expertise: Should be a high or middle level employee of the organization
comfortable with using general purpose applications on a computer
2.2.4 CONSTRAINTS
None

11

2.2.5 ASSUMPTIONS AND DEPENDENCIES

Once a book is ordered it cant be cancelled like other online bookings.
Once a payment is done it cant be refundable.
2.2.6

APPORTIONING REQUIREMENT
Not Required

2.3 SPECIFIC REQUIREMENTS

This section contains the software requirements to a level of detail sufficient to enable
designers to design the system, and testers to test the system.
2.3.1 EXTERNAL INTERFACES
2.3.1.1 USER INTERFACES
The following screens will be provided:
2.3.1.2 HARDWARE INTERFACES
Processor
:
PROCESSOR
:
RAM
:
STORAGE CAPACITY
:
Mouse Standard Mouse
a. Keyboard Logitech Keyboard

Intel Pentium Duel CPU

DUAL CORE
4GB
500GB

2.3.1.3 SOFTWARE INTERFACES

FRONT-END
:
PHP
BACK-END
:
MY SQL
OPERATING SYSTEM
:
WINDOWS 7//XP/8/8.1/10
Wamp Server 2.2e

2.3.1.4 COMMUNICATION INTERFACES

None

12

2.3.2

SYSTEM FEATURES

We analyzed and conclude that project can be implemented using 3 major modules:1. Ordering Books: Using this module user can search about various books and know
the charges details for various types of books and order them.
i. Validity Checks:
a. Name should not blank.
b. Type must be specified.
c. User should enter address.
d. Age should be filled.
ii. Sequencing Information:
a. Firstly, user enter name.
b. After this user enter gender.
c. Then he/she enter address.
d. Then, user enter age.
iii.

Error Handling / Response to abnormal situations:

a. If user left any field blank then it shows an error alert box.
b. If booking is successful then it shows a message above form regarding successful
booking.
2.3.3
2.3.4

PERFORMANCE REQUIREMENTS
None
LOGICAL DATABASE REQUIREMENTS

The proposed information system contains the following data tables in its database
collection.
1.
2.
3.
4.
5.
2.3.5
2.3.6

User Table
Book Category Table
Book Sub-Category Table
Contact Table
Payment Table
DESIGN CONSTRAINT
2.3.5.1
STANDARD COMPLIANCE
None
SOFTWARE SYSTEM ATTRIBUTES
13

Reliability
This application is a reliable product that produces fast and verified output of all its
processes.
Availability
This application will be available to use for your end users and help them to carry out
their operations conveniently.
Security
The application will be password protected. User will have to enter correct username,
password and role in order to access the application.
Maintainability
The application will be designed in a maintainable manner. It will be easy to to
incorporate new requirements in the individual modules.
Portability
The application will be easily portable on any windows-based system that has oracle
installed
2.3.7

OTHER REQUIREMENTS
None

14

3. METHODOLOGIES FOR DATA COLLECTION

3.1 PRIMARY DATA COLLECTION
Data that has been collected from first-hand-experience is known as primary data.
Primary data has not been published yet and is more reliable, authentic and objective.
Primary data has not been changed or altered by human beings; therefore its validity is
greater than secondary data.

Primary sources can include

Interviews, diaries, letters, journals, speeches, autobiographies, and witness
statements.
Articles containing original research, data, or findings never before shared.
Government documents and public records.
Art, photographs, films, maps, fiction, and music.

3.2 SECONDARY DATA COLLECTION

Data collected from a source that has already been published in any form is called as
secondary data. The review of literature in nay research is based on secondary data.
Mostly from books, journals and periodicals. Secondary sources can include
Textbooks
Review articles and critical analysis essays
Biographies
Historical films, music, and art
Articles about people and events from the past
Secondary data is mainly used for this project

15

4. METHODOLOGY USED FOR ANALYSIS, DESIGN AND DEVELOPMENT

SDLC
SDLC Stands for Software Development Lifecycle Model. Software Development Life
Cycle, or Software Development Process, defines the steps/ stages/ phases in the building
of software. The development models are the various processes or methodologies that are
being selected for the development of the project depending on the projects aims and
goals. There are many development life cycle models that have been developed in order
to achieve different required objectives. The models specify the various stages of the
process and the order in which they are carried out. The selection of model has very high
impact on the testing that is carried out. It will define the what, where and when of our
planned testing, influence regression testing and largely determines which test techniques
to use. The Model that we prefer for our project is Iterative Waterfall Model.
4.1 STAGES OF MODEL
REQUIREMENT ANALYSIS AND SPECIFICATION PHASE:
The goal of this phase is to understand the exact requirement of the customer and to
document them properly. The requirement describe the what of a system not the how.
This phase produce a large document written in a natural language, contains a description
of what a system will do without describing how it will be done.
DESIGN:
The goal of this phase is to transform the requirements specification into a structure that
is suitable for implementation in some programming language. Here, overall software
architecture is defined, and the high level and detailed designed work is performed. This
work is documented and known as software design description (SDD) document.
IMPLEMENTATION AND UNIT TESTING PHASE:
During this phase design is implemented. If the SDD is complete, the implementation and
Coding phase proceeds smoothly, because all the information needed by the software
developers is contained in SDD.
16

INTEGRATION AND SYSTEM TESTING PHASE:

This is very important phase the purpose of unit testing is to determine that each
independent module correctly implemented, to determine that the interface between
modules is also correct, and for this reason integration testing is performed. System
testing involves the testing of the entire system, whereas software is a part of system.
OPERATION AND MAINTENANCE PHASE:
Software maintenance is a task that every development group has to face. When the
software is delivered to the customer site, install and is operational. Therefore the release
of the software inaugurates the operations and maintenance phase of the lifecycle.
4.2 BLOCK DIAGRAM OF ITERATIVE WATERFALL MODEL

Figure 2.1: Iterative Waterfall Model

17

4.3 REASONS FOR CHOOSING MODEL

This model is simple and easy to understand and use.
It is easy to manage due to the rigidity of the model each phase has specific
deliverables and a review process.
In this model phases are processed and completed one at a time. Phases do not
overlap.
It works well for smaller projects where requirements are very well understood.
5 PROJECT PLANNING AND SCHEDULING :
This planning Gantt chart shows that how the work is done ,on which date it was
completed and how the work is sequenced .This planning makes it easy to know that how
much time a particular work will require.

Fig 2.2(a) Gantt chart of Bookstore Management System

18

Fig 2.2(b) Gantt chart of Bookstore Management System

19