EX NO : 02 DOCUMENT THE SOFTWARE SPECIFICATION DATE :

31-01-25 REQUIREMENTS FOR THE IDENTIFIED SYSTEM .

AIM:
To document the software specification requirements for the identified system.
PROCEDURE:
1. INTRODUCTION:
The Software Requirements Specification captures all the requirements in a single
document. TheLibrary System that is to be developed provides the members of the
Library and employees of the library with books information and many other facilities.
1.1 Purpose:
The Library Management System (LMS) automates library operations,
improving the management of resources, users, and transactions, and
providing efficient book borrowing, returning, and reporting.
1.2 Scope:
The system covers user management, book cataloging, transactions
(borrowing, returning, reserving), fine tracking, and report generation. It is
accessible via a web interface for both library members and staff.
1.3 Environmental Characteristics
The LMS will be web-based, supporting multi-user access on standard
browsers and devices, with scalability for future growth. It will integrate with
email services and potentially a payment gateway for fines.
2. OVERALL DESCRIPTION:
2.1 Product Perspective:
The Library Management System (LMS) is a web-based
application for managing library resources and transactions, integrated
with the library’s infrastructure for easy access.
2.2 Product Features:
● Book & User Management: Manage books, users, and
transactions.
● Search & Reporting: Search for books and generate reports.
● Fine Management: Track and calculate overdue fines.
2.3 User Classes:
● Admin: Full access to all system features.
● Library Member: Access to book transactions and personal
details.
● Guest: Browse the catalog only.
2.4 Operating Environment:
The LMS will run on web browsers (Chrome, Firefox, etc.) on desktop
and mobile devices, hosted on a secure server.
2.5 Design Constraints:
The system must be scalable, secure, and compatible with existing library
hardware. It should comply with privacy regulations.
2.6 User Documentation
 A user manual will be provided for easy guidance on system usage and
troubleshooting, consolidating all necessary information in one document.
3. FUNCTIONAL REQUIREMENT:
Functional requirements define the fundamental actions that system must
perform.
3.1 Admin Functionalities
Admins have full access to all system features, including managing users, books,
transactions, and generating reports.
● 3.1.1 User Management
○ 3.1.1.1 Add User: Admin can add new users to the system by providing
details like name, email, and membership type.
○ 3.1.1.2 Update User: Admin can edit user information, including contact
details and membership status.
○ 3.1.1.3 Delete User: Admin can delete users from the system.
○ 3.1.1.4 View User Profile: Admin can view detailed information about
registered users.
● 3.1.2 Book Management
○ 3.1.2.1 Add Book: Admin can add new books to the catalog, providing
details like title, author, ISBN, publisher, and genre.
○ 3.1.2.2 Update Book: Admin can edit book details (e.g., availability status,
book description).
○ 3.1.2.3 Delete Book: Admin can remove books from the catalog.
○ 3.1.2.4 View Book Catalog: Admin can view all books in the catalog and
search by various attributes (title, author, ISBN).
● 3.1.3 Transaction Management
○ 3.1.3.1 View Borrowing Transactions: Admin can view all current book
borrowings by users.
○ 3.1.3.2 Modify Transaction: Admin can manually adjust transaction
details, such as extending due dates or returning books.

○ 3.1.3.3 Manage Overdue Books: Admin can view and handle overdue
books, including applying fines or sending reminders.
● 3.1.4 Fine Management
○ 3.1.4.1 Set Fine Rates: Admin can set or modify the fine rate for overdue
books.
○ 3.1.4.2 Track and Manage Fines: Admin can track and manage overdue
fines for users, including adjustments and payments.
● 3.1.5 Report Generation
○ 3.1.5.1 Generate Book Reports: Admin can generate reports for books
(total books, availability, borrowed, etc.).
○ 3.1.5.2 Generate User Reports: Admin can generate reports on user
activity, such as borrowed books and outstanding fines.
○ 3.1.5.3 Generate Fine Reports: Admin can generate reports on fines (total
fines, outstanding payments).
3.2 Library Member Functionalities
Library members can access book-related features and manage their personal transactions.
● 3.2.1 Book Search
 ○ 3.2.1.1 Search by Title: Members can search for books by title.
○ 3.2.1.2 Search by Author: Members can search for books by author.
○ 3.2.1.3 Search by ISBN or Genre: Members can search by ISBN or book
genre.
● 3.2.2 Borrowing and Returning Books
○ 3.2.2.1 Borrow Books: Members can borrow available books and receive a
due date.
○ 3.2.2.2 Return Books: Members can return borrowed books, and the
system updates transaction status.
○ 3.2.2.3 Renew Books: Members can extend the borrowing period for books
that are not overdue.
● 3.2.3 Reservation
○ 3.2.3.1 Reserve Books: Members can reserve books that are currently
checked out, with notifications when the book is available.
● 3.2.4 Transaction History
○ 3.2.4.1 View Borrowing History: Members can view a list of previously
borrowed books, including borrow dates and return status.
○ 3.2.4.2 View Due Dates: Members can check due dates for borrowed
books.
● 3.2.5 Fine Management

○ 3.2.5.1 View Fines: Members can view any fines they owe for overdue
books.
○ 3.2.5.2 Pay Fines: Members can pay outstanding fines online.
3.3 Guest Functionalities
Guests have limited access, mainly for browsing the book catalog.
3.3.1 Catalog Browsing
3.3.1.1 Browse Books by Title/Author: Guests can browse books by title or
author.
3.3.1.2 Browse by Genre/ISBN: Guests can browse by genre or ISBN.
3.3.2 Book Search
3.3.2.1 Search by Title/Author: Guests can search for books by title or author but
cannot borrow or reserve books.
4. EXTERNAL INTERFACE REQUIREMENT:
The Library Management System will have a web-based user interface accessible via
standard browsers, allowing easy navigation for both users and admins. It will integrate
with a database for data storage, email services for notifications, and potentially a
payment gateway for fine transactions.
4.1 User Interface:
The user interface will be web-based, allowing users and admins to access
the system via modern browsers. It will be intuitive, responsive, and user-friendly,
supporting both desktop and mobile devices.
4.2 Hardware interface
The system (in our case, Haramaya University Library Management
System) shall run on a Microsoft Windows based system of:
 ● Processor: Pentium 4 or above
● RAM: 256 MB or above
● Hard disk: 80 GB or above
4.3 Software interface
● Database: SQL server 2005
● Operating system: Windows XP
● Visual basic Studio 2010 for designing users interfaces.
4.4 Communication Interfaces
The Library management system will be connecting to World Wide Web
5. NON-FUNCTIONAL REQUIREMNT:
5.1 Performance Requirements:
The system should respond within 5 seconds, support 500 concurrent users, and
scale for a 50% annual increase in users or books.
5.2 Safety Requirements:
Daily backups of critical data are required, with clear error messages for system
failures.
5.3 Security Requirements:
The system must use encrypted passwords, encrypt sensitive data, and implement
role-based access control for different user roles.