Lab 8
Priyanshu Tyagi
Roll No: 2200290130132
Software Requirements Specification (SRS)
1. Introduction
1.1 Purpose:
The purpose of this document is to specify the requirements of the Library Management System
(LMS) for managing the library operations such as book issue, return, catalog management, and
member registration.
1.2 Scope:
The scope of this system includes functionalities for students, staff, and administrators to manage
books, user accounts, and transactions. The system will be accessible via a web interface.
1.3 Definitions, Acronyms, and Abbreviations:
LMS: Library Management System
SRS: Software Requirements Specification
1.4 References:
IEEE Std 830-1998 - IEEE Recommended Practice for Software Requirements Specifications
1.5 Overview:
This document describes the SRS for the LMS, including system features, external interfaces, and
non-functional requirements.
2. Overall Description
2.1 Product Perspective:
The Library Management System is a standalone web-based application designed for libraries of
educational institutions. It allows librarians to manage the book inventory and issue books to
students and staff.
2.2 Product Features:
- User Registration and Login
- Book Catalog Management
- Issue and Return Books
- Search Functionality
- Fine Management
- Report Generation
2.3 User Classes and Characteristics:
- Students: Can view available books, issue and return books.
- Staff: Can manage book inventory and fine payments.
- Administrators: Can manage all features, including user roles.
2.4 Operating Environment:
The system will operate on a web server with an Internet connection. It will be accessible via
modern browsers such as Chrome, Firefox, or Edge.
3. System Features
3.1 Feature 1: User Registration and Login
- Description: Users will be able to create an account and log in to access the library system.
- Input: User details (name, email, password)
- Output: Access granted or error message
3.2 Feature 2: Book Catalog Management
- Description: Librarians will manage book details, including adding, removing, and editing books.
- Input: Book details (title, author, publisher)
- Output: Updated book catalog
4. External Interface Requirements
4.1 User Interfaces:
The user interface will be a web-based dashboard with sections for managing books, users, and
transactions.
4.2 Hardware Interfaces:
The system will require a web server with sufficient storage and processing power to handle
expected transactions.
4.3 Software Interfaces:
The LMS will interact with a database system (e.g., MySQL) to store and retrieve data.
4.4 Communication Interfaces:
The system will use HTTP/HTTPS protocols for communication between the client (browser) and the
server.
5. System Attributes
5.1 Reliability:
The system will ensure data consistency and handle failures gracefully.
5.2 Availability:
The system will be available 99.9% of the time.
5.3 Security:
The system will implement encryption for user passwords and sensitive data.
5.4 Maintainability:
The system will be easy to maintain, with clear modular design and logging features for debugging.
6. Other Non-Functional Requirements
6.1 Performance Requirements:
The system should handle up to 500 concurrent users.
6.2 Usability:
The system will be user-friendly, with intuitive navigation for users of varying technical proficiency.
6.3 Legal Requirements:
The system will comply with data protection and privacy regulations.
