Software Requirements Specification

for

LIBRARY MANAGEMENT SYSTEM

(LMS)
Version 1.0 approved

Prepared by

Sanket D. Deshmukh

Dattatraya I. Dongare

Neha L. Biman

Rohit A. Deshmukh

Sinhgad College of Engineering, Pune-41

13 March, 2011
SRS for Library Management System Page ii

Table of Contents

Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions...................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1

2. Overall Description..................................................................................................................2
2.1 Product Perspective.........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3

3. External Interface Requirements...........................................................................................3

3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces.............................................................................................................3

4. System Features.......................................................................................................................4
4.1 System Feature 1.............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4

5. Other Nonfunctional Requirements.......................................................................................4

5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
SRS for Library Management System Page iii

6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6
SRS for Library Management System Page 1

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 document is developed after a number of
consultations with the client and considering the complete requirement specifications of the given
Project. The final product of the team will be meeting the requirements of this document.

1.2 Document Conventions

The following are the list of conventions and acronyms used in this document and the project as
well:
 Administrator: A login id representing a user with user administration privileges to the
software
 User: A general login id assigned to most users
 Client: Intended users for the software
 SQL: Structured Query Language; used to retrieve information from a database
 VB: Visual Basic (The front-end for LMS)
 Use Case: A broad level diagram of the project showing a basic overview
 Boolean: A true/false notation
 Interface: Something used to communicate across different mediums
 Unique Key: Used to differentiate entries in a database

Typographical conventions:
Throughout this document, the following conventions have been used: -
Font: - Times New Roman
Size 18: for Main Headings
Size 14: for Sub Headings
Size 12: for the rest of the document.
SRS for Library Management System Page 2

Words in Bold are important terms, and have been formatted to grab the attention of the reader.

1.3 Intended Audience and Reading Suggestions

This document is meant for:

 Developers
 Librarian
 Library staff
 Patrons of library
This document will be reviewed frequently by the above audiences to check if the different
phases of the project are being completed by meeting the given requirements. If there are any
changes in the requirements in the course of the project they must be included in this document by
making the necessary changes.

1.4 Product Scope

The main scope and deliverables of the project would be:

- Understand and prepare detailed user specifications

- Prepare high level and detailed design specifications of the system
- Prepare Test Plan & Test cases
- Develop a prototype system
- Perform unit testing, integration testing, system testing & regression testing
- Demonstrate bug free application

1.5 References

1. Volere System specification template

2. Rational Unified Process – Business modeling template
3. Statement of need
4. ' RFID Based Library Management System’, by Dhanalakshmi M, Uppala Mamatha.
5. ‘RFID and libraries’, by Lori Bowen Ayre, August 19, 2004
SRS for Library Management System Page 3

2. Overall Description
2.1 Product Perspective

The proposed Library Management System which is being developed by Innovative

Library Management Solutions team is an innovative Library Management System. This System
will provide a search functionality to facilitate the search of resources. This search will be based on
various categories viz. book name or the book id. Also Advanced Search feature is provided in
order to search various categories simultaneously. Further the library staff personnel can
add/update/remove the resources and the resource users from the system. Further each branch is
managed individually and locally by that branch library staff. The System should reflect and support
this decentralized structure. A provision should further be allowed to add a branch. The System will
also have an ADMIN who has full-fledged rights with regards to managing resources across
branches – such as transferring books across these branches. The users can know the number of
available books, information about their account etc.

2.2 Product Functions

The Library Management System provides online real time information about the books
available in the Library and the user information. The Product functions are more or less the same
as described in the product perspective. The functions of the system include the system providing
different type of services based on the type of users [Member/Librarian].

 The member should be provided with the updated information about the books catalog.
 Provisions for the members to borrow the books they want, if all the other required rules
hold good.
 The member is given a provision to check his account information and change the account
information any time in the given valid period.
 The members are provided with the books available roster and allowed to choose the books,
which they want to use in the coming up days.
SRS for Library Management System Page 4

 The librarian can get the information about the members who have borrowed or returned the
books.
 The librarian is provided with interfaces to add/delete the books available in the book
catalog.
 The members when complete the book borrowing or returning process, the due to be paid by
the member must be calculated and the information about the member and the due amount is
sent to the billing system.

2.3 User Classes and Characteristics

The users of the system are members, librarians, staff and the administrators who maintain
the system. The members, staff and the librarian are assumed to have basic knowledge of the
computers. The administrators of the system to have more knowledge of the internals of the system
and is able to rectify the small problems that may arise due to disk crashes, power failures and other
catastrophes to maintain the system. The proper user interface, users manual, online help and the
guide to install and maintain the system must be sufficient to educate the users on how to use the
system without any problems.

2.4 Operating Environment

Operating System : Windows XP and above

Hardware platform : Computer System
Front End : Visual Basis
Back End : MS Access

2.5 Design and Implementation Constraints

 The information of all the users must be stored in a database that is accessible by the
Library System.
 The Library System is running on the university computer and is running all 24 hours a
day.
SRS for Library Management System Page 5

 The users must have their correct usernames and passwords to enter into the Library
System.
 The product is accomplished with login facility so that specific function is available to
specific student.

2.6 User Documentation

 User guide
 On-line tutorials
 Visual operation guide(CD/DVD)

2.7 Assumptions and Dependencies

 The users have sufficient knowledge of computers.

 The users know the English language, as the user interface will be provided in English
 The product can access the library database
SRS for Library Management System Page 6

3. External Interface Requirements

3.1 User Interfaces

Front End : Visual Basic

3.2 Hardware Interfaces

The Server Side:

 Operating System: Windows XP or better

 Processor: Pentium 3.0 GHz or higher
 RAM: 256 Mb or more
 Hard Drive: 10 GB or more.
The Client side:

 Operating System: Windows XP or better

 Processor: Pentium III or 2.0 GHz or higher.
 RAM: 256 Mb or more

Database : MS Access
Application : Visual Basic

3.3 Software Interfaces

A firewall will be used with the server to prevent unauthorized access to the system.
SRS for Library Management System Page 7

3.4 Network Interfaces

The existing Local Area Network (LAN) will be used for collecting data from the users and
also for updating the Library Catalogue.

4. System Features

4.1 Database – Storage

4.1.1 Description and Priority

Proposed Database is intended to store, retrieve, update, and manipulate information related to
university which include:

 Books availability
 Staff information
 Student details
 My Account
 Calculation of fines

4.1.2 Stimulus / Response Sequences

Responses for Administrator:

The administrator can Login and Logout. When the administrator logs into the library
system, the system will check for validity of login .If the Login and password are valid, the
response to this action is the administrator will be able to modify, view, add, deleting and all other
functions that can be performed on the database.
SRS for Library Management System Page 8

4.2 Functional Requirements

This section gives the list of Functional and non functional requirements which are
applicable to the Library Management System.

4.2.1 Interface Requirements

This section describes how the software interfaces with other software products or users for
input or output.

4.2.1.1 User Interfaces

Describes how this product interfaces with the user.

GUI

It describes the graphical user interface, if present. This section should include a set of
screen dumps or mockups to illustrate user interface features.

1. Description
The user interface must be customizable by the administrator

2. Criticality
This issue is essential to the overall system. All the modules provided with the software
must fit into this graphical user interface and accomplish to the standard defined.

3. Technical issues
In order to satisfy this requirement the design should be simple and all the different
interfaces should follow a standard template. There will be the possibility of changing colors and
images, plus switching between interfaces with the minimum impact for the users.
SRS for Library Management System Page 9

4. Risks
To reduce the circumstances under which this requirement might not able to be satisfied, all
the designers must have been developed web sites previously and they must be aware of html
restriction and cross browsers implementations before starting the designing. In order to reduce the
probability of this occurrence the entire design team will be trained in basic html development and
macromedia fireworks, this tool will be used instead of Photoshop.

5. Dependencies with other requirements

All user interfaces should be able to interact with the user management module and a part of
the interface must be dedicated to the login/logout module
SRS for Library Management System Page 10

5. Other Nonfunctional Requirements

5.1 Performance

5.1.1 Response Time

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.

5.1.2 Administrator/Librarian Response

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

5.1.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.

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

5.1.5 Resource Utilization

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

5.2 Security Requirements

All 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
SRS for Library Management System Page 11

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.

5.3 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

1.1 Software Quality Attributes

5.3.1 Usability

 The system shall allow the users to access the system from the Internet using HTML or
it’s 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.

5.3.2 Reliability

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

5.3.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.

5.3.4 Mean Time Between Failures (MTBF)

The system will be developed in such a way that it may fail once in a year.

5.3.5 Mean Time to Repair (MTTR)

SRS for Library Management System Page 12

Even if the system fails, the system will be recovered back up within an hour or less.

5.3.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.

5.3.7 Maximum Bugs or Defect Rate

Not specified.

5.3.8 Access Reliability

The system shall provide 100% access reliability.

1.2 Business Rules

NA

Appendix A: Glossary

LMS : Library Management System

SRS for Library Management System Page 13

Appendix B: Analysis Models (UML Diagrams)

Use Case Diagram

SRS for Library Management System Page 14

Class Diagram
SRS for Library Management System Page 15

Activity Diagram 1
SRS for Library Management System Page 16

Activity Diagram 2
SRS for Library Management System Page 17

Sequence Diagram 1
SRS for Library Management System Page 18

Sequence Diagram 2
SRS for Library Management System Page 19

Sequence Diagram 3