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.
1.1 Purpose
This specification document describes the capabilities that will be provided by the software
application ‘online book store’. It 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 .It is
being produced for a customer interested in selling books via the Internet. The Book E-Commerce System will allow any user to create an account to become a customer. The customer, through the process of account creation, will have the option to become a member of the site. The system will allow customers to browse, 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- Software Requirement Specification OBS- online book store
Customer- A person who is purchasing book
Administrator/Admin- User having all the privileges to operate OBS Staff- Staff of the university operating URS and coordinating the admissions
1.4 References
Object Oriented Software Engineering by Yogesh Singh and Ruchika Malhotra, PHI
Learning private Limited,2012
IEEE Recommended Practice for Software Requirement Specifications- IEEE standard
830-1998
IEEE standard for software test documentations-IEEE standard 829/1998
1.5 Overview
The SRS is divided into three major sections introduction, overall description and specific
2.1 Product Perspective
The Online Shopping System shall be developed using client server architecture and will be compatible with Microsoft Windows operating system. Front end of the system will be developed using HTML5, CSS, javaScript, bootstrap the back and will be developed using PHP
2.1.1 System interfaces
University Database: It contains student’s and staff’s details like branch, program, role, etc
2.1.2 User interfaces
The Online Shopping Portal will have the following user friendly and menu driven interfaces:
1. Login: Allow the entry of Only authorised users through valid login ID and password. 2. Add to Cart: To allow customer to add item to cart.
3. Edit Cart: To allow member to edit the information of products. 4. Checkout: To allow customer to make payment.
2.1.3 Hardware interfaces
1. Screen resolution of at least 640*4 80 or above. 2. Support for printer.
3. Computer system with Internet connections.
2.1.4 Software interfaces
1. Microsoft Windows operating system. 2. A web browser( chrome, firefox etc). 2.1.5 Communication interfaces
In OBS, communication is via WAN( Wide Area Network )
2.1.6 Memory Constraints
At least 512 MB RAM and 500 MB space of hard disk will be required to run the software.
This product release will not cover any automated housekeeping aspects of the database. The
administrator at the client site (i.e. University) will be responsible for manually deleting old/non-required data. Database backup and recovery will also be handled by
administrator.
However, the system will provide a ‘Reset System’ function that will delete (upon confirmation from the Administrator) all the existing information from the database.
2.1.8 Site adaptation requirements
In the URS, the terminal at the client side will have to support the hardware and software Interfaces specified
2.2 Product functions
The Online Shopping Portal will allow access only to the authorised users with specific roles( system administrator, customer,member). Depending upon the users role, he /she will be able to access only specific modules of the system.
A summary of major functions that the Online Shopping Portal shall perform includes: 1. Login facility for enabling only authorised access to the system.
2. System administrator will be able to add modify delete view product, 3. The customer will be able to item to cart.
2.3 User characteristics
Qualification: At least matriculation and comfortable with English.
Experience: Should be well versed about the process of University library. Technical experience: Elementary knowledge of computers.
2.4 Constraints
1. The software does not maintain records of periodicals. 2. There will be only one administrator.
3. The user will not be allowed to update the user id.
4. To reduce the complexity of the system, there is no check on delete operation. 5. The administrator should be very careful before editing of any product.
2.5 Assumptions and dependencies
1. The academic section will provide the list of admitted students.
2. The login ID and password must be created by system administrator and communicated to concerned users to avoid unauthorised access to the system.
3. The acquisition section of the library will provide the list of the books purchased by the library.
No such requirement
3.Specific Requirements
This section contains the software requirements in detail along with the various forms to be developed.
3.1 External Interfaces Requirements
CART PROTOTYPE:
LOGIN PAGE
3.3 Performance Requirements
Should run on 1 GHz, 512 MB RAM machine
Responses should be within 2 seconds
3.4 Design constraints
None
3.5 Software System Attributes
Usability
The application will be user friendly and easy to operate and the function will be easily understandable
Reliability
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. Users will have to enter correct login ID and password to access the application
Maintainability
The application will be designed in a maintainable manner. It will be easy to incorporate new requirements in the individual modules
Portability
The application will be easily portable on any windows based system with a modern web browser
3.6 Logical Database Requirements
The following information will be placed in a database :
Table name Description
Login Records the login details of the user ID and password Student Records the details of the student
Staff Records the details of the staff Branch Records the branch status
Notification Records all the notifications generated
3.7 Other Requirements
