JAPHET KIPKOECH
SIT/B/01-04834/2022
Software Requirements Specification (SRS) for University Library Database System
1. Introduction
PURPOSE
The purpose of this SRS is to define the requirements for the University Library Database System (ULDS),
which will facilitate the management of library resources, including books, users (students and faculty),
and borrowing transactions. This document is intended for project managers, developers, and
stakeholders.
1.2 SCOPE
The ULDS will provide functionalities such as catalog management, user registration, borrowing and
returning books, and generating reports. The system will support a web-based interface for library staff
and users, ensuring easy access to library resources.
1.3 Definitions, Acronyms, and Abbreviations
ULDS: University Library Database System
Librarian: Staff responsible for managing library operations.
User: A student or faculty member who interacts with the system.
ISBN: International Standard Book Number.
1.4 References
Library Management Standards.
SQL Database Management System Documentation.
2. Overall Description
2.1 Product Perspective
The ULDS will be a standalone web application, integrated with the university’s student information
system to streamline user data management. It will support both desktop and mobile access.
2.2 Product Functions
Manage book catalog (add, update, delete books).
Register and manage users (students and faculty).
Track borrowing and returning of books.
Generate reports on book inventory, user activity, and overdue items.
2.3 User Classes and Characteristics
Librarians: Manage library resources and users.
Students: Search for books and manage their borrowing.
Faculty: Access and manage library resources relevant to their teaching and research.
2.4 Operating Environment
Web browsers (Chrome, Firefox, Safari).
University network infrastructure.
Database server for storing data (e.g., MySQL, PostgreSQL).
2.5 Design and Implementation Constraints
The system must comply with data privacy regulations (e.g., FERPA).
Must be compatible with existing university IT infrastructure.
2.6 Assumptions and Dependencies
Users have internet access and basic computer literacy.
Library staff will receive training on the new system.
3. Specific Requirements
3.1 Functional Requirements
3.1.1 Book Management
FR1: Librarians must be able to add new books to the catalog.
FR2: Librarians must be able to update existing book information.
FR3: Librarians must be able to delete books from the catalog.
FR4: Users must be able to search for books by title, author, or ISBN.
3.1.2 User Management
FR5: Librarians must be able to register new users (students and faculty).
FR6: Librarians must be able to update user information.
FR7: Users must be able to view their profile and borrowing history.
3.1.3 Borrowing and Returning
FR8: Users must be able to borrow books and view current loans.
FR9: Users must be able to return books and update their borrowing status.
FR10: The system must send notifications for overdue books.
3.1.4 Reporting
FR11: Librarians must be able to generate reports on book inventory.
FR12: Librarians must be able to generate reports on user activity and overdue items.
3.2 Non-Functional Requirements
3.2.1 Performance
NFR1: The system must support at least 200 concurrent users.
NFR2: Search queries must return results within 2 seconds.
3.2.2 Security
NFR3: The system must require user authentication for access.
NFR4: User data must be encrypted in transit and at rest.
3.2.3 Usability
NFR5: The system must have a user-friendly interface for all user classes.
NFR6: The system must provide help documentation for users.
4. Use Cases
4.1 Use Case Diagram
(Insert a use case diagram illustrating interactions between users and the system.)
4.2 Use Case Descriptions
UC1: Search for Books
Actors: Student, Faculty
Precondition: User is logged in.
Postcondition: Search results are displayed.
UC2: Borrow Book
Actors: Student, Faculty
Precondition: User has selected a book.
Postcondition: Book status is updated to borrowed, and the due date is recorded.
5. Data Requirements
The system will use a relational database to store information on books, users, and transactions.
Data fields will include:
Books: Book ID, Title, Author, ISBN, Availability Status.
Users: User ID, Name, Email, Role (Student/Faculty), Borrowing History.
Transactions: Transaction ID, User ID, Book ID, Borrow Date, Due Date, Return Date.
6. System Features
6.1 Catalog Management
Feature: Librarians can manage the book catalog (add, edit, delete books).
Priority: High
6.2 User Registration
Feature: Librarians can register new users in the system.
Priority: High
7. Validation and Verification
Testing will include unit tests, integration tests, and user acceptance testing.
Each functional requirement will have corresponding test cases to ensure compliance.
8. Appendices
Diagrams illustrating the database schema and architecture of the system.
9. Glossary
Catalog: A list of books available in the library.
Loan: The process of borrowing a book from the library.
---
This SRS provides a structured framework for developing the University Library Database System,
ensuring clear requirements that will guide the development process and facilitate communication
among stakeholders.
