Software Requirement and Specification Document of Library Management System

1. SRS Document of Library
Management System
Group Members:
• Najeeb Ullah (13646)
• Muhammad Ghani (13831)
• Sami Ullah (13999)
• Amar Amjad (13893)

2. CONTENTS
Introduction
01
Overall Description
02
External Interface Requirements
03
System Features
04
Other Requirements
06
Other Non-Functional Requirements
05

3. Revision History
Name Date Reason for change Version
ABC 29-11-23 Initial release or draft 1.0
XYZ 1-12-23 Updated based on feedback 1.1

4. 1.1 Purpose
• Comprehensive overview of LMS requirements
• Focus on version 1.0
• Encompasses entire system
• Defines specifications for development, implementation, and operation
1.2 Document Conventions
• Main Title: Calibri Light, 20, Bold
• Sub Title: Calibri Light, 18, Bold
• Body: Calibri Body, 16
1.3 Audience and Reading Suggestions
• Developers, project managers, testers, LMS stakeholders
• Start with the basics, then explore role-specific sections
1. INTRODUCTION

5. 1.4 Product Scope
• Focus on making library tasks easy and efficient
• Automates borrowing, returning, and cataloging
• User-friendly interface for librarians and visitors
1.5 References
 Book:
• Software Engineering: A Practitioner’s Approach 8th Edition by Roger S. Pressman, Ph.D.
• Software Engineering: 9th Edition by Ian Sommerville.
 Website:
• www.slideshare.net
• www.studocu.com

6. 2.1 Product Perspective
• Standalone system managing library resources
• Interfaces with library database, patron records, and external systems
2.2 Product Functions
• Cataloging Books
• Managing Patron Records
• Tracking Borrowed and Returned Items
• Generating Reports
• User-Friendly Interfaces
• Search and Retrieval
2.3 User Classes and Characteristics
• Librarians, Administrators, Patrons (Library Visitors)
2. OVERALL DESCRIPTION

7. 2.4 Operating Environment
• Windows operating system
• Web-based platform accessible through modern browsers
• Hardware: SSD, Monitor: 24 inch, Basic input devices: QWERTY Keyboard, mouse, Output devices:
printer
2.5 Design and Implementation Constraints
• Record book transactions promptly
• Notify members of fines promptly
2.6 User Documentation
• Manuals, online help, tutorials for users
• Empower users for effective LMS usage
2.7 Assumptions and Dependencies
• Good internet connection, strong server, compatibility with online services

8. 3.1 User Interfaces
• User-friendly design for librarians and patrons
• Features: easy search, clear navigation and status messages.
3.2 Hardware Interfaces
• Communicates with standard hardware components
3.3 Software Interfaces
• Connects with a database server
• May integrate with external authentication services
3.4 Communications Interfaces
• Uses standard web protocols (HTTP/HTTPS)
3. EXTERNAL INTERFACE REQUIREMENTS

9. 4.1 System Feature 1: User Login and Signup
• Secure and user-friendly login and signup
• High Priority
• Functional Requirements, Security Requirements, Usability
4.2 System Feature 2: Cataloging Books
• Librarians manage book records
• High Priority
• Functional Requirements
4.3 System Feature 3: Managing Patron Records
• Librarians manage patron records
• High Priority
• Functional Requirements
4. SYSTEM FEATURES

10. 4.4 System Feature 4: Tracking Borrowed and Returned Items
• Automated tracking of library materials
• High Priority
• Functional Requirements
4.5 System Feature 5: Generating Reports
• Tools to generate reports
• High Priority
• Functional Requirements
4.6 System Feature 6: User-Friendly Interfaces
• Simple and intuitive interface
• High Priority
• Functional Requirements
4.7 System Feature 7: Search and Retrieval
• Facilitates easy search and retrieval
• High Priority
• Functional Requirements

11. 5.1 Performance Requirements
• Responds within 2 seconds
• Concurrent user support: up to 100 users
5.2 Safety Requirements
• Confirms user identity and permissions
5.3 Security Requirements
• Data safety (HTTPS)
• Secure password storage
5.4 Software Quality Attributes
• Adaptability and usability
5.5 Business Rules
• Patrons can borrow a maximum of [5] books at a time
• Overdue books incur [500] per day
5. OTHER NON-FUNCTIONAL REQUIREMENTS

12. 6.1 Make it Easy for Everyone
• Accessibility Requirements
• System should be easy to use for everyone, including those with disabilities
6.2 Play by the Rules
• Legal and Compliance Requirements
• System must follow the law to protect user data and respect copyright rules for books
6.3 Keep Things Safe
• Backup and Recovery
• Plan for data backup and recovery
6. OTHER REQUIREMENTS

13. • LMS (Library Management System): Software system manage library tasks.
• SRS (Software Requirements Specification): Document defining software system details.
• Cataloging: Organizing and recording library resource details.
• Patrons: Library visitors who borrow books.
• Authentication Services: Systems verifying user identity.
• HTTPS (Hypertext Transfer Protocol Secure): Secure data transmission protocol.
• User Interface (UI): Design enabling user-system interaction.
• Concurrent Users: Simultaneous system users (up to 100).
• Adaptability: System's flexibility for future updates.
• Usability: Interface user-friendliness for all classes.
• Backup and Recovery: Strategies for data safeguarding and retrieval.
• Copyright Rules: Legal guidelines for user data and book copyrights.
• TBD (To Be Determined): Unresolved items or decisions (Appendix C).
Appendix A - Glossary

14. Use-case Higher Level Diagram
Appendix B - Analysis Models

15. Use-case Lower Level Diagram
Appendix B - Analysis Models

16.  TBD-001: Integration with External Authentication Services
• Reason for TBD: Pending decision on specific external authentication services
• Responsible Party: System Integration Team
• Expected Resolution Date: [10-1-2024]
• Status: Open
 TBD-002: Detailed Hardware Specifications
• Reason for TBD: Waiting for final decision on hardware configurations
• Responsible Party: System Architecture Team
• Expected Resolution Date: [10-2-2024]
• Status: Open
 TBD-003: User Interface Design Standards
• Reason for TBD: Awaiting finalization of UI design standards
• Responsible Party: UX Design Team
• Expected Resolution Date: [10-3-2024]
• Status: Open
Appendix C - To Be Determined List

17. THANK YOU