LIBRARY MANAGEMENT

SYSTEM

SRS
 PROJECT NAME: Library Management System
 INTRODUCTION
 BUSINESS REQUIREMENT OVERVIEW
 ASSUMPTIONS AND CONSTRAINTS
 FUNCTIONAL REQUIREMENTS
 USABILITY REQUIREMENTS
 PERFORMANCE REQUIREMENTS
 SUPPORTABILITY REQUIREMENTS
 SECURITY REQUIREMENTS
 INTERFACE REQUIREMENTS
Introduction
The project aims and objectives that will be achieved after completion of this project are
discussed in this subchapter. The aims and objectives are as follows:
 Online book issue
 Request column for librarian for providing new books
 A separate column for digital library
 Student login page where student can find books issued by him/her and date of
return.
 A search column to search availability of books
 A teacher login page where teacher can add any events being organized in the
college and important suggestions regarding books.

Business Requirement Overview

Library Management System is a computerized system which helps user(librarian) to
manage the library daily activity in electronic format. It reduces the risk of paperwork such
as file lost, file damaged and time consuming.
It can help user to manage the transaction or record more effectively and timesaving.

Assumptions and Constraints

The problem occurred before having computerized system includes:
 File lost
o When computerized system is not implemented file is always lost because of
human environment. Sometimes due to some human error there may be a
loss of records.
 File damaged
o When a computerized system is not their file is always lost due to some
accident like spilling of water by some member on file accidentally. Besides
some natural disaster like floods or fires may also damage the files.
 Difficult to search record
o When there is no computerized system there is always a difficulty in
searching of records if the records are large in number.
 Space consuming
o After the number of records become large the space for physical storage of
file and records also increases if no computerized system is implemented.
 Cost consuming
o As there is no computerized system the to add each record paper will be
needed which will increase the cost for the management of library.

Functional Requirements
1. NORMAL USER

1.1 USER LOGIN

Functional requirements
-user id is provided when they register
-The system must only allow user with valid id and password to enter the system
-The system performs authorization process which decides what user level can access to.
-The user must be able to logout after they finished using system.

1.2 REGISTER NEW USER

Functional requirements
-System must be able to verify information
-System must be able to delete information if information is wrong

1.3 REGISTER NEW BOOK

Functional requirements
-System must be able to verify information
-System must be able to enter number of copies into table.
- System must be able to not allow two books having same book id.

1.4 SEARCH BOOK

Functional requirements
- System must be able to search the database based on select search type
- System must be able to filter book based on keyword entered
- System must be able to show the filtered book in table view

1.5 ISSUE BOOKS AND RETURN BOOKS

Functional requirements
-System must be able to enter issue information in database.
-System must be able to update number of books.
- System must be able to search if book is available or not before issuing books
-System should be able to enter issue and return date information
1.6 EVENT ADDITION
Functional requirements
-System should be able to add detailed information about events.
-System should be able to display information on notice board available in the
homepage of site.
Usability Requirements

Improvement in control and performance

The system is developed to cope up with the current issues and problems of library. The
system can add user, validate user and is also bug free.
1. Save cost
a. After computerized system is implemented less human force will be required
to maintain the library thus reducing the overall cost.
2. Save time
a. Librarian can search record by using few clicks of mouse and few search
keywords thus saving his valuable time.
3. Option of online Notice board
a. Librarian will be able to provide a detailed description of workshops going in
the college as well as in nearby colleges
4. Lecture Notes
a. Teacher have a facility to upload lectures notes in a pdf file having size not
more than 10mb

Performance Requirements

PROCESSOR INTEL CORE PROCESSOR OR BETTER

PERFORMANCE
OPERATING SYSTEM WINDOWS VISTA, WINDOWS7,
UBUNTU
MEMORY 1GB RAM OR MORE
HARD DISK SPACE MINIMUM 3 GB FOR DATABASE
USAGE FOR FUTURE
DATABASE MY SQL

Supportability Requirements
This system provides a computerized version of library management system which will
benefit the students as well as the staff of the library.
It makes entire process online where student can search books, staff can generate reports
and do book transactions. It also has a facility for student login where student can login and
can see status of books issued request as well for book or give some suggestions. It has a
facility of teacher’s login where teachers can add lectures notes and give necessary
suggestion to library and add info about workshops or events happening in our college or
nearby college in the online notice board.
Security Requirements

 System will use secured database

 Normal users can just read information, but they cannot edit or modify anything
except their personal and some other information.
 System will have different types of users and every user has access constraints.
 System use shall not cause any harm to human users.
 The system shall accommodate high number of books and users without any fault.
 System shall handle expected and non-expected errors in ways that prevent loss in
information and long downtime period.

Interface requirements

The user interface requirements are concerned with the user interface and how information
is presented to the user.

 Usability
o Interfaces are a critical class of components within the DML that will provide
the means by which users interact with the system. As such, all interfaces
should provide easy access to help as well as clearly indicate the current
state of the user’s transaction when the user isn’t idle.
o Transaction and error status MUST be displayed within each interface
component.
o Cut and paste of text within interfaces and into and out of the interfaces
must be supported.

 Administrative
o Administrative interfaces will assist Library Staff in building/maintaining
collections and controlling access to them. Because of the complexity of the
data model, Library Staff will need to be able to edit multiple records
simultaneously and create links between them.
o Administrative must be able to have multiple records open for editing
o Administrator must be able to create links (references) between records
without needing to type in record identifiers.

 Library user account manage system

o The system shall display the user account information including user ID, last
and first name, and user position, privilege.
o The system shall use a graphic user interface which allows librarians to
choose actions including removing, changing and adding user account and
account information.
 Logging
o Within the system, logging will be used to provide a trail of transactions that
have taken place. This might either be for developer debugging purposes,
administrative checks on usage, or research on the usability of interfaces.
o Transaction logs MUST be kept for each service provided.
o Sufficiently detailed client session logs MUST be generated to support
analysis of user activities.

 Security and Privacy

o The user’s password MUST never be exposed to compromise.
o User session logs stored for usability and another research must be
anonymous.

 Book download
o When download e-book, the system shall show all the e-book information
and check user including
 the first and last name of the user
 the library card number
 the library card expiring date
 to check valid user or not