• Introduction

– Purpose
– Scope
– Definition, Acronyms and abbreviations
– References
– Overview
• The Overall Description
– 2.1 Product Perspective
• System Interfaces
• Hardware Interfaces
• Software Interfaces
• Communication Interfaces
• Memory Constraints
• Operations
• Site Adaptation Requirements
 – Product Functions
– User Characteristics
– Constraints
– Assumptions for dependencies
• Specific Requirements
– External Interfaces
– Functions
– Performance requirements
– Logical database requirements
– Design Constraints
– Software System attributes
– Organization of specific requirements
– Additional Comments.
• 1. INTRODUCTION

1.1 PURPOSE
The main objective of this document is to illustrate the requirements of the
project Library Management system. The document gives the detailed description
of the both functional and non-functional requirements proposed by the
client.The purpose of this project is to provide a friendly environment to maintain
the details of books and library members.The main purpose of this project is to
maintain easy circulation system using computers and to provide different reports.
This project describes the hardware and software interface requirements using ER
diagrams and UML diagrams.
• 1.2 SCOPE
Library Management System is basically updating the manual library system into
an internet-based application so that the users can know the details of their
accounts, availability of books and maximum limit for borrowing. The project is
specifically designed for the use of librarians and library users. Library
Management System can be used by any existing or new library to manage its
books and book borrowing, insertion and monitoring. It is especially useful for any
educational institute where modifications in the content can be done easily
according to requirements. We can add new features as and when we require,
making reusability possible as there is flexibility in all the modules.
• 1.3 Definition, Acronyms, Abbreviation:

• 1.4 References
• Books Software Requirements and Specifications:
• A Lexicon of Practice, Principles and Prejudices (ACM Press) by Michael
Jackson Software Requirements (Microsoft) Second EditionBy Karl E. Wiegers
Software Engineering: A Practitioner’s Approach Fifth Edition By Roger S.
Pressman
• Websites http://www.slideshare.net/ http://ebookily.net/doc/srs-library-
management-system

1.5 OVERVIEW
SRS includes following sections overall description and specific requirements
• Overall Description will describe major role of the system
components and inter-connections.
• Specific Requirements will describe roles & functions of the actors.
• Appendix Appendices may be used to provide additional (and hopefully
helpful) information.
• Index: An index is an alphabetical list with page numbers that refer to all
the major topics in a document.
• 2. OVERALL DESCRIPTION
• 2.1 PRODUCT PRESPECTIVE
The proposed Library Management System will take care of the current book detail at any
point of time. The book issue, book return will update the current book details
automatically so that user will get the update current book details.
• 2.2 Product function
• The main purpose of this project is to reduce the manual work. This software is capable of
managing Book Issues, Returns, Calculating/Managing Fine, Generating various Reports
for Record-Keeping according to end user requirements. The administrator will control
members and manage books. The member’s status of issue/return is maintained in the
library database. The member’s details can be fetched by the librarian from the database
as and when required. The valid members are also allowed to view their account
information.
SOFTWARE REQUIREMENT
Front end: HARDWARE REQUIREMENT
Android version Android developer tool
• Advance java 2GB ram
1.2 GHz processor Windows 7/8/8.1/10
Intel i5

Back end:
• MySQL
• 2.3USER CHARACTERSTICS
The system provides different types of services based on the type of users
[Member/Librarian]. The Librarian will be acting as the controller and he will have
all the privileges of an administrator. The member can be either a student or staff
of the university who will be accessing the Library online.
• The features that are available to the Librarian are:-
• A librarian can issue a book to the member.
• Can view the different categories of books available in the Library
• Can view the List of books available in each category
• Can take the book returned from students
• Add books and their information to the database
• Edit the information of existing books
• Can check the report of the existing books
• Can check the report of the issued books
• Can access all the accounts of the students

• The features that are available to the Members are:-

