Deva Dharshini K
953622205015
EXPERIMENT-2
DOCUMENT THE SOFTWARE REQUIREMENTS SPECIFICATION (SRS)
FOR THE IDENTIFIED SYSTEM
AIM:
To Document the Software Requirements Specification (SRS) for the Library
Management System.
REQUIREMENTS:
The purpose of system requirement analysis is to obtain a thorough and detailed
understanding of the business needs for the Library Management System (LMS) as
defined in the project scope. This process helps in identifying, analyzing, and
defining the functional and non-functional requirements of the system. The objective
is to ensure that all stakeholders (students, librarians, faculty, and administrators)
have a clear and agreed-upon set of requirements before proceeding with system
design and development. During the system requirement analysis phase, a framework
for the application is developed, which serves as the foundation for future design,
development, and implementation efforts. This framework ensures that the LMS
effectively supports key functionalities such as book cataloging, user management,
book issue/return processes, fine management, and reporting.
OBJECTIVES OF THE LIBRARY MANAGEMENT SYSTEM:
The Library Management System (LMS) is developed with the objective of
simplifying and automating the daily operations of a library. The system aims to
reduce manual effort, enhance accuracy, and provide quick access to books and
member records. Key objectives include efficient book management, automated book
issuance and return tracking, fine calculation, and user authentication to ensure secure
access. Additionally, the system seeks to improve search capabilities, generate
detailed reports, and enable role-based access for different users such as students,
faculty, and librarians. By achieving these objectives, the LMS ensures a smooth,
organized, and user-friendly library experience.
Deva Dharshini K
953622205015
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. The Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
3. External Interface Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces
3.4 Communications Interfaces
4. System Features
5. Other Non-Functional Requirements
5.1 Performance Requirements
5.1.1 Capacity
5.1.2 Dynamic Requirements
5.1.3 Quality
5.2 Software System Attributes
5.2.1 Reliability
5.2.2 Availability
5.2.3 Security
5.2.4 Maintainability
5.3 Business Rules
6. Other Requirements
7. Appendix A: Glossary
8. Appendix B: Analysis Models
Deva Dharshini K
953622205015
1. Introduction
1.1 Purpose
The purpose of this document is to define the Software Requirements Specification
(SRS) for the Library Management System (LMS). It provides details on the system’s
functional and non-functional requirements, including user interfaces, system
attributes, and business rules.
1.2 Scope
The Library Management System (LMS) will automate and streamline library
operations such as book cataloging, borrowing, returning, fines management, and
user registration. It will support online book reservations, real-time inventory
tracking, and digital library access.
1.3 Definitions, Acronyms, and Abbreviations
LMS (Library Management System): A system used for managing library
resources and operations.
ISBN (International Standard Book Number): A unique identifier for books.
RFID (Radio Frequency Identification): Technology used for tracking books
and users.
OPAC (Online Public Access Catalog): A digital database of available books
in the library.
1.4 References
[ISO 27001] – Information Security Management Standard.
[Dublin Core] – Metadata Standard for Libraries.
1.5 Overview
The system will provide the following features:
Book Cataloging & Search (ISBN-based database).
User Management (students, faculty, and staff).
Book Borrowing & Returning (with automated due-date reminders).
Fines & Penalty System (for overdue books).
Digital Library Support (for e-books and PDFs).
Real-time Inventory Tracking (using RFID).
2. The Overall Description
Deva Dharshini K
953622205015
2.1 Product Perspective
The LMS will be a cloud-based or on-premise system, integrating with university
databases, RFID tracking systems, and digital repositories.
2.2 Product Functions
Book Management: Cataloging, searching, issuing, and returning books.
User Management: Registration and role-based access for students, faculty, and
staff.
Loan Management: Borrowing, renewals, and due-date tracking.
Fines & Fees: Automated fine calculation for overdue books.
Reporting & Analytics: Library usage, book demand trends, and fine reports.
2.3 User Characteristics
Librarians: Manage book inventory and transactions.
Students & Faculty: Borrow, return, and search books.
Administrators: Oversee system configurations and reports.
2.4 Constraints
The system must comply with GDPR and ISO 27001 for data security.
The response time for search queries must be under 2 seconds.
2.5 Assumptions and Dependencies
The system assumes integration with university databases and student records.
Secure API connections are required for external data exchange.
3. External Interface Requirements
3.1 User Interfaces
Library Dashboard: For book management and user tracking.
User Portal: For searching, reserving, and renewing books.
Mobile App: For digital library access and notifications.
3.2 Hardware Interfaces
RFID Scanners & Barcode Readers: For book tracking.
Self-Checkout Kiosks: For borrowing and returning books.
3.3 Software Interfaces
Deva Dharshini K
953622205015
University Database Integration: For user authentication.
OPAC System: For book search and catalog access.
3.4 Communications Interfaces
Secure API (HTTPS): For integration with external systems.
Email & SMS Alerts: For due-date reminders and reservation updates.
4. System Features
User Authentication: Secure login using institutional credentials.
Book Search & Cataloging: ISBN-based lookup with filters.
Automated Due-Date Reminders: Email and SMS alerts.
Self-Service Kiosks: Borrowing and returning books via RFID or barcode.
Real-time Inventory Management: Library staff can track book availability.
5. Other Non-Functional Requirements
5.1 Performance Requirements
5.1.1 Capacity
The system must support 10,000+ concurrent users.
It should manage millions of book records efficiently.
The system must support multiple library branches under a single network.
Should efficiently manage millions of digital and physical book records.
5.1.2 Dynamic Requirements
Search queries must be processed in under 2 seconds.
The system should handle 500+ borrowing transactions per second.
Book search and retrieval operations must complete in under 1.5 seconds.
The system should process at least 1,000+ digital checkouts per second for e-
books.
5.1.3 Quality
Ensures 99.99% uptime with failover mechanisms.
Should support real-time database synchronization for multi-location access.
Implement automated load balancing to handle peak traffic.
5.2 Software System Attributes
5.2.1 Reliability
Deva Dharshini K
953622205015
The system will use redundant backups to prevent data loss.
Automated data recovery in case of accidental deletion.
Cloud-based disaster recovery mechanisms to prevent loss of book records.
5.2.2 Availability
The system must be available 24/7, with scheduled maintenance periods.
99.999% uptime for cloud-hosted services.
Graceful degradation of services during maintenance periods.
5.2.3 Security
End-to-end encryption for all transactions.
Role-based access control to prevent unauthorized actions.
Biometric authentication for secure access in high-security libraries.
Automated fraud detection for suspicious borrowing activities.
Data anonymization for user privacy in analytics.
5.2.4 Maintainability
Modular design for easy feature upgrades without downtime.
Automated update deployment with rollback features.
Plug-and-play modules for integrating new features.
5.3 Business Rules
Maximum Book Limit: Users can borrow up to 5 books at a time.
Fine Calculation: ₹5 per day per book for overdue returns.
Reservation Timeframe: Books must be collected within 48 hours of
reservation.
Book Renewal Policy: Users can renew books only twice, after which they
must return them.
Lost Book Penalty: If a book is lost, the user must pay the full book price +
₹50 processing fee.
Library Membership Tiers: Different borrowing limits for students, faculty,
and external members.
6. Other Requirements
The system should have a mobile-friendly interface.
It must support cloud deployment for scalability.
E-book and audiobook integration for digital lending.
AI-powered book recommendations based on user reading history.
Voice search capability for enhanced accessibility.
Integration with citation tools for academic users.
Deva Dharshini K
953622205015
7. Appendix A: Glossary
LMS: Library Management System.
ISBN: International Standard Book Number.
RFID: Radio Frequency Identification.
OPAC: Online Public Access Catalog.
Dewey Decimal System (DDS): Library classification system for organizing
books.
MARC: Machine-Readable Cataloging format for bibliographic records.
ILS: Integrated Library System, a suite for managing library operations.
8. Appendix B: Analysis Models
Use Case Diagram: Shows interactions between users and the system.
Data Flow Diagram: Illustrates data movement across modules.
Entity-Relationship Diagram: Defines relationships between books, users, and
transactions.
Sequence Diagram: Illustrates the step-by-step flow of book borrowing and
returning.
State Diagram: Defines book status transitions (Available → Reserved →
Checked Out → Returned).
Activity Diagram: Visual representation of the book reservation process.
Deva Dharshini K
953622205015
RESULT:
Thus, the Software Requirements Specification (SRS) document for the Library
Management System has been analyzed successfully.
Performance (25)
Viva voce (10)
Record (15)
Total (50)
