System Requirement Specification

1. INTRODUCTION
This document aim at defining the overall requirement of Library Management System. Efforts have been made to define the requirements exhaustively and accurately. The final product will have only those features which have been mentioned in this document. No other features will be added by developer or anyone other for addition features a formal change request will need to be raised.

1.1 Purpose
This document helps in making Library Management System software. All the work done earlier manually on paper will be done on computer helps to keep proper records and give security to each book and members. This document is intended for the following group of people: Librarian to keep record of book. Easy to maintain records of member. Fine collection become easily. Reduces time for searching of books.

1.2 Scope
This software helps all to keep records of book coming in library and going out of library. This software keep track of all books, record of each member like their address, phone number, number of book issued and returned, fine caused by late return of book etc. It supports over 30 languages and adds more every day. The software is expected to complete in the duration of seven months and the estimated cost is Rs.5 lakhs.

1.3 Definition, Acronyms, and Abbreviations.

Internet An interconnected system of networks that connects computers around the world via the TCP/IP protocol. MB Ms Sec SRS TCP/IP E-mail MTBF MTTR SMS Mega Bytes. Milliseconds. Seconds. Software Requirements Specification. Transmission Control Protocol/Internet Protocol. Electronic mail. Mean Time Between Failures Mean Time to Repair
Short Message Service

1.4 References
www.google.com www.wikipedia.com Software Engineering by- K.K.Aggarwal

1.5 Overview
Section 1.0 discusses the purpose and scope of the software. Section 2.0 describes the overall functionalities and constraints of the software and user characteristics.

Section 3.0 details all the requirements needed to design the software.

2. THE OVERALL DESCRIPTION 2.1 Product Perspective

Library management is both web based and without web based application that allows member to check their status online or check their status in library This software is the easiest and most flexible online for keeping record of book and track of their members. This software provides the facilities to do bar code checking, to check whether the book is of this library or not. Procedure is easy to use and fast in nature. This software also provides real time statistics of the availability of book in library. This software provides a unique login id and encrypted password to each individual to protect privacy of the users. Many times unauthorized attempt of login will send email and sms to user mobile.

2.2 Product Functions

The major function that the software will performs are described as follows:

1. Multiliguistic: The user/viewer has the choice to choose

his/her preferential language from 40+ languages and more updated daily. All the page content is automatically transformed to the language selected by the user. User also has the freedom to switch to a different language mentioned in the list in between that session.

2. Secure Online Account Management: The user is

provided with a unique account and encrypted password only provided to the user and the administrator. The various functions that can performed by the user with his/her account are as follows: Notification: The user can activate notifications options to allow the software to notify the user about returning of book on time, pay fine and other such details. Secure Account: Each user account will we kept secure and their private detail will not be given to anyone except administrator when asked by them. Many times unauthorized login will send user email and sms on their phone about this unauthorized login.

3. Maintain Proper Record: Record of each books

will kept properly like when book came to library first, year of publication, author, price, book name and other details. It also keeps proper detail record of each user like which book issued by them, when they returned to library fine etc.

4. Query Processing:
Real time searching (Book availability can be searched on internet show the availability of book in library and tells when it will be coming to library back again). Search can be performed on the bases of author, book name, year of publish. Substrings will be allowed in search. Brief detail about each books will we given to sort out query of user.

2.3 User Characteristics

There are different kinds of users that will be interacting with the system. The intended user of the software is as follows:

Unregistered User/Novice: A novice or unregistered user is one who has little or no experience with the use of the web based application software to register online. This type of user will find it easy to access and use this software as each and every step is clearly illustrated in this software. This software is provided with instruction tips at every step in fully utilizing the software to its worth.

Registered User: A registered / experienced user, who is accustomed to the software and has been provided with a proper account and password, is provided with the proper details of user account like profile of user, details about issue of book, return of book, fine to be pay etc. details.

2.4. Constraints
The major constraints that the project has are as follows: Only one user will have access to the unique id provided to the user to login his/her account. The number of invalid login attempts must not exceed the limit of 4. If so happen the administrator will be notified and an automatic electronic mail will appear in the email address provided by the registered user also sms will be send to user on his mobile A user can issue only 3 books on his id The software should have a Java(TM) database.

 The software is a operational in Java platform requires Java(TM) 5. The software will have secured direct link access to the bank credit card transaction page to carry out fine transaction.

2.5 Assumptions and Dependencies

(I) Fine collection structure should does not change. (II) Number of books to be issued per member is 3 should not change. (III) Book should be returned within 10 days to avoid fine. (IV) The users have sufficient knowledge of computers. (V) The library computer should have Internet connection and Internet server capabilities.

3. SPECIFIC REQUIREMENTS: 3.1 External Interface Requirements 3.1.1 User Interface Requirements
The user interface provided should be very user-friendly one and it should provide an optional interactive help for each of the service listed. The interface provided is a provided a menu driven one and the following screens will be provided. 1. Login Screen: This will be first screen that will be displayed. It will allow user to access different screens based on users role. Various role provided on this screen will be (i) User ID: Alphanumeric length up to 10 characters. (ii) Password: Alphanumeric length up to 10 characters. (iii)Role: Will have following various role user and administrator.

