Software Requirements Specification: Library Management System
Software Requirements Specification: Library Management System
Software Requirements Specification: Library Management System
On
LIBRARY MANAGEMENT
SYSTEM
Submitted By:
SHAH KENIL RAMESH – B160632CS
MANU JOSE PHILIP – B160158CS
GOGIENNI BHARATH – B160653CS
SHIRSWAR MALHAR – B160511CS
2
TABLE OF CONTENTS
1. INTRODUCTION 3
1.1 PURPOSE 3
1.2 SCOPE 3
1.3 REFERENCES 3
2. FUNCTIONAL REQUIREMENTS 4
3. NON-FUNCTIONAL REQUIREMENTS 5
3.1 USABILITY REQUIREMENT 5
3.2 ERROR HANDLING 5
3.3 SECURITY REQUIREMENTS 5
3.4 SOFTWARE REQUIREMENTS 5
3.5 HARDWARE REQUIREMENTS 5
1. INTRODUCTION
1.1 PURPOSE
1.2 SCOPE
The document only covers the requirements specifications for the Library
Management System.
This document does not provide any references to the other component of the
Library Management System.
All the external interfaces and the dependencies are also identified in this
document.
The overall scope of the feasibility study is to provide sufficient information to
allow a decision to be made as to whether the Library Management System
project should proceed and if so, its relative priority in the context of other
existing Library Management Technology
1.3 REFERENCES
Fundamentals of Database System by Elmasri
Fundamentals of Software Engineering by Rajib Mall
4
2. FUNCTIONAL REQUIREMENTS
1. The LMS should store all information about librarian and other users
(students and faculty members) – their login info, books issued, etc.
2. The LMS should store all information about the books and users in two
separated databases.
3. The LMS should allow searching books/journals by author, title, keywords
or availability.
4. The LMS should generate request’s reports for librarian, upon which
he/she could make decisions about accepting/rejecting the requests.
5. The LMS should allow users to view their personal information and status
(numbers of books issued, days left, etc.)
6. The LMS should provide modules to search, request and renew books.
7. The users should be able to view their recent check-ins/checkouts,
calculate and clear dues, request/recommend more books, etc.
8. The librarian must be able to add/remove books, manage users, process
dues, view recommendations from users, etc.
Use case analysis of the different functionalities has been provided in section
5 for better understanding of the system
5
3. NON-FUNCTIONAL REQUIREMENTS