• Can view the different categories of books available in the Library
• Can view the List of books available in each category
• Can own an account in the library.
• Can view the books issued to him
• Can put a request for a new book
• Can view the history of books issued to him previously
• Can search for a particular book
 2.4 CONSTRAINTS
Any update regarding the book from the library is to be recorded to have
update & correct values, and any fine on a member should be notified as
soon as possible and should be correctly calculated.

2.5 ASSUMPTIONS AND DEPENDENCIES

• The assumptions are:-
• The coding should be error free
• The system should be user-friendly so that it is easy to use for the users
• The information of all users, books and libraries must be stored in a
database that is accessible by the website The system should have more
storage capacity and provide fast access to the database
• The system should provide search facility and support quick transactions
• The Library System is running 24 hours a day
• Users may access from any computer that has Internet browsing
capabilities and an Internet connection
• Users must have their correct usernames and passwords to enter into
their online accounts and do actions
• 3 SPECIFIC RQUIREMENTS
• FUNCTIONAL REQUIREMENT
R.1:Register
• Description : First the user will have to register/sign up. There are two
different type of users.
The library manager/head : The manager have to provide details about
the name of library,address, phone number, email id.
Regular person/student : The user have to provide details about his/her
name of address,phone number, email id.

• R.1.1: Sign up
Input: Detail about the user as mentioned in the description.
Output: Confirmation of registration status and a membership number
and password will be generated and mailed to the user.
Processing: All details will be checked and if any error are found then an
error message is displayed else a membership number and password will
be generated.
R.1.2 : Login
Input: Enter the membership number and password provided.
Output : User will be able to use the features of software.
R.2 : Manage books by user.
R.2.1 : Books issued.
Description : List of books will be displaced along with data of return.
R.2.2 : Search
Input : Enter the name of author's name of the books to be issued.
Output : List of books related to the keyword.
R.2.3 : Issues book
State : Searched the book user wants to issues.
Input : click the book user wants.
Output : conformation for book issue and apology for failure in issue.
Processing : if selected book is available then book will be issued else error will be
displayed.
R.2.4 : Renew book
State : Book is issued and is about to reach the date of return.
Input : Select the book to be renewed.
Output : conformation message.
Processing : If the issued book is already reserved by another user then error message will
be send and if not then conformation message will be displayed.
R.2.5 : Return
Input ; Return the book to the library.
Output : The issued list will be updated and the returned book will be listed out. R.2.6 ;
Reserve book
Input ; Enter the details of the book.
Output : Book successfully reserved.
Description : If a book is issued by someone then the user can reserve it ,so that later the
user can issue it.
• R.2.6 Fine
Input : check for the fines.
Output : Details about fines on different books issued
by the user.
Processing : The fine will be calculated, if it crossed
the date of return and the user did not
renewed if then fine will be applied by Rs 10 per day.
R.3 Manage book by librarian
R.3.1 Update details of books
R.3.1.1 Add books
Input : Enter the details of the books such as
names ,author ,edition, quantity.
Output : confirmation of addition.
R.3.1.2 Remove books
Input : Enter the name of the book and quantity of
books.
Output : Update the list of the books available
• 2.4.2 Non Functional Requirements
• Usability Requirement
The system shall allow the users to access the system from the phone using
android application. The system uses a android application as an interface. Since
all users are familiar with the general usage of mobile app, no special training is
required. The system is user friendly which makes the system easy.
• Availability Requirement
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.
• Efficiency Requirement
Mean Time to Repair (MTTR) - Even if the system fails, the system will be
recovered back up within an hour or less.
• Accuracy
The system should accurately provide real time information taking into
consideration various concurrency issues. The system shall provide 100% access
reliability.
• Performance Requirement
The information is refreshed depending upon whether some updates have
occurred or not in the application. 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. Responses to view
information shall take no longer than 5 seconds to appear on the screen.
• Reliability Requirement
The system has to be 100% reliable due to the importance of data and the
damages that can be caused by incorrect or incomplete data. The system will run 7
days a week, 24 hours a day