1. A Welcome screen is provided to the user containing the two categoriesi) User Profile ii) Issue or returning of book record. 2. In the next screen the user is provided with various choicesFor user profile section: The options provided in the user profile panel are User personal details. Total fine paid. Book issued by user Notification The options provided in the Issue or returning of book panel are Return date of book Issue book detail Query about books 2. On selecting user profile panel user will see 3 options again. 3. In user profile details user will see all this details like name, address, phone number, date of birth, sex language etc. 4. Fine collected by user on which book will be shown in this column and in last there will be summation of total fine collected by that user. 5. Book issued or returned by user in past or in current time all that proper records are kept and user can see which book has been issued on which date by him. 6. Notification page will remind the member about returning of book on time and also about incoming of new books in library. 7. On selecting issue or return of book there will be 3 options.

8. Return date of each book will be shown separately so that user knows when to return back book to avoid fine. 9. Issue book page will show all the details about book like book name, author name, price of book, brief description about book and publication year. 10. Query of user will be sort out by administrator like when a new member come he\she does not know about fine structure basically it is a kind of forum which sort out question asked by member

3.1.2 Hardware Interface Requirements

The hardware requirements with which this software gives its optimal performance are

Hard disk Storage space 2 gb or greater available Network Card. A Display screen /Monitor with the screen resolution 640 X 480 or higher. PC with 300 megahertz or higher processor clock speed recommended. 128 megabytes (MB) of RAM or higher recommended (64 MB minimum supported. Keyboard and Mouse (compatible Pointing device).

3.1.3 Software Interface Requirements

In order to perform various different functions, this software needs to interact with various other software. So there are certain software interface requirements that need to be fulfilled which are listed as follows:

Windows 95/98 /XP/Vista/7, MAC OS is required. Internet Explorer or any other web browser to access the online account. Java JDK platform for software use. Java Servlet JSP engine for software login system.

Microsoft ASP.NET 2.0

3.1.4 Communication Interface Requirements

The software needs to communicate with the various banks where the payments are made, the transportation and the entertainment industries which issues the tickets and provide the various offers and updates. So, the following are the various communication interface requirements that are needed to be fulfilled in order to run the software successfully:

The system will employ dial-up POS with the central server for low cost communication. The communication protocol used shall be TCP/IP. Protocol used for data transfer shall be File Transfer Protocol. (FTP).

3.2 Software Product Features 3.2.1 Usability: The system will allow the users to access the system from the Internet using HTML or its derivative technologies. The system uses a web browser as an interface. Since all users are familiar with the general usage of browsers, no specific training is required. The system is user friendly and self-explanatory.

3.2.2 Reliability
The system will be very reliable due to the importance of data and the damages incorrect or incomplete data can do.

3.2.3 Availability
The system is available 100% for the user and is used 24 hrs. a day and 365 days a year. The system shall be operational 24 hours a day and 7 days a week.

3.2.4 Mean Time Between Failures (MTBF)

The system will be developed in such a way that on crash data does not get erased and it kept safe.

3.2.5 Mean Time to Repair (MTTR)

Even if the system crash, the system will be recovered back up within a 10 minutes or less.

3.2.6 Accuracy
The accuracy of the system is limited by the accuracy of the speed at which the employees of the library and users of the library use the system.

3.2.7 Maximum Bugs or Defect Rate

Not specified.

3.2.8 Access Reliability

The system shall provide 100% access reliability.

3.2.9 Performance 3.2.9.1 Response Time

The Splash Page or Information page should be able to be downloaded within a minute using a 56K modem. The information is refreshed every two minutes. The access time for a mobile device should be less than a minute. The system shall respond to the member in not less than two seconds from the time of the request submittal. The system shall be allowed to take more time when doing large processing jobs.

3.2.9.2 Administrator/Librarian Response

The system shall take as less time as possible to provide service to the administrator or the librarian.

3.2.9.3 Throughput
The number of transactions is directly dependent on the number of users. The users may be the Librarian, employees of the Library and also the people who use the Library for checking-out books, returning books and checking online library account.

3.2.9.4 Capacity
The system is capable of handling 250 users at a time.

3.2.10 Resource Utilization

The resources are modified according the user requirements and also according to the books requested by the users.

3.2.11 Supportability
The system designers shall take in to considerations the following supportability and technical limitations.

3.2.12 Internet Protocols

The system shall be comply with the TCP/IP protocol standards and shall be designed accordingly.

3.3. Performance Requirements

None

3.4. Design Constraint

None

3.5. Software System Attributes 3.5.1 Security

This application will be password protected .Users will have to enter correct username and password to access this application

3.5.2. Maintenance
This application will be designed in a maintenance manner. It will be easy to incorporate new requirements in the individual modules.

3.5.3. Portability
This application will be easily portable on any OS with a web browser to access to the web to update its data base real time.

3.6 Logical Database requirements:

The following information will be placed in database.

3.7 Other Requirements:

None