Software Requirements

Specification
for

LIBRARY MANAGEMENT
SYSTEM

Version 1.0 approved

Prepared by pallavi

NIT J

05-02-2025

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> 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
6. Other Requirements ................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6

Revision History
Name Date Reason For Changes Version

1. Introduction

1.1 Purpose
The Library Management System (LMS) is developed to manage library resources efficiently by
automating book cataloging, user registration, borrowing and returning books, and handling overdue
fines. This system aims to enhance the user experience by minimizing manual tasks, reducing errors,
and improving book tracking.

1.2 Document Conventions

● Bold headings indicate sections.
● Important terms are italicized.

1.3 Intended Audience and Reading Suggestions

This document is intended for:

● Developers: To understand system functionality.

● Library Staff: To comprehend operational requirements.
● Administrators: To ensure system meets organizational goals.
● Testers: To verify system compliance.

1.4 Product Scope

This system will:

● Automate library management functions like book issuance and returns.

● Provide real-time book availability updates.
● Maintain a digital record of transactions.
● Handle fines for overdue books.
● Offer search and reporting features.

1.5 References
● IEEE Software Engineering Standards.
● Database Design Best Practices.

2. Overall Description

2.1 Product Perspective

This LMS replaces manual record-keeping with a database-driven system that allows easy retrieval
of information about books, users, and transactions.

2.2 Product Functions

● Book Catalog Management: Adding, updating, and deleting book records.
● User Management: Registering students and staff, assigning roles.
● Borrowing/Returning Books: Recording book check-ins and check-outs.
● Fine Calculation: Automatically calculating overdue fines.
● Reports & Analytics: Generating statistics on book usage.

2.3 User Classes and Characteristics

● Librarians: Manage books and user records.
● Students: Borrow, return, and search for books.
● Administrators: Monitor overall system functionality.
2.4 Operating Environment
● OS: Windows, Linux, macOS.
● DBMS: MySQL, PostgreSQL.
● Programming Languages: Java, Python.

2.5 Design and Implementation Constraints

● The system must be accessible via a web browser.
● User authentication is required for book transactions.

2.6 User Documentation

● User Manual.
● Help Desk Support.

2.7 Assumptions and Dependencies

● Requires internet connectivity for cloud storage.
● Assumes barcode scanners for book tracking.

3. External Interface Requirements

3.1 User Interfaces

● Librarian Dashboard: Manage books, users, and transactions.
● Student Portal: Search for books and check borrowing history.

3.2 Hardware Interfaces

● Barcode scanners for book identification.
● Printers for report generation.

3.3 Software Interfaces

● Database: MySQL/PostgreSQL.
● Authentication System: LDAP or OAuth

3.4 Communications Interfaces

Email/SMS notifications for due dates.

4. System Features
4.1 Book Management
 4.1.1 Description and Priority

Book management is a critical component of the Library Management System,

enabling librarians to add, update, remove, and categorize books. This feature ensures
that users can access updated book information in real time. Given its importance, this
feature is assigned a high priority. It significantly affects the system's efficiency in
maintaining an organized and searchable catalog.

4.1.2 Stimulus/Response Sequences

When a librarian enters new book information, the system processes the input,
validates the details, and updates the database. Upon successful addition, the book
becomes searchable for users. If incorrect information is provided, the system prompts
the librarian to correct it. When a book is removed, the system verifies its current
status, ensuring it is not currently borrowed before deletion.

4.1.3 Functional Requirements

The book management feature must include the following functional capabilities:

● REQ-1: The system shall allow librarians to add new books with attributes such
as title, author, ISBN, category, and availability status.
● REQ-2: The system shall permit book removal only if it is not currently issued
to any user.
● REQ-3: The system shall enable librarians to update book details, including
changes in category or author information.
● REQ-4: The system shall provide a search functionality allowing users to filter
books by title, author, and genre.
● REQ-5: The system shall maintain a record of removed books for auditing
purposes.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

● The system should support 100+ concurrent users.

5.2 Safety Requirements

● Regular data backups must be taken.

5.3 Security Requirements

● User passwords must be encrypted.

5.4 Software Quality Attributes

● Scalable, reliable, and easy to use.

5.5 Business Rules

● Books can only be borrowed for 14 days.
● Users with unpaid fines cannot borrow books.