Software

Requirements
Specification

Project: Library Management System

Author: Abhsihek Wagare

wagareabhishek@gmail.com

Company: TATA

Publication date: 2023-09-07

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Product perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.1 System interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.2 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.3 Hardware interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.4 Software interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.5 Communications interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.6 Memory constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.7 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.8 Site adaptation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.9 Interfaces with services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Product functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 User characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.6 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.7 Assumptions and dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.8 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.9 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 External interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Usability requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 Performance requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.5 Logical database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.6 Design constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.7 Standards compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.8 Software system attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4 Supporting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1 Introduction
[SRS-1] A library management system is software that is designed to manage all the functions of library.

It helps librarian to maintain the database of new books and the books that are borrowed by members along with
their due dates.

This system completely automates all your library's activities .The best way to maintain ,organize, and handle
countless books systematically is to implement a library management system software.

A library management system is used to maintain library records. It tracks the records of the number of books in the
library ,how many books are issued ,or how many books have been returned or renewed or late fine charges ,etc.

Type: Section

1.1 Purpose
[SRS-2] This is the software requirement specification for the Library Management System .The purpose of this
document is to convey information about the application requirement ,both functional and non-functional ,to the
reader.

Type: Section

1.2 Scope
[SRS-3]

Manually updating the library system into an android based application so that the user can know the details
of the books available and maximum limit on borrowing from their computer and also through their phones.
Also user can provide feedback for adding some new books to the library.

Type: Section

1.3 Product perspective

[SRS-4] The Library Management System is used for Library Manager, Librarian , and Library user. The system is self-
contained. It is possible to exchange date with other system through external interface if required.

Type: Section

1.3.1 System interfaces

[SRS-5]

Type: Section

1.3.2 User interfaces

[SRS-6] The program offers a decent graphical interface for the user that can be run on the device by an
administrator performing the necessary tasks such as designing ,reviewing ,displaying the book information.

Type: Section

1.3.3 Hardware interfaces

[SRS-7]

Type: Section

1.3.4 Software interfaces

Software Requirements Specification 1

[SRS-8] Operating System : Window

Type: Section

1.3.5 Communications interfaces

[SRS-9] Window

Type: Section

1.3.6 Memory constraints

[SRS-10]

Type: Section

1.3.7 Operations
[SRS-11]

Type: Section

1.3.8 Site adaptation requirements

[SRS-12]

Type: Section

1.3.9 Interfaces with services

[SRS-13]

Type: Section

1.4 Product functions

[SRS-14]

Type: Section

1.5 User characteristics

1. Library Manager-
Good understanding to library operation
Responsible for library operation

[SRS-15] 2.Library User-

Older generation may like the new system be similar to the old one in terms of user interfaces and
functionality.
Will not have any formal training to use the system.

Type: Section

1.6 Limitations
[SRS-16]

Type: Section

1.7 Assumptions and dependencies

[SRS-17]

Software Requirements Specification 2

Type: Section

1.8 Definitions
[SRS-18]

Type: Section

1.9 Acronyms and abbreviations

[SRS-19]

Type: Section

2 Requirements
[SRS-20] The system requirement in library management focuses on the possibility of search for books by title,
author, or subject by the member. They should be able to locate a book physically by the unique identification code
and the rack number for each book.

The system should limit the number of book that can be taken and the number of days that a book can be kept for.
The system should generate fine when due from the member.

Type: Section

2.1 External interfaces

[SRS-21] It should be simple and easy for consumers to understand and use. It should also be an immersive
interface. For the user and administrator , the device should prompt the login to the program and correct feedback
parameters.

Type: Section

2.2 Functions
[SRS-22]

Type: Section

2.3 Usability requirements

[SRS-23]

Type: Section

2.4 Performance requirements

[SRS-24] The Computer's capability depends on the software's efficiency .Provided the database size is big enough
,the program will take any amount of inputs . This would be dependent on the memory space available.

Type: Section

2.5 Logical database requirements

[SRS-25]

Type: Section

2.6 Design constraints

Software Requirements Specification 3

[SRS-26] Whenever a library member wants to take a book, the book issued by the library authority can check all the
book information as well as the student details and store it in library system. A great deal of human interference can
be avoided in the event of book.

Type: Section

2.7 Standards compliance

[SRS-27]

Type: Section

2.8 Software system attributes

[SRS-28]

Maintainability :The device would not need any servicing .

scalability :Applicable

Type: Section

3 Verification
[SRS-29] This process typically includes verifying the individual's Books and References.

Type: Section

4 Supporting information
[SRS-30]

Type: Section

5 References
[SRS-31]

Type: Section

Software Requirements Specification 4