Book Store Srs

1. Introduction The document aims at defining the overall software requirements for online book store. Efforts have been made to define the requirements exhaustively and accurately. accurately.

1.1 Purpose This specification document describes the capabilities that will be provided by the software application ‘online book store’. t also states the various required constraints by which the system will abide. The intended audience for this document are the development team! testing team and end users of the product.

1.2 Scope The software system being produced is called online book store .t is  being produced for a customer customer interested interested in selling books via the nternet. The "ook E#$ommerce %ystem will allow any user to create an account to become a customer. customer. The customer! through the process of account creation! will have the option to  become a member of the site. The The system will will allow customers customers to browse! search! search! select! and add books to a shopping cart. Then! provided they have books in their shopping cart! check out books in shopping cart and decrement the stock that the inventory the system maintains. The system also allows a manager to manage the inventory with full create! retrieve! update and delete functionality with regards to books in the system.

1.3 Definitions, Abbreviations and Acronyms SRS# %oftware &equirement %pecification OBS online book store !ustomer# ' person who is purchasing book  Administrator"Admin# (ser having all the privileges to operate )"% Staff # %taff of the university operating (&% and coordinating the admissions

1.# References 

  *)b+ect )b+ect )riented %oftware Engineering by ,ogesh ,ogesh %ingh and &uchika -alhotra! / 0earning private 0imited!21    *EEE EEE &ecommended ractice for %oftware &equirement %pecifications# %pecifications# EEE standard 342#1553    *EEE EEE standard for software test documentations#EEE standard 3561553

1.$ Overvie% The %&% is divided into three ma+or sections introduction! overall description and specific

2. Re&uirements

2.1 Product Perspective The )nline %hopping %ystem shall be developed using client server architecture and will  be compatible with -icrosoft 7indows operating system. 8ront end of the system will be developed using /T-09! $%%! +ava%cript! bootstrap the back and will be developed using /

2.1.1 System interfaces (niversity :atabase; t contains student’s and staff’s details like branch! program! role! etc 2.1.2 'ser interfaces The )nline %hopping ortal will have the following user friendly and menu driven interfaces; 1. 0ogin; 'llow the entry of )nly authorised users through valid login : and password. . 'dd to $art; To allow customer to add item to cart. 4. Edit $art; To allow member to edit the information of products. <. $heckout; To allow customer to make payment. 2.1.3 (ard%are interfaces 1. %creen resolution of at least =<2>< 32 or above. . %upport for printer. 4. $omputer system with nternet connections. 2.1.# Soft%are interfaces 1. -icrosoft 7indows operating system. . ' web browser? chrome! firefox etc@. 2.1.$ !ommunication interfaces n )"%! communication is via 7'A? 7ide 'rea Aetwork @ 2.1.) *emory !onstraints 't least 91 -" &'- and 922 -" space of hard disk will be required to run the software. 2.1.+ Operations

This product release will not cover any automated housekeeping aspects of the database. The administrator at the client site ?i.e. (niversity@ will be responsible for manually deleting old6non#required data. :atabase backup and recovery will also be handled by administrator. /owever! the system will provide a ‘&eset %ystem’ function that will delete ?upon confirmation from the 'dministrator@ all the existing information from the database. 2.1. Site adaptation re&uirements n the (&%! the terminal at the client side will have to support the hardware and software nterfaces specified

2.2 Product functions The )nline %hopping ortal will allow access only to the authorised users with specific roles? system administrator! customer!member@. :epending upon the users role! he 6she will be able to access only specific modules of the system. ' summary of ma+or functions that the )nline %hopping ortal shall perform includes; 1. 0ogin facility for enabling only authorised access to the system. . %ystem administrator will be able to add modify delete view product! 4. The customer will be able to item to cart.

2.3 'ser c-aracteristics Bualification; 't least matriculation and comfortable with English. Experience; %hould be well versed about the process of (niversity library. Technical experience; Elementary knowledge of computers.

2.# !onstraints 1. The software does not maintain records of periodicals. . There will be only one administrator. 4. The user will not be allowed to update the user id. <. To reduce the complexity of the system! there is no check on delete operation. 9. The administrator should be very careful before editing of any product.

2.$ Assumptions and dependencies 1. The academic section will provide the list of admitted students. . The login : and password must be created by system administrator and communicated to concerned users to avoid unauthorised access to the system. 4. The acquisition section of the library will provide the list of the books purchased by the library.

2.) Apportionin of Re&uirements

 Ao such requirement

4.Specific Re&uirements This section contains the software requirements in detail along with the various forms to  be developed. 3.1 /0terna Interfaces Re&uirements

!AR PROOP/4

BRO5S/ I67/6OR

8O9I6 PA9/

BOO: 8ISI69

3.2 ;unctions

3.3 Performance Re&uirements    *%hould run on 1 C/D! 91 -" &'- machine   *&esponses should be within  seconds  3.# Desin constraints  Aone 3.$ Soft%are System Attributes    *'sabiity The application will be user friendly and easy to operate and the function will be easily understandable    *Reiabiity The application will be available to the candidates through the registration period and have a high degree of fault tolerance    *Security The application will be password protected. (sers will have to enter correct login : and password to access the application    **aintainabiity The application will be designed in a maintainable manner. t will be easy to incorporate new requirements in the individual modules    *Portabiity The application will be easily portable on any windows based system with a modern web browser  3.) 8oica Database Re&uirements The following information will be placed in a database ; abe name Description 0ogin &ecords the login details of the user : and password %tudent &ecords the details of the student %taff &ecords the details of the staff  "ranch &ecords the branch status  Aotification &ecords all the notifications generated 3.+ Ot-er Re&uirements  Aone