Software Requirements Specification

Version: 1.0

Book Rental System

Software Requirements Specification

Software Requirements Specification

Version: 1.0

Revision History
Date 05/06/11 Revision 1.0 Description Initial Version Author Team

ii

Contents
1.INTRODUCTION...........................................................................................................................................IV 2.SYSTEM CONTEXT.......................................................................................................................................V 3GENERAL REQUIREMENTS.....................................................................................................................VII 3.2SOURCE SYSTEM REQUIREMENTS.................................................................................................VIII 4SYSTEMS MANAGEMENT AND MONITORING...................................................................................IX 5DISASTER CONTINGENCY SOLUTION..................................................................................................IX 6EFFECT OF THE SOLUTION......................................................................................................................IX

System Requirements Specification

Version: 1.0

1. Introduction
This document contains the Software Requirements Specification (SRS) of an Book Rental System. The main aim of this project is to provide automation to all operations in a book shop.

1.1

Purpose
The SRS contains the complete description of the software requirements for the Book Rental System. It provides insight to the design and information needed for software support.

1.2 Scope
The Book Rental System is developed for the XRU book shop to improve the current inventory process. Here we are try to develop such type system which is provide the automation on the any type of the bookshop. That means a shop which has the type system which provides the facility to the customers of the shop to purchase the books from the shop without any complexity. For example any customer want to purchase any book from the shop than first of all customer just choose the stream of the book than he/she can see the more than one type of books there and then he/she can choose the specific book from there. And then purchase it by paying price on bookshop cash counter and receives its invoice

1.3 Assumptions
User has basic knowledge of computer and English.

1.4 1.5

Dependencies
There is no dependency

Contacts Technical Contacts

System name Book Rental System Contact Name xyz Telephone 201-675-7841 Email sanjacob2004@gmail.com

Business Contacts
System name Book Rental System Contact Name Mr. Philip Wlazlo Telephone 212-998-3513 Email pwlazlo@nyu.edu

1.6

References
Name Stakeholder Request Author pqr Version 1.0 Date 05/06/2011

iv

System Requirements Specification

Version: 1.0

2.

System Context

Almost every activity in the world today is controlled by computer driven software programs. His trend was first accommodated by engineering applications in the past. However, as the life style became more and more complex, every area of human interactions was invaded by various software systems, such as real time, business, simulation, embedded, web based, personal and more recently, artificial intelligence software etc. According to the above facts, managing and maintaining a book shop could also be controlled by efficient software. This project focuses attention on designing efficient and reliable software which controls the transactions of a bookshop. In real world, it tends to associate with automated systems as they provide many benefits than doing the same thing in manually. As above mentioned, here we have introduced a system which can be used to maintain a bookshop. When we are concerning the manual process of a bookshop, the major problem is the waste of time. A customer has to waste his/her valuable time when he needs to buy a book as all the events such as searching, purchasing are done by members of the staff .In briefly, the manual process is very slow. But automation will reduce the time taken in the whole process. In a bookshop we should deal with a large store. Then person (storekeeper) has to maintain it with documents which are recorded by him. Therefore, there may be defective reports. Also company has to appointed more persons to complete the maintenance of the stationery. Then the company has to have an additional cost.

2.1 Current State

An example of a process/data flow diagram

System Requirements Specification

Version: 1.0

2.2 Future State

Book shop automation system (BAS): BAS should help the customers query whether a book in a stock the user can query the availability of a book either by using the book title or by using the name of author. If the book is not currently sold by the bookshop, then the customer is asked to enter the full detail of the book for procurement of the book by the bookshop. The customer can also provide his e-mail address and mobile, so that he can be intimated automatically by the software as and when the book copy received. If a book not in the stock, the query for the book is used to increment a request field for the book. The manager can periodically view the request field of the book arrive at a rough estimate regarding the current demand for different books. BAS should maintain the price of various books. As soon as customer selects his book for purchase, the sale clerk would enter the ISBN number of the books. BAS should update the stock BAS should allow employees to update inventory whenever new supply arrives. Also upon request by the owner of book shop. BAS should generate sales statistics (viz, book name, publisher, ISBN number, number of copies sold and the sales revenue) for any period.

vi

System Requirements Specification

Version: 1.0

2.3 Feasibility Study

Feasibility study is the measure of how beneficial or practical the development of an information system will be to an organization. The Feasibility analysis is a cross life cycle activity and should be continuously performed throughout the system life cycle. Feasibility tests; Operational feasibility: By automating the book shop both the customers and employees will feel better than when it was manual. Users will get a very quick service by reducing the manual recordings. Also employees will feel comfortable by reduction of their work. Recording errors will be reduced. Easy to handle a large database. Losing of records will be avoided. Considering all these factors we can conclude that all the users and end users will be satisfied by the system. Technical feasibility: For the design and development of the system, several software products have been accommodated. Database design MS Access. Interface design .NET Framework. Coding C# or any other supported Language. This softwares have the enough efficiency in producing the system. Therefore the project is technically feasible. Schedule feasibility: The duration of time required for the project has been planned appropriately and it is the same as the duration of time expected by the customer.

General Requirements
3.1General Functional Requirements
General Functional Requirements Interactive System Secure login Description System should be interactive and easy to use for students and staff members User should be able to securely login in the system.

vii

System Requirements Specification

Version: 1.0

General Functional Requirements Purchase Book Request for new password Search Book/Customer/publisher Add book/category/customer/publis her Rent a book Return a book

Description Customer should be able to purchase book Administrator should be able to reset the password. User should be able to search for the book, customer or publisher As per inventory management store supervisor able to add book/category/customer and publisher If book available in the store customer should be able to rent the book When a book is returned the store supervisor should be able to record it in the inventory Various Report based on different criteria should be made available Administrator should be able to add a new user

Report Generation Add New User

3.2 Source System Requirements

Requirement Type System Pre-Processing System Connectivity System Error Handling Description This will relate to business processes/jobs which should run to populate the source tables/files. The online system would be a web application and would be connected to the university database. Error handling should be taken care of and appropriate user friendly errors should be displayed

3.3 Non Functional Requirements

Non-Functional Requirements Language Support Fault tolerance Scalability Description System should be easy to operate for users with knowledge of basic English. User should be able to access the system 24*7; except during scheduled maintenance. The system should be able to handle 10,000 users simultaneously

viii

System Requirements Specification

Version: 1.0

Non-Functional Requirements Response Time

Description Response time of the system should be less than 0.1ms

3.4 Security Requirements

Security Requirements Integrity Requirements Privacy Requirements Access Requirements Description Data integrity should be assured by limiting access to the database and by appropriate synchronization and back-up functionalities. The users privacy will be granted by the limited access that the log-in process is going to give. Every user must have secure and private access to his/her data.

4 Systems Management and Monitoring

The system and external documents need to be updated constantly according to necessities of stakeholder. The system and database should be available 24/7 to the users. System should be able to manage all data coming from the database.

5 Disaster Contingency Solution

Re-process data from the previous successful run of the interface. In all cases, a recovery and/or reconciliation process must be outlined as well for when services resume.

6 Effect of the solution

It may be difficult to allow exceptions During heavy technical issues system may cause issue in inventory management and manual entry may be required Even though these advantages prevail, due to lack of IT literacy and fluency of clients and lack of distribution of internet facility will have a negative impact and it will take some time to cover up the capital investment made on implementing the new system. Since the technical facilities are expanding in great heaps, proposed system will facilitate enhancing productivity immensely.

ix