A Project Report on

Library Management System

IT 242: Software Design and Development

Submitted By:
Anshu Gautam
Submitted to:
Bodhika Pandeya
Mr. Tilak Khatri
Hira K.C
Faculty of Management
Prabeen B.K
Samir Ghimire
Utsab Roka

April, 2025
 Acknowledgement
We, the students of BIM 5th Semester, would like to express our sincere gratitude to our
respected subject teacher Mr. Tilak Khatri for his invaluable guidance, support, and
encouragement throughout the development of this project titled "Library Management
System".

Sir, your constructive feedback, continuous assistance, and motivation at every stage helped
us successfully complete this project. This opportunity to explore the practical
implementation of software design and development has enhanced our technical knowledge
and team collaboration.

We are also grateful to our fellow group members for their cooperative efforts, active
participation, and dedication, which made this project a success.

Lastly, we extend our heartfelt thanks to our department and all faculty members who
indirectly supported us in this project.

………………….. ………………………..
Mr. Tilak Khatri Head of Department
Subject Teacher (HOD Signature)

2
3
Table of Contents

Chapter One: Introduction....................................................................................................................4

1.1. Introduction................................................................................................................................4
1.2. Objectives of the Project............................................................................................................4
1.3. Methodology..............................................................................................................................4
Chapter Two: Tasks and Activities Performed.......................................................................................5
2.1 Requirement Analysis..................................................................................................................5
a) Functional Requirements...........................................................................................................5
b) Non-Functional Requirements...................................................................................................6
2.2 Feasibility Study...........................................................................................................................6
a) Technical Feasibility...................................................................................................................6
b) Economic Feasibility..................................................................................................................6
c) Legal Feasibility..........................................................................................................................6
d) Operational Feasibility...............................................................................................................6
2.3 Solution Design............................................................................................................................7
2.3.1 Activity Diagram....................................................................................................................7
2.3.2 Sequence Diagram................................................................................................................8
2.3.3 E-R Diagram..........................................................................................................................9
2.4 System Development.................................................................................................................10
2.4.1 Tools Used..........................................................................................................................10
2.4.2 Module Description............................................................................................................10
2.4.3 Testing................................................................................................................................10
Chapter Three: Discussion and Conclusion..........................................................................................11
3.1 Discussion..................................................................................................................................11
3.2 Conclusion.................................................................................................................................11
3.3 Recommendation......................................................................................................................11

4
Chapter One: Introduction
1.1. Introduction

A Library Management System (LMS) is a software that helps manage the day-to-day
operations of a library. It automates processes such as book issuing, returning, cataloging,
and maintaining records of members, staff, and books. The main objective is to reduce human
effort and errors, improve efficiency, and ensure that all operations run smoothly and
systematically.

Previously, libraries relied on a manual system, which included maintaining handwritten

records of books, members, and transactions. This system had many disadvantages, such as
difficulty in searching for records, increased chances of human errors, time-consuming
processes, and challenges in tracking overdue books and fines. Data loss due to misplacement
or physical damage of records was also a common issue. These limitations caused delays and
dissatisfaction among users and staff.

With the help of LMS, these problems can be solved. It provides a centralized and digitized
platform that ensures data consistency, quick access to records, automatic calculation of
fines, and efficient reporting. The system not only saves time and effort but also provides
better control over library activities.

1.2. Objectives of the Project

 To automate the manual work in the library.

 To maintain a proper database of books and members.
 To make searching of books and users faster.
 To manage the issuing and returning process efficiently.
 To generate useful reports and keep track of fines or penalties.

1.3. Methodology

This project follows the Waterfall Model of Software Development Life Cycle (SDLC),
involving distinct phases:
 Requirement Analysis
 System Design
 Implementation
 Testing
 Deployment
 Maintenance

5
Chapter Two: Tasks and Activities Performed
2.1 Requirement Analysis

a) Functional Requirements

 Login and authentication system.

 Book catalog management.
 Member registration and management.
 Issue/return book functionality.
 Fine calculation for late returns.
 Search functionality (by title, author, ISBN).
 Report generation (daily/weekly/monthly).

Use Case Diagram

Fig.1: Use Case diagram of Library Management System

6
b) Non-Functional Requirements

 User-friendly interface.
 Secure and reliable data handling.
 Data backup and recovery support.
 Performance and speed for multiple users.

2.2 Feasibility Study

a) Technical Feasibility

The system is highly feasible from a technical standpoint. It is developed using widely used
and well-supported technologies like PHP, MySQL, HTML, and CSS. These tools are open-
source and require minimal hardware requirements, making implementation possible even in
basic computing environments. Thus, there are no technical limitations to deploying the
system.

b) Economic Feasibility

From an economic perspective, the system is cost-effective. It is developed using free tools
and platforms, which significantly reduces development costs. Moreover, the automation of
manual tasks results in long-term savings on labor, stationery, and management time.
Therefore, the system is economically viable and sustainable.

c) Legal Feasibility

The system adheres to standard data protection and privacy laws. All third-party libraries and
tools used are open-source and comply with licensing regulations. Sensitive user data is
stored securely, ensuring compliance with relevant legal standards. Hence, the system faces
no legal barriers to implementation.

d) Operational Feasibility

Operationally, the system is easy to use and integrates seamlessly into library workflows.
Librarians and users can quickly learn and adapt to it. The interface is user-friendly, and the
system addresses all major operational problems faced in the manual system. It enhances the
overall efficiency and reliability of library operations, making it operationally practical and
beneficial.

7
2.3 Solution Design

System design is the process of defining elements of a system like modules, architecture,
components and their interfaces and data for a system based on the specified requirements.

2.3.1 Activity Diagram

Fig.2: Activity diagram of Library Management System

8
2.3.2 Sequence Diagram

Fig.3: Sequence diagram of Library Management System

9
2.3.3 E-R Diagram

Fig.4: Entity-Relation diagram of Library Management System

10
2.4 System Development

2.4.1 Tools Used

 Frontend: HTML, CSS, JavaScript

 Backend: PHP
 Database: MySQL
 Server: XAMPP/WAMP
 Design Tools: Draw.io, Lucidchart

2.4.2 Module Description

 Admin Module: Manages books, users, and generates reports.

 Librarian Module: Issues, returns, and tracks books.
 Student Module: Searches, views, and reserves books.

2.4.3 Testing

Test Case Module Input Expected Result Status

Login with valid Login Valid email & Redirect to dashboard Pass
credentials password
Book Issue Issue Valid Member & Book issued & status Pass
Module Book ID updated
Return Book Return Book ID with due date Book returned & fine Pass
Module calculated
Search Book Catalog Keyword: “C List of matching Pass
Programming” books

11
Chapter Three: Discussion and Conclusion
3.1 Discussion

While working on the development of this system, we learned how a real-world problem like
library record-keeping can be solved with systematic planning and development. We
encountered various challenges in data normalization, validation logic, and user access
control, which we resolved through proper testing and peer feedback.

Group collaboration, feedback from our teacher Mr. Tilak Khatri, and real-time testing
helped us polish the system into a usable product.

3.2 Conclusion

The Library Management System automates the major functionalities of a traditional library,
from issuing to returning and searching books. It reduces errors, simplifies operations, and
improves user experience for both librarians and students.

3.3 Recommendation

 Develop a mobile version for students and staff.

 Integrate notifications for due and overdue books.
 Implement advanced analytics and smart search.
 Allow exporting reports as PDFs.
 Enable cloud-based access for wider usability.

12