Library Management

System
Software Engineering –
ESC591
Department Of Information
Technology
GROUP –4
NISHITA DEY 11500222004

KRITIKA LAXMI 11500222005

TANMAY PAUL 11500222001

SMARAK BASAK 11500222009

 SRS Document for
•
LMS
An SRS document, or Software Requirements Specification document, is a
comprehensive description of a software system to be developed. It includes
detailed requirements and specifications that the software must fulfill.
1. Introduction
• Purpose:-
The primary purpose of the Library Management System (LMS) is to efficiently manage and automate the
operations of a library .
• Intended Audience and Reading Suggestions :-
Project Stakeholders
Client Representatives
Quality Assurance and Compliance Teams
• Product Scope:-
Functional Scope
Allow librarians to add, modify, and delete books and other library materials.
Non-Functional Scope
Handle concurrent users and large datasets efficiently.

Constraints
Compatibility with existing hardware and software infrastructure.
2. Overall Description 3. External Interface Requirements
• Purpose: Standalone system to automate 3.1 User Interfaces
library tasks like book management and • Registration/Login: Sign up and log in for users and staff.
member interactions. • Forgot Password: Reset via email.
• Functions: Book cataloging, circulation • For Users: Search, borrow, return books; chat support; provid
(borrowing/returns), user management, and • For Staff: Manage books and users; track activities and missin
reporting. 3.2 Hardware Interfaces
• Users: Librarians and library members. • Barcode Scanners: For book transactions.
• Environment: PCs or servers, compatible • Printers: For receipts and labels.
with Windows, Linux, macOS. Requires a • Workstations: PCs connected via network.
database and web server. 3.3 Software Interfaces
• Constraints: Security, data accuracy, • Database: MySQL/PostgreSQL.
scalability. • OS: Windows, Linux, macOS.
• Documentation: Manuals, online help, • Email: For notifications.
tutorials. 3.4 Communications Interfaces
• Assumptions: Primarily used in-library. • Registration: Requires email, name, and password.
• Dependencies: Integration with existing • Browser: Compatible with Google Chrome.
databases. • Security: HTTPS for secure communication.
• Feedback: Star ratings (1-5).
4. System Features
4.1 Registration 4.5 Managing Books and Activities
• User account creation • Track book transactions and activities
• Valid username/email, minimal data usage • Notifications, data management
4.2 Searching and Borrowing Books 4.6 Managing User Information
• Search and borrow books • Organize user data
• Search functionality, set return dates • Display user info, track book data
4.3 Returning and Recommending Books 4.7 Lists (Defaulter, Missing,
• Return books and recommend new ones Recommended Books)
• Timely returns, recommend books • Show lists of defaulters, missing books,
4.4 Feedback Interface and recommendations
• Collect user feedback • Manage and display lists
• Star ratings, feedback form
5. Other Nonfunctional Requirements
5.1 Performance Requirements
• Support a large number of books and users.
• Response times under 5 seconds.
5.2 Safety Requirements
• Database backups required.
• Recovery within 30 minutes after a crash.
5.3 Security Requirements
• Use secure databases.
• Users can only view or modify their own data.
Use Case Diagram
A Use Case Diagram shows the functional requirements
of the system, showing what the system is supposed to
do from the user's perspective.
In total there are 12 Use cases for the
Library management system showing
different interacting features of the
software. User

1. Selecting identity (a staff or a user)

For both user/staff
2. Sign up page Developer

3. Login page Staff

4. Searching of books
5. Borrowing books
Only for User
6. Returning books
7. Chatbot
8. Recommend Books
9. Feedback
10. Managing books Only for Staff
11. User activities
12. Missing books
Activity
Diagram
An Activity Diagram is a type of flowchart that visually represents the flow of activities or
tasks in a system. It illustrates the sequence of activities and the flow of control.

1: Login/sign up page
The person selects their
2: User activities
identity, then they go to the
Once logged in, they are
sign up page where they enter
taken to the home page,
a valid email.
now the user can search,
Once verified they can
borrow and return books.
proceed to login with a valid
user ID and password.
 3: Staff Activities
The staff after logging in are taken to a homepage
different from the users. Here the staff is required to
manage books (i.e. keep record of borrowed books and
keep track of removal and addition of books). They also
need to penalize the late returned book borrowers.

4: Chatbot and Feedback

Here, the user asks any query that they have and the
chatbot answers it.
Then the user is asked for feedback on how their
experience was on the software.
 Sequence Diagram
A Sequence Diagram shows how objects in a system interact with each other through
messages exchanged between objects to accomplish a specific task.
1: Login interaction :-
1. User opens the application
2. Message is given to enter the login details
3. The details given are cross checked from the
database.
4. On right information input, the user is taken to the
homepage of the application

2: User interaction :-
1. User types in a book’s name to search.
2. It is checked in the database for availability.
3. If available then user can borrow it, if not then
they can recommend the book.
4. On borrowing, they’ll have to set a time range
and date and time to return the book which will be
stored in the database.
 3: Staff interactions :-
1. Staff needs to type in the record of
book activities like return dates
borrowed books and removing and
adding of books.
2. They will be stored in the database
3. The database will send a reminder
through the application to the staff on
any nearing return dates of any
books.
4. The staff is to make a list of people
who are late and penalize them.

3: Chatbot and Feedback

interactions :-
1. User asks for any query that they have.
2. Application checks the answer to that
query in the database.
3. If found the answer is given to the user
through Application.
4. Feedback is asked from the user which is
stored in the database after the user gives
their feedback.
Class
Diagram
A Class Diagram describes the static structure by showing system’s classes, attributes,
methods, and the relationships between the classes.
Class 1: Library Management System :- Class 2: Books :-
1. Attributes – i) UserType (String) 1. Attributes – i) Title (String)
ii)username (String) ii) Author (String)
iii)password (String) iii) Publication (String)
2. Functions – i) login() ii) register() 2. Functions – i) Reservation-status() ii) Book_request()
iii)logout() iii) Feedback() iv)
Renew_info()
 Thank
s!
CREDITS: This presentation template was created by
Slidesgo, and includes icons by Flaticon, and infographics &
images by Freepik