You are on page 1of 5

Library Management

Software Requirement
L.Chaitanya Reddy
Reg No: 070911152


1. Introduction
1.1. Purpose
1.2. Scope
1.3. Definitions, Acronyms and Abbreviations
1.4. References
1.5. Overview

2. General Description
2.1. Product Perspective
2.2. Product Functions
2.3. User Characteristics
2.4. Operating Environment
2.5. General Constraints
2.6. Assumptions and Dependencies

3. Specific Requirements
3.1. Functional Requirements
3.2. Design Constraints
3.3. Non-Functional Requirements

3.3.1. Security
3.3.2. Performance Requirements
3.3.3. Maintainability
3.3.4. Reliability

1.1 Purpose

The main objective of this document is to describe all the requirements and the
functioning of a Library Management System (LMS). The LMS is intended for educational
purpose. The users include: students, teaching staff and the non teaching staff of the respective
Developers should consult this SRS document and its revisions as the only source of
requirements for the project. They should not consider any other requirement statements, written
or verbal as valid until they appear in this document or its revision.
The Library management and its staff should use this document as the primary means to
communicate confirmed requirements to the development team.

1.2. Scope

The proposed software product is the Library Management System (LMS). The system
will be used to allocate PID’s to students, teaching and non-teaching staff. Based on the PID’s the
library staff will keep track of the books issued to students and staff, the return dates and fine if
the book is not returned before the return date. The staff will also have a record of the existing
books, the number of their copies and new books added to the library. The intention of the system
is to efficiently manage the library and keep track of the circulation of the books. Requirement
statements in this document are both functional and non-functional.

1.3. Definitions, Acronyms and Abbreviations

The following are the list of conventions and acronyms used in the document and the
project as well:
 LMS: Library Management System
 PID: Identification for students, teaching and non teaching staff.
 SRS: Software Requirement Specification
 Record: An account of books in the library and books issued
 GUI: Graphic User Interface
 SQL: Structured Query Language, used to retrieve information from the database
 Database: Collection of information in a structured form

1.4. References

No formal references have been referenced in this document.

1.5. Overview
This Software Requirement Specification (SRS) is the requirements work product that
formally specifies Library Management System (LMS). The objective of the document is to
describe the system’s requirements (functional requirements and non-functional requirements)
and constraints. The brief structure of this document is organized as follows:
Section 2 of this document provides an overview of the functions the proposed Library
Management System (LMS) will do. These include a general description of the product, user
characteristics, general constraints and any assumptions for this system.
Section 3 presents the domain model. Picture 1 shows an overview of Library
Management System (LMS) and the relationships between requirements.


2.1. Product Perspective

This Library Management System (LMS) is a self contained system that performs the
functions of a library such as maintain record of all the books in the library, keeping record of the
circulation of books, maintaining student and staff records and calculating penalty if the books to
be collected are not returned before the return date.

2.2. Product Functions and Features

The system features and functions and features can be described as follows: