You are on page 1of 13



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.
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









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


DEFINITION. 8 . ABBREVIATIONS DFD : Data Flow Diagram ER : Entity Relationship PHP : Hypertext Pre-processor SRS : Software Requirements Specification REFERENCES www.2. 2.  The application can be accessed 2.1. and Download E-books. ACRONYMS.2 OVERALL DESCRIPTION OF PROPOSED SYSTEM 2.2.  The web application should tie up with the “verified by visa” and “VeriSign” organizations for far more secure transactions. Download E-books or cancel a particular Book ordered and also provide the cost of Books. The name of the project is “Bookstore Management System”.google.1.seminarproject. features and functionality in detail. self-contained and independent software product.K.3     2.1. This will provides option for viewing different books available with different categories and provide customers with the facility to order a book.wikipedia. Aggarwal .1 PRODUCT PERSPECTIVE The application will be windows-based. www. Yogesh Singh www.1.scribd.2 SCOPE  The web application should be able to remember the preference of a user like remembering his billing and shipping Books: Software Engineering book by The rest of this SRS document describes the various system requirements. cancel a particular ordered book.4      by anyone anywhere.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.

HTML. Following screens will be provided.1 SYSTEM INTERFACES None 2.2 INTERFACES The application will have a user friendly and menu based interface. 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. Book Category: User can search different kind of book from book category. Role of administrator: i.1. (ii) Access to different screens will be based upon the role of the user and administrator as below: Roles of user:i. iii. ii. Feedback: Administrator can view all feedbacks about the product given by the user. password for Administrator and customer.1.2. (i) A Login Screen for entering username. Update prices: In any case if there are prices to be increased or decreased then the admin can update it. JAVASCRIPT SQL 2.PHP. ii.2. CSS. 9 . Add/Remove Book Details: Administrator can direct interact with the database so he/she can add or remove the new book from database.

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

2. Administration :This function allows the admin to define system parameters (i. Users :Users can check and select the different categories of book and add those books to the cart.2. 2.2. ii. A summary of the major functions that the software will perform: i. Operator). manage and maintain any system setting. he/she will be able to access only specific modules of the system.2 PRODUCT FUNCTIONS The system will allow access only to authorized users with specific roles (Administrator. Login Facility :Used for the admin and users for login into the program. Book categories). This provides various facilities according to the type of user (admin or Customer). Technical Expertise: Should be a high or middle level employee of the organization comfortable with using general purpose applications on a computer 2.2. Educational Level: At least graduate and should be comfortable with English language. Booking :This is also an essential function that handles all aspects of ordering the book.3 USER CHARACTERISTICS 1.4 CONSTRAINTS None 11 . Depending upon the user’s role. Another considerable feature is:  Maintain Books(add/modify/delete) iv. 2. iii.e.

1 EXTERNAL INTERFACES 2.1 USER INTERFACES The following screens will be provided: 2.1/10 Wamp Server ASSUMPTIONS AND DEPENDENCIES  Once a book is ordered it can’t be cancelled like other online bookings.2e 2. Keyboard – Logitech Keyboard     Intel Pentium Duel CPU DUAL CORE 4GB 500GB 2.1.3. and testers to test the system.3 SOFTWARE INTERFACES FRONT-END : PHP BACK-END : MY SQL OPERATING SYSTEM : WINDOWS 7//XP/8/8.1.3.  Once a payment is done it can’t be refundable.3. 2. 2.1.2 HARDWARE INTERFACES  Processor :  PROCESSOR :  RAM :  STORAGE CAPACITY :  Mouse – Standard Mouse a.3 SPECIFIC REQUIREMENTS This section contains the software requirements to a level of detail sufficient to enable designers to design the system.1.4 COMMUNICATION INTERFACES None 12 .3.2.6 APPORTIONING REQUIREMENT Not Required 2.

3. Firstly. 1. 2. 2.3.5 2. c. b. iii. User should enter address. Then he/she enter address. b. user enter age. ii.4 PERFORMANCE REQUIREMENTS None LOGICAL DATABASE REQUIREMENTS The proposed information system contains the following data tables in its database collection. If user left any field blank then it shows an error alert box. Error Handling / Response to abnormal situations: a. If booking is successful then it shows a message above form regarding successful booking. Validity Checks: a.2 SYSTEM FEATURES We analyzed and conclude that project can be implemented using 3 major modules:1. d.3 2. Sequencing Information: a.3.3. 4.5. c. b. 2. Then. 5. 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.3. user enter name. Age should be filled.6 User Table Book Category Table Book Sub-Category Table Contact Table Payment Table DESIGN CONSTRAINT 2.1 STANDARD COMPLIANCE None SOFTWARE SYSTEM ATTRIBUTES 13 . d.3. Name should not blank. Type must be specified.2.3. After this user enter gender.

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

letters. Mostly from books. and witness statements. music. » Government documents and public records. autobiographies.3. journals and periodicals. 3.1 PRIMARY DATA COLLECTION Data that has been collected from first-hand-experience is known as primary data. METHODOLOGIES FOR DATA COLLECTION 3. diaries. maps. and music. Secondary sources can include » Textbooks » Review articles and critical analysis essays » Biographies » Historical films. speeches. » Art. journals. Primary data has not been published yet and is more reliable. fiction. The review of literature in nay research is based on secondary data. authentic and objective. Primary data has not been changed or altered by human beings. or findings never before shared. films. and art » Articles about people and events from the past » Secondary data is mainly used for this project 15 . photographs. » Articles containing original research.  Primary sources can include » Interviews.2 SECONDARY DATA COLLECTION Data collected from a source that has already been published in any form is called as secondary data. therefore its validity is greater than secondary data. data.

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

and for this reason integration testing is performed. to determine that the interface between modules is also correct.1: Iterative Waterfall Model 17 . Therefore the release of the software inaugurates the operations and maintenance phase of the lifecycle.INTEGRATION AND SYSTEM TESTING PHASE: This is very important phase the purpose of unit testing is to determine that each independent module correctly implemented. 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. System testing involves the testing of the entire system. whereas software is a part of system.2 BLOCK DIAGRAM OF ITERATIVE WATERFALL MODEL Figure 2. install and is operational. 4.

 It works well for smaller projects where requirements are very well understood.4. 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 .  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.3 REASONS FOR CHOOSING MODEL  This model is simple and easy to understand and use. Fig 2.This planning makes it easy to know that how much time a particular work will require.2(a) Gantt chart of Bookstore Management System 18 .

2(b) Gantt chart of Bookstore Management System 19 .Fig 2.