Academia International College

Affiliated to Tribhuvan University

Institute Of Science and Technology

Gwarko, Ring Road, Lalitpur -7, Nepal

Report On
“Library Management System”
Submitted To:
Department Of Computer Science and Information Technology
Academia International College

Submitted By: Submitted On:

Amita Kumari(23995)

Anjali Shrestha(23997) Signature:

Kabita Maharjan(24007)
 ACKNOWLEDGEMENT

This is our very first project on report writing. We are currently in our learning phase and would
like to thank you for taking the time to read this. We are pleased and thankful to our team leader,
Ms. Alka Jha, who has given us this opportunity to work on this Report Writing assignment. We
would also like to thank all our group members for the help they gave to complete this project.
Finally, we would like to thank our teacher Mr. Jagannath Luitel for his support and guidance in
completing this project. Our task was to design a library management system. We utilized lucid
charts to make the various diagrams for this report in order to be completed. We will be solely
responsible for any errors made, and we will do everything in our power to make them right. The
expertise of the group as a whole is also reflected in this report, which demonstrates our
comprehension of this crucial part of the library sector. We would like to express our gratitude to
every team member who tirelessly worked on this project and shared their expertise with us so
that we could all participate equally to its successful completion. We hope that in the future we
can continue to work together with Ms. Jha and her team on more projects like this to help us in
our development as professionals in the field of Information Management.

Thank you for taking your time to look through this project!

2
 ABSTRACT
Library management is a project to electronically manage and store book information according
to student needs. This system helps both students and library administrators to keep track of all
books available in the library at all times. This allows both administrators and students to search
for the books they need. Universities will have to continuously check issued and returned books
and even calculate penalties. Performed manually, this task is tedious and error prone. These
errors are avoided by allowing the system to track information such as the date of publication,
the last date the book was returned, and even finer details. Therefore, there is no need to
manually track this information and the possibility of error is eliminated. Therefore, the system
greatly reduces manual work and eliminates the possibility of small errors to keep the library
running smoothly.

3
Contents
ACKNOWLEDGEMENT .......................................................................................................................... 2

ABSTRACT ................................................................................................................................................. 3

Table of Figure.............................................................................................................................................. 5

ABBREVIATION......................................................................................................................................... 6

Chapter 1 ..................................................................................................................................................... 7

1. Introduction ......................................................................................................................................... 7

1.1 Statement of problem.................................................................................................................... 7

1.2 Objectives....................................................................................................................................... 7

1.3 Scope............................................................................................................................................... 8

1.4 Limitations ..................................................................................................................................... 8

Chapter 2 ..................................................................................................................................................... 9

2. Methodology ............................................................................................................................................ 9

2.2 Literature Review ............................................................................................................................. 9

2.3 Development Methodology ............................................................................................................. 10

2.3.1 System Development Life Cycle (SDLC) ............................................................................... 10

2.3.2 Waterfall Methodology ............................................................................................................ 11

Chapter 3 ................................................................................................................................................... 12

3. System Analysis ..................................................................................................................................... 12

3.2. Requirement Analysis .................................................................................................................... 12

3.2.1 Functional Requirements ........................................................................................................ 12

3.2.2. Non-Functional Requirements ............................................................................................... 14

3.3. Feasibility Analysis ........................................................................................................................ 15

3.3.1. Technical Feasibility ............................................................................................................... 15

3.3.2 Operational Feasibility ............................................................................................................ 16

4
 3.3.3. Economic Feasibility ............................................................................................................... 16

3.4. Data Model ..................................................................................................................................... 16

3.5. Process Model ................................................................................................................................. 17

Chapter 4 ................................................................................................................................................... 20

4. System Design .................................................................................................................................... 20

4.1. System Design ................................................................................................................................. 20

4.1.1. Architecture Design ................................................................................................................ 20

4.1.2. Database Design ...................................................................................................................... 21

4.1.3. Sequence Diagram................................................................................................................... 22

4.1.4. Class Diagram ......................................................................................................................... 23

4.1.4. Flowchart ................................................................................................................................. 24

References ................................................................................................................................................... 25

Table of Figure
Figure 1 Waterfall Method.......................................................................................................................... 11
Figure 2 Use Case Diagram ........................................................................................................................ 14
Figure 3 ER Diagram .................................................................................................................................. 17
Figure 4 Context Diagram .......................................................................................................................... 18
Figure 5 DFD Level-1 ................................................................................................................................. 19
Figure 6 DFD Level-2 ................................................................................................................................. 20
Figure 7 N-Tier Architecture ...................................................................................................................... 21
Figure 8 Database Design ........................................................................................................................... 21
Figure 9 Sequence Diagram ........................................................................................................................ 22
Figure 10 Class Diagram ............................................................................................................................ 23
Figure 11 Flowchart .................................................................................................................................... 24

5
 ABBREVIATION
LMS Library Management System

DFD Data Flow Diagram

ER Entity Relationship

SDLC System Development Life Cycle

6
 Chapter 1

1. Introduction
The term "LMS" also refers to an automated library system. A library management
system is a software application that helps a library to manage and organize its books,
journals and other materials. It is described as software created to control fundamental
housekeeping tasks in a library. The LMS assists in giving the user information on every
book in the library as well as staff contact information. Additionally, it records when a
book is published, given as a gift, or added to the library. The main components of a
library management system includes a database of the library’s holdings, a cataloging
module for adding new materials and updating existing records, a circulation module for
tracking borrowing books and returns.

A library management system helps libraries to efficiently manage and organize their
collections, and provides a convenient way for users to access and borrow materials.

1.1 Statement of problem

The library's collecting and lending operations are currently managed manually and take
a lot of time, which leads to inefficiencies and possible mistakes. For handling these
procedures and enhancing customer service, the library requires a more practical and
efficient solution. The secrecy of library transaction reports and documents is not
provided by manually input data. Position, accessibility, and uninviting decor limit the
range of services that school libraries may offer, while size, obsolete fixtures and
furnishings and rigid layouts limit their capacity to engage students.

1.2 Objectives
The major objective of this library management system is to monitor services and
transactions:

 To reduce paper work and provide data security in details which will be available on
a click.
 To easily update the information of library services and operations.

7
 To computerize the categorizing, arranging, and lending of works as well as the
management of the library's collection.
 To offer users a simple interface so they can put holds, search for and access
resources, check out and return items, and more.
 To keep track of and evaluate use information in order to make choices about
collection growth and other aspects of library services.
 To make it possible for the library to provide further services like online materials
and access to digital collections.
 By making it simpler for users to access and borrow resources, as well as by sending
out timely and relevant suggestions and alerts, we want to improve the benefactor
experience.

1.3 Scope
Our system’s intended user include:

 Students
 Teachers
 Institutes

The major scope of this project are:

 Authentic users upon login.

 List the books that are available for checkout.
 The ability to reserve any books that are on hand.
 The option to cancel a prior reservation for a book.
 A profile-viewing and profile-editing interface.
 A password-reset mechanism in case the user forgets their password.
 Providing a user interface for staffs to add or remove books.
 A status page where all users may examine the books they have checked out, their
due dates, and any specific fines.

1.4 Limitations
The limitations of our project:

8
  Cost: For smaller libraries with tighter resources, implementing and maintain a
library management system can be expensive.
 Technology dependence: Since a library management system depends upon
technology, any problems with hardware or software that underlies the system
might cause disruptions in library operations.
 Limited functionality: It may not be possible to customize or integrate a library
management system with other systems because it lacks some of the features and
functionality that a library needs.
 Data security and protection of client privacy are essential since a library
management system handles sensitive client data.
 User adoption: If users or library personnel are used to the current system or feel
at ease with manual procedures, they may be reluctant to embrace a new library
management system.
 Integration with current systems: A library management system may not be able
to work with the existing systems and procedures of the library, necessitating
considerable modifications to the way the library is now run.
 Data duplication and size make backup maintenance difficult. Data analysis and
database access are time-consuming. Quickly obtaining book status is
challenging.
 Manually sorting the book is an extremely challenging task. When a book has
many entries in the library system or when a new book is uploaded, data
inconsistencies may also occur. It seems hard to add a new book, update the
information about the book and the pupils, and organize them systematically.

Chapter 2

2. Methodology
2.2 Literature Review
2.2.1 Library Management System based on N-layer architecture.

It is similar to three tier architectures but number of application servers are increased and
represented in individual tiers in order to distribute the business logic so that the logic

9
 will be distributed. N-Tier application is also known as Distributed application (Samuel,
2018 ).

2.2.2 Design and implementation of Library Management

The software used to develop Library Management System is Microsoft Visual Studio
2008 and SQL Server 2008 as the database (Chuan, 2010/11).

2.2.3 Library Management Access System

Access to a library management system is typically controlled through the use of user
accounts and login credentials. If you are a member of a library that uses a library
management system, you may have been provided with a username and password. If not,
you will need to contact the library staff to create an account and obtain login credentials.

2.3 Development Methodology

2.3.1 System Development Life Cycle (SDLC)
The System Development Life Cycle (SDLC) is a conceptual model used in project
management that describes the stages involved in an information system development
project form an initial feasibility study through maintenance of the completed
applications.

The methodology we used to develop this system is waterfall model.

10
2.3.2 Waterfall Methodology

Figure 1 Waterfall Method

A linear, sequential procedure is what distinguishes the waterfall methodology for

software development. It is frequently employed for projects with clear needs and a
predictable nature. This method works well for projects where the requirements and
scope are properly defined from the beginning.

A library management system (LMS) is a piece of software that assists in the

administration of the collection, users, circulation, and other aspects of running a library.
The standard characteristics of a library management system are cataloging, check-
in/check-out, and reporting.

11
 We believe that a library management system might benefit from the Waterfall technique
because it is a simple application with clear needs. The development process for an LMS
can go along in a linear, sequential fashion since the requirements are probably clear and
predictable.

Advantages of using waterfall methodology

 Maintaining scope of project within the requirements and needs of the stakeholders
 Establishing cost control
 Time management of all the required activities
 Provide documented evidence of the activities that govern the project

Chapter 3

3. System Analysis
3.2. Requirement Analysis
3.2.1 Functional Requirements
Functional requirements in a library management system refer to the specific functions or
features that the system must have in order to meet the needs of the library and its users.
Examples of functional requirements for a library management system include the ability
to search for and check out books, manage and track library inventory, process and track
overdue fines, and generate reports on system usage and circulation. Additionally, a
library management system may have functional requirements to integrate with other
systems, such as an authentication system to validate user credentials or an interlibrary
loan system to request books from other libraries. The Library Management System has
roles like Librarian as admin and member.

3.2.1.1. User Log In

This feature is used by the user to login the system. They are required to enter user id an
password before they are allowed to enter the system. The user id and password will be
verified and if invalid id is there user is not allowed to enter the system.

 User id provided when they register

12
  The system must only allow user with valid id and password to enter the system.
 The system performs authorization process which decides what user level can
access to.
 The user must be able to logout after they finished using system.

3.3.1.2. Register New User

This feature can be performed by all users to register new user to create account.

 System must be able to verify information.

 System must be able to delete information if information is wrong.

Admin Features

 Admin Dashboard
 Admin can add/update/delete category
 Admin can add/update/delete author, books.
 Admin can issue new book to student and also update the details when student
return book
 Admin can search student by using their student ID.
 Admin can also view student details.

Students

 Student can register yourself an after registration they will get their own id.
 After login student can view own dashboard.
 Student can update own profile.
 Student can view issued book and book return date-time.
 Student can also change own password.

13
 Figure 2 Use Case Diagram

This feature used by the user to login into system. They are required to enter user id and
password before they are allowed to enter the system .The user id and password will be verified
and if invalid id is there user is allowed to not enter the system .
3.2.2. Non-Functional Requirements
1. Easy to use

The proposed system is user-friendly and provide Graphical User Interface (GUI). The
system is designed for a user friendly environment so that student and staff of library can
perform the various tasks easily and in an effective way.

2. Performance

The system can handle a large number of concurrent users and perform searches and
other operations in a timely manner. When a library management system is implemented
librarian and user will easily access library as searching and book transaction will be very
faster.

14
 3. Security

The system will provide access to only legitimate users. It will be secure on network and
only authorized person can use it. The system is secure and protect sensitive information
of users and library.

4. Reliability

The Server would perform desired tasks as expected. The system does its work with more
accuracy like user registration to the system, user validation and authorization, book
search and issue operation, return status , and updating the database by synchronizing
between database and application.

5. Accuracy

Accuracy is another important non-functional requirement for the library management

system. The data stored about the books and the fines calculated should be correct,
consistent, and reliable.

3.3. Feasibility Analysis

Feasibility analysis is the process of evaluating a proposed system or project to determine
whether it is viable and practical to implement. Feasibility study is conducted once the
problem is clearly understood. Feasibility study is a high-level capsule version of the
entire system analysis and design process. The objective is to determine quickly at a
minimum expense how to solve a problem. The purpose of feasibility is not to solve the
problem but to determine if the problem is worth solving. A feasibility analysis for a
library management system would typically include the following components:

3.3.1. Technical Feasibility

This involves evaluating whether the proposed system can be implemented with existing
technology and resources. It includes assessing the availability of software, hardware, and
other infrastructure needed to support the system, as well as evaluating the compatibility
of the system with existing systems.

15
 3.3.2 Operational Feasibility
In this project, the management will know the details of each project where he may be
presented and the data will be maintained as decentralized and if any inquires for that
particular contracts can be known as per known as per their requirements and necessaries.
This involves evaluating whether the proposed system can be effectively and efficiently
integrated into the library's current operations. This includes assessing the impact of the
system on staff workload and procedures, as well as determining if there is enough staff
to operate and maintain the system.

3.3.3. Economic Feasibility

The computerized system will help in automate the selection leading the profits and
details of the organization. With this software, the machine and manpower utilization are
excepted to go up by 80%-90% approximately. This involves evaluating the costs and
benefits of implementing the proposed system. This includes assessing the costs of
developing, implementing, and maintaining the system, as well as determining the
potential return on investment. It also includes evaluating the costs of not implementing
the system.

Hence, our system is feasible as it is capable of meeting its needs and will provide a good
return on investment.

3.4. Data Model

ER Diagram

An Entity-Relationship (ER) diagram is a graphical representation of entities and their

relationships to each other. It is used in database design and software engineering to
model and organize data and to understand the relationships between different entities.

ER diagrams are useful for visualizing the structure of a database and for communicating
the design of a database to others. They can also be used to generate a database schema,
which is the blueprint for creating the actual database. It maps well to relational model.
The constructs used in ER model can easily be transformed into relational tables. It is
simple and easy to understand with a minimum of training. Therefore, the model can
easily be used by the database designer to communicate the design to the end user.

16
 Figure 3 ER Diagram

3.5. Process Model

DFD Diagram

DFD is a graphical representation of the flow of information in a system. It can show

incoming, outgoing, and stored data flow. There is no control flow in DFD, and there are
no loops or decision rules.
It can be used to communicate between a system analyst and anyone else involved in
developing a system. The DFD is a modelling tool for structured analysis. Data Flow
Diagrams are widely used because they facilitate visualizing the significant phases and
data involved in software-system processes.

17
 1. Context Level Diagram

Context Diagram is another name for DFD Level 0. It's a basic overview of the entire
system or process studied or modelled. It's meant to be a quick peek into the system,
displaying it as a single high-level process with connections to external entities. a context
diagram provides a general overview of a process, focusing on its interaction with outside
elements rather than its internal sub-processes.

The context diagram is given below:

Figure 4 Context Diagram

2. DFD Level-1

A Data Flow Diagram (DFD) Level 1 for a library management system would provide a
high-level overview of the flow of data within the system. The DFD would show the
main processes involved in the system, as well as the external entities that interact with
the system and the data stores used by the system.

The DFD Level 1 for a library management system:

 Check out books

 Book inventory
 User information

18
 Figure 5 DFD Level-1

3. DFD Level-2

A Data Flow Diagram (DFD) Level 2 for a library management system would provide a
more detailed view of the flow of data within the system, breaking down the processes
identified in the DFD Level 1 into smaller, more detailed sub-processes.

19
 Figure 6 DFD Level-2

Chapter 4

4. System Design
4.1. System Design
System design in a library management system refers to the process of defining the architecture,
components, interfaces, and data for the system. The design process involves taking into
consideration the functional and non-functional requirements of the system, as well as the
constraints and limitations of the environment in which the system will be implemented.

4.1.1. Architecture Design

Architecture design of a library management system refers to the overall structure and
organization of the system, including the major components, their relationships, and how they
interact with each other.

20
 Figure 7 N-Tier Architecture

4.1.2. Database Design

Figure 8 Database Design

21
4.1.3. Sequence Diagram

Figure 9 Sequence Diagram

22
4.1.4. Class Diagram

Figure 10 Class Diagram

23
4.1.4. Flowchart

Figure 11 Flowchart

24
References
Chuan, T. c. (2010/11). Library Management System. Kuala Lumpur: Tunku Abdul Rahman College.

Samuel, A. (2018 ). Design and Implementation of Library Management System. International Journal Of
Computer Applications.

25