SOFTWARE REQUIREMENT

specification(SRS) for
Library Management System

Prepared by:
NAME: Akanksha Verma
Roll no: B57
Reg no:11614257
Section: k1608
1 Introduction
Modern Libraries are not
made up of just Books but
CD ROMs, Articles, Project
Reports, Bound volumes are
substantial part of the
holding, Managing the
holdings manually is a not a
simple job. There are few
solutions but many a times,
we find ourselves "making
them works" by finding
"ways to work around"
system inadequacies.
Moreover we have limited
staff resources, these "work
around" waste time, effort,
and skills that should be
spent on user services.
Library Management system
is a small footprint software
suitable for personal /
individual Libraries. You can
store the information about
the books and other material
and control the movement of
the same.
1.1 Purpose
This document describes the
software requirements and s
pecification (SRS) for LMS
software. The document is in
tended for the customer and
the developer (designers, tes
ters, maintainers). The reade
r is assumed to have basic kn
owledge of LMS.Knowledge a
nd understanding of Unified
Modeling Language (UML) di
agrams is also required.
1.2 Project Scope
LMS is essentially meant of
collections. It is a multi-user
version and can take care of
all the fundamental functions
of a Library like Cataloguing,
Circulation, Accessioning and
Housekeeping. It can cater to
all the basic functions of a
small library.
2.Function
Requirement
2.1The Librarian
2.1.1 Add Article
New entries must be
entered in database
2.1.2 Update Article
Any changes in articles
should be updated in case
of update
2.1.3 Delete Article
Wrong entry must be
removed from system
2.1.4Inquiry Members
Inquiry all current enrolled
members to view their
details
2.1.5 Inquiry Issuance
Inquiry all database articles
2.1.6 Check out Article
To issue any article must be
checked out
2.1.7 Check In article
After receiving any article
system will reenter article
by Checking
2.1.8 Inquiry waiting for
approvals
Librarian will generates all
newly application which is
in waiting list
2.1.9 Reserve Article
This use case is used to
reserve any book with the
name of librarian, it can be
pledged
2.1.10 Set user Permission
From this user case
Librarian can give
permission categorically,
also enabling/disabling of
user permission can be set
through this use case
2.2MEMBER
2.2.1 Authentication
User must authenticated
before accessing system
2.2.2 Search Article
User can search any
article
 2.2.3 Request Article
After successful searching
member mark this book as
requested article
2.2.4 Check Account
This use case is used
to check account details
2.3 Asst. Librarian
2.3.1 Prepare Library database
All data base must be prepared
2.4Guest
2.4.1 Register user
User must full fill all
application form for
registration
3.NON-Functional
Requirement
3.1 Safety Requirements
The database may get crashed at
any certain time due to virus or
operating system failure.
Therefore, it is required to take
the database backup
3.2 Security Requirements
We are going to develop a
secured database for the
university .There are different
categories of users namely
teaching staff, administrator,
library staff ,students etc.,
Depending upon the category of
user the access rights are
decided. It means if the user is
an administrator then he can be
able to modify the data, delete,
append etc., all other users
other than library staff only have
the rights to retrieve the
information about database.
3.3Software Quality
Attributes
The Quality of the database is
maintained in such a way so that
it can be very user friendly to all
the users of the database
3.4Hardware Constraints
The system requires a database
in order to store persistent data.
The database should have
backup capabilities.
3.5 Software Constraints
The development of the system
will be constrained by the
availability of required software
such as database and
development tools.
The availability of these tools will
be governed by
3.6 Hardware Interfaces
3.6.1 Server
Operating System:
Windows
Processor: Pentium 4.0
GHz or higher
RAM: 1GB Mb or more
Hard Drive: 80 GB or more
3.6.2Client
Operating System:
Windows.
Processor: Pentium III or
2.0 GHz or higher.
RAM: 512 Mb or more
3.7 Software interfaces
Oracle database 8i or 10g
Developer 2000
3.8Accessibility:
Accessibility refers to the design
of products, devices, services, or
environments for people who
experience disabilities.[1] The
concept of accessible design and
practice of accessible
development ensures both
"direct access" (i.e. unassisted)
and "indirect access" meaning
compatibility with a
person's assistive technology.
3.9Reliability:
Reliability engineering is a sub-
discipline of systems
engineering that
emphasizes dependability in
the lifecycle management of
a product. Dependability, or
reliability, describes the ability of
a system or component to
function under stated conditions
for a specified period of time.
3.10Maintainability:
In engineering, maintainability is
the ease with which a product
can be maintained in order to:
correct defects or their cause,
repair or replace faulty or
worn-out components
without having to replace still
working parts,
prevent unexpected working
condition,
maximize a product's useful
life