INJIBARA UNIVERSITY

COLLEGE OF ENGINEERING AND TECHNOLOGY

DEPARTMENT OF SOFTWARE ENGINEERING

TITLE:LIBRARY MANAGEMENT SYSTEM PROJECT

PREPARED BY GROUP SIX

NAME ID NUMBER
1,Eyob kelemu……………………………………………………………………..> 1500800
2,Mengistu Abawa……………………………………………………………..> 1500977
3,Daniel Ayen………………………………………………………………………> 1500711
4, Kidist Adal…………………………………………………………………………>1700013
5,Bawezawit Gash………………………………………………………………..> 1500673

Advisor’name Mrs Amsalu Tesema

Submitted Mrs Amsalu T.

Submission
date…./…../….

I
 Injibara,Ethiopia(ET)

Abbreviation and acronyms

LMS ……………………………….Library Management System.
IT……………………………..Information System

II
 Executive summery
The Library Management System (LMS) project aims to modernize library operations
by developing a cloud-based system that improves accessibility and efficiency. The
traditional library systems have outdated processes which limit accessibility. The new
LMS is designed to provide a better experience for both staff and patrons through a
user-friendly interface accessible from any location with internet access.

The system intends to transform the library into a dynamic and accessible center for
learning. It addresses the limitations of the existing system, which includes a limited
number of books, insufficient space, and difficulty in searching records. The LMS
will automate routine tasks such as book check-in and check-out, reservation
management, and overdue notifications. The project will primarily benefit students,
teachers, researchers, and library staff by improving efficiency, saving time, reducing
errors, and providing easy access to resources. The system is designed to be scalable
and adaptable to the evolving needs of the library.

The project's feasibility was evaluated across technical, operational, economic, and
social aspects. The system development followed a waterfall model due to the clarity
of the requirements. The project also considered the legal aspects and implications of
implementing such a system.

III
IV
 CHAPTER ONE
INTRODUCTION
It is known that the Directorate of Library and Documentation Services is one of the departments in
Injibara university. It has been a few years since the library started providing book lending and 24-
hour reading services to the university community. It is still striving more than ever to continue the
renaissance journey and rapid growth that has started, and to achieve the third growth and
transformation plan.
The Directorate of Library and Documentation Services is not only a complete source of information
for its users, but also a leading player in the university's educational, research and community
services.
The increasing number of users of the library has led to the preparation of the guidelines in order to
make the operating system more efficient and to inform customers on how to use the library's
resources. This guide is designed to enable the entire university community to use the library facilities
equally.
The guide summarizes which books are in the circulation section, why a book should be kept on loan
for a long period of time, and to decide the payment penalty for the user who returns the books and
loses them after spending more than the allowed time.
In addition, the guidelines will cover the rights and obligations of librarians and other laws. Above all,
the guidelines emphasize the following issues. An operating system that takes transparency,
accountability and responsibility
Therefore, this guide will serve as a manifesto for sustainable development in its entirety, as a
resource for our university, especially as a work guide for our library. The guide is open to criticism
and correction at any time

1.1 background of the organization

Until the time this document was prepared, Injibara university has one library, and in the existing
rooms of the building, books are organized separately for all colleges by college, an Internet lab and
repository with more than 100 computers, and reading and discussion rooms that can accommodate
more than 8000 students.Libraries have long been the heart of educational institutions, serving as
repositories of knowledge and fostering intellectual growth among students and faculty. Injibara
University, a growing academic institution, exemplifies this tradition with its well-organized library. As
of the time this document was prepared, Injibara University boasts a single, central library that plays a
crucial role in supporting the university's academic mission.
Physical Structure and Organization
The library at Injibara University is designed to cater to the diverse needs of its students and faculty.
The building is thoughtfully organized, with separate sections dedicated to the various colleges within
the university. This segregation ensures that students can easily access resources relevant to their
specific fields of study. Each college has its own designated area within the library, where books and
other materials are systematically arranged, fostering an environment conducive to focused academic
research.
Technological Integration
One of the standout features of the Injibara University Library is its commitment to integrating
technology to enhance learning and research. The library houses an Internet lab and repository
equipped with over 100 computers. This digital hub provides students with access to online
databases, e-books, and other electronic resources, broadening their horizons beyond traditional
print materials. The availability of such technology ensures that students can stay abreast of the latest
developments in their fields and leverage digital tools for their academic work.
Reading and Discussion Spaces
In addition to its extensive collection of resources, the Injibara University Library offers ample space
for reading and discussion. The library can accommodate more than 8000 students at any given time,
providing a comfortable and quiet environment for individual study. Furthermore, designated
discussion rooms are available for group work and collaborative projects. These spaces encourage
interaction and the exchange of ideas among students, fostering a collaborative academic culture.
Library Management System

1
To manage its extensive collection and ensure efficient operations, the Injibara University Library
likely employs a Library Management System (LMS). An LMS automates various library functions, such
as cataloging, circulation, and inventory management. By doing so, it reduces the administrative
burden on library staff and ensures accurate tracking of resources. The system also enhances user
experience by offering features such as online catalog searches, resource reservations, and
automated notifications for due dates and overdue items.
Academic Support and Community Engagement
The Injibara University Library plays a pivotal role in supporting the academic endeavors of its
students and faculty. It provides access to a wealth of resources, from textbooks and academic
journals to digital media and online databases. The library staff are dedicated to assisting users in
finding the information they need, offering research support and guidance. Additionally, the library
serves as a hub for academic events, such as lectures, workshops, and book discussions, further
enriching the intellectual life of the university community.

1.2 Statement of the problem

Injibara university library is having difficulty integrating various formats, including :-
Limited resource:- have a limited number of books especially for freshman students,a poor
environment,means their is insufficient room,chair.
User involvement:-Some systems not involve users much in the process, and not be able to gather
information about user interests.
Resource allocation:- A library not allocate resources well to meet the needs of students and
teachers. As enrollment and staff increase, libraries need to invest more resources.
Difficulty searching records:- Manual systems can make it difficult to search for records.
Risk of file damage or loss: Manual systems can increase the risk of file damage or loss

1.3 Objective of the project

1.3.1 General objective
The objective of the LMS management system project is used to design and implement an efficient
and user friendly system that automates the various tasks associated with managing library.
1.3.2 Specific objectives
The specific objectives of this project include:-
* Efficient Book Management: Streamlining the process of book acquisition, catalogue, and tracking
to ensure an organized and easily accessible collection.
* User-Friendly Interface: Developing an intuitive and user-friendly interface for library staff and
patrons to facilitate easy navigation, quick retrieval of information, and seamless interaction with the
system.
* Automation of Processes: Automating routine library tasks such as book check-in and check-out,
reservation management, and overdue notifications to improve operational efficiency and reduce
manual workload.
* Enhanced Search and Retrieval: Implementing an advanced search mechanism to allow users to
quickly locate books, authors, or genres, promoting a more efficient and enjoyable library experience.
* Integration with Other Systems: Offering the flexibility for integration with other academic or
administrative systems to create a cohesive and interconnected information ecosystem within the
institution.
* Scalability: Designing the system to be scalable, allowing for easy expansion and adaptation to the
evolving needs of the library as it grows over time.

1.4 Scope of the project

Library Management System Project is basically updating the manual library system into an
internet-based web application so that the users can know the details of their accounts, availability of
books and maximum limit for borrowing and many more features.
The project is specifically designed for the use of librarians and library users. The product will work as a
complete user interface for library management process and library usage from ordinary users. Library
Management System can be used by any existing or new library to manage its books and book
borrowing, insertion and monitoring. It is especially useful for any educational institute where
modifications in the content can be done easily according to requirements.

2
The project can be easily implemented under various situations. We can add new features as and
when we require, making reusability possible as there is flexibility in all the modules. In terms of
performance, tools available, cross platform compatibility, libraries, cost (freely available), and
development process these languages are pretty compatible

1.5 Limitation
Library Management System (LMS), "limitation" refers to performance of the system those are faced
in our project,
1,Shortage of time
The time allotted for the development of the system was not sufficient to build large-scale and
complex system.
2,Lack of experience
As a second year software engineering students, we lack a lot of technical knowledge and expertise in
developing systems that can actually be implemented and serve people in the real world.
3,Scarcity of resources
Developing a fully functional library management system requires gathering, thorough examination,
and understanding of business processes, documents, and information that can only be accessed from
the main office of the library

1.6 System development methodology

In software engineering, a system development methodology refers to the framework that is used to
structure, plan, and control the process of developing an information system.
Software development methodologies define the processes we use to build software. These
methodologies are also referred to as Software Development Process Models. Each methodology
follows a series of steps unique to its type, to ensure success in the process of software development.

1.6.1. System Development Process Model

The process model we used to develop the system is waterfall model.The waterfall model is a
sequential approach, where each fundamental activity of a process represented as a separate phase,
arranged in linear order. This model requires planning and scheduling activities before starting
working on them, it is plan-driven. Plan-driven process is one in which all the activities are first
planned, and then each progress is measured against the plan.
We choice waterfall model because it enables
1,requirement were well known ,clear and fixed.
2,chances of ambiguity are less so the product definition is stable.
3,technology is well understood by team due to prior experience.
4,once the product is ready then it can be customized and deployed in the user environment to make
it available the end user.
5,once the product is developed ,we can add few more features in the feature release.

1.6.2 System Development Approach

The waterfall model development approach is used in situations where there is a need
for a highly structured and systematic approach to software development. It can be effective in
ensuring that large, complex projects are completed on time and within budget, with a high level of
quality and customer satisfaction
Diagram 1

3
1.6.3 System Development tools
System development tools for library management systems (LMS) help to design the
architecture, modules, and data flow of the system. These tools can also help to determine
the user interfaces, database architecture, and integration points with external systems
1.7 significance of the project
Improve efficiency:LMS help librarians perform their daily tasks more efficiently.
Save time:- LMS can automate manual tasks, such as entering data and writing records,
which can save time.
Reduce errors: LMS can help reduce errors in data management.
Provide easy access: LMS make it easier for users to find books and other resources.
Store data:LMS can store valuable data and information for long periods of time.
Make libraries cost-effective: LMS can help make libraries more cost-effective.

1.7.1 beneficiary of the project

This project is useful for
* students
* teachers
* reasechers
* staff members of the library
* we as a user of the library and the developer of a new LSM,

1.8 Feasibility study

A feasibility study helps you to evaluate a project's benefits and risks, and to compare
them with alternative solutions. It can help you to determine if the project is worth pursuing, and if so,
how to plan and execute it effectively. A feasibility study for an LMS project should cover four main
areas: technical, operational, economic, and social feasibility.
1.8.1 Operational feasibility
Operational feasibility refers to the impact of the LMS project on the library's daily
operations. It also evaluates LMS user acceptance and satisfaction. Operational
feasibility helps you answer the following questions: How will the LMS improve
library service efficiency and quality? How will the LMS affect the roles and
responsibilities of the library staff and users? How will the LMS integrate with the
library procedures? How will the LMS facilitate communication among library
stakeholders? How easy is it to use and learn the LMS.
1.8.2 Technical feasibility
Technical feasibility assesses the availability and suitability of the
hardware, software, network, and security requirements for the LMS project. It
also evaluates the technical skills of the project team and users. Technical
feasibility helps you to answer questions such as: What are the functional and

4
non-functional requirements of the LMS? What are the best technologies and
platforms to use for the LMS? How compatible is the LMS with existing and future
systems? How reliable and secure is the LMS? How easy is it to maintain and
update the LMS?
1.8.3 Legal Feasibility
A legal feasibility for a library management system involves evaluating
the legal aspects and implications of implementing such a system. This study
assesses whether the proposed library management system complies with
relevant laws and regulations, and identifies potential legal risks and
considerations

1.8.4 Economic feasibility

Economic feasibility addresses the LMS project's costs and benefits. It also
evaluates the return on investment (ROI) and the break-even point. Economic
feasibility addresses these questions: What are the initial and recurring costs of
the LMS project? What are the project's direct and indirect benefits? How long will
it take to recover the costs of the project? How will the project affect the library's
budget and revenue? How will the project cope with changes in the market and
demand?

1.9 project schedule

A project schedule is essentially a timeline that outlines all the tasks and milestones that need to be
completed in a project, along with the dates when they should be started and finished.

Table 1 project schedule

N phase Task Start End Dur Responsib

o date date atio le team
n members
1 introducti Background 01/05 02/0 one Eyob and
on organization,statement /2017 5/20 day bezawit
of the 17 s
problem,objective of
the project,
System development 03/05 05/ Two Eyob and
methodology,system /2017 o5/2 day bezawit
development 017 s
approach,feasibility
study
Requirem Current system 06/05 08/0 Two Danel and
2 ent description,and major /2027 5/20 day mengstu
analysis function,and existing 17
problem

5
 Requirement 09/05 10/0 0ne Danel and
gathering,and its /2017 5/20 day mengstu
methods, 17 s

Proposed system
description

System System overview 12/05 14/0 Two Danel and

3 Model modeling up to usecase /2027 5/20 day mengstu
model, 27 s

Class diagram up to 15/05 17/0 Thre Danel and

user interface /2017 5/20 e mengstu
17 day
s
4 System Introduction up to 18/05 20/0 Two Yared and
design system decomposition /2017 5/20 day kidst
17 s

Deployment diagram to 21/05 22/0 One Yared and

package diagram /2027 5 day kidst
2017 s

5 Conclusio Conclusion 23/05 23/0 The All group

n and /2017 5 sam member
recomme Recommendation 2017 e
ndation day
s

1.9.1 work break down

The team that develops the project consists of six individuals. And the work break down is
delegated to the members of the team as shown in the following table

Table 2. Work breakdown.

No Roles or task Team mebers

1 Introduction Eyob and bezawit

2 Requirement analysis and Daniel and

system model mengstu
3 System design and conclusion Yared and kidst
and recommendation

1.9.2 project budget

6
The development of the library management system involves several material costs,
categorized as follows.

Hardware Cost:

 Desktop computers were provided by the university.

 The team members used their own laptops for individual tasks.
 Additional hardware devices required included flash drives, paper, pens, markers, and other
similar items

Software Cost:

 Most of the software and libraries needed for the project were free to download and use.
 An exception was Wondershare Edraw Max, for which a cracked version was used due to cost
consideration
 Generally, no significant expenses were incurred for the software components of the project

These categories outline the primary material costs involved in the system's development, ensuring that
the project stays within budgetary constraints while utilizing available resources efficiently.

Chapter Two-Requirement
Analysis
2.1 Current system description
In the current situation, both students and other users of the library have to show
their ID when entering the library. In addition, it is the duty of librarians to keep
readers ID when borrowing books. Not only this but also doing with one small computer
classes, one small masters classes and large manual book store classes in a large hall. And the librarian
adjust the manual books, give the books when student wants and manages the overall library system.
2.1.1 Major function of the current system
The major functionalities of library management system are :
 Event management: librarians manage the student activities by using security camera .
 Face recognition: when students enter to the library the scan machine scans students face.
 Cataloging: Makes it easy to search for books, magazines, journals, and digital media
2.1.2 problem of existing system
When we develop a library management system (LMS), it's essential to be aware of potential
limitations that could impact the project's success. Here are some common limitations you might
encounter:
1. Scope Limitations:-Deciding on which features to include can limit the system's functionality. You
may need to prioritize essential features over more advanced ones.
• User Roles: The system may only cater to specific user roles (e.g., librarians, members) and not
accommodate other roles (like administrators or external users).
2. Technical Limitations:-
• Technology Stack: The choice of programming languages, frameworks, and databases can limit
scalability and performance.
• Integration with Existing Systems: If the library has existing systems (e.g., cataloging, payment
processing), integrating with them may be challenging.
• Platform Compatibility: Ensuring the system works across various devices and operating systems can
be a limitation.
3. User Experience Limitations
• Usability: Designing an intuitive user interface can be challenging, especially for users who may not
be tech-savvy.
• Accessibility: Ensuring the system is accessible to users with disabilities might require additional
effort and resources.

7
4. Data Management Limitations
• Data Migration: If transitioning from an existing system, migrating data accurately can be complex
and time-consuming.
• Data Security: Protecting sensitive user information and ensuring compliance with data protection
regulations can be a significant challenge.
5. Budgetary Constraints
• Funding: Limited budget can restrict the scope of features, technology choices, and the ability to
hire skilled developers.
• Maintenance Costs: Ongoing support and maintenance costs can be a concern if not planned for
adequately.
6.Time Constraints
• Project Timeline: Limited time for development can lead to rushed features or inadequate testing,
impacting quality.
• Updates and Upgrades: Regular updates may be challenging to implement if the initial
development is rushed.
7. User Adoption
• Training Needs: Users may require training to effectively use the new system, which can be
resource-intensive. • Resistance to Change: Existing users may resist adopting a new system due to
familiarity with previous processes.
8. Regulatory Compliance
• Legal Requirements: Compliance with copyright laws and licensing agreements for books and digital
resources can complicate system design.
9. Performance Limitations
• Scalability: The system may struggle to handle increased loads as the number of users or data
grows.
• Response Time: Performance issues may arise if the system is not optimized for quick searches and
transactions.

2.2 Requirement Gathering

Requirement gathering is a way of collect information to solve problems that are
currently happening in Library. It is crucial process for library management
systems development that involves collecting and defining the needs and
expectations of information for a particular project or system. It is an essential
step to ensure that identified problems effectively
2.2.1 Requirement Gathering methods
Here are several methods of requirement gathering that can be to collect
information from different stakeholders.
1. Interviews: One-on-one discussions with stakeholders to gather detailed
insights about their needs, expectations, and pain points.
2. Surveys and Questionnaires: Structured forms that can be distributed to a
larger audience to collect quantitative and qualitative data about their
requirements.
3, Observation: Watching users interact with existing systems or workflows to
identify needs and areas for improvement based on real-world usage
4,Document Analysis: Reviewing existing documentation, such as business
plans, user manuals, and system specifications, to extract relevant requirements
5,Use Cases: Developing use case scenarios that describe how users will interact
with the system, which helps in identifying functional requirements.
6,Feedback from Customer Support: Gathering insights from customer
support teams who interact with users and understand their challenges and
needs.

2.2.2 Bussiness Rules

8
Business rules are specific guidelines or constraints that govern the operations,
decisions, and behaviors within a system. For a Library Management System
(LMS), business rules help define how the system should function in relation to
users, resources, and processes.
Here are some examples of business rules for a Library Management System:

 Library users must not make any noise after entering the library.
 Readers should handle books carefully.
 Readers should return to the place after reading the books.
 It is forbidden to enter the library by sandal.
 It is forbidden to enter the library any types of food and drink.
 Students must show their ID when they enter to the library.
2.3 proposed system description
The "Proposed System Description" for a Library Management System (LMS)
outlines the envisioned features, functionalities, and architecture of the system
that is being proposed to address the needs of a library. This description serves as
a blueprint for developers, stakeholders, and decision-makers, detailing how the
new system will improve upon existing processes or replace outdated systems.
2.3.1 Overview
A Library Management System (LMS) is a sophisticated tool designed to handle the day-to-day
operations of a library efficiently.
The Library Management System (LMS) is a digital solution designed to automate and streamline
library operations. It provides a comprehensive platform for managing books, users, and various
library services, enhancing both the efficiency and user experience for library staff and patrons.
2.3.2 Functional requirement
A functional requirement specifies what a library management system should do, describing its
functions, tasks, or behaviors that it must accomplish. It's essentially what the LMS system needs to
perform to fulfill user needs. " the library management system must allow users to log in with a
username and password.
Here are examples:
 Book Management: The system should cover tasks related to book acquisition, cataloging, and
organization within the library.
 User Management: Creating and managing user accounts, handling patron information, and
providing authentication for library services.
 Circulation Management: Automating the process of book check-in, check-out, and reservation
to streamline circulation activities.
 Search and Retrieval: Implementing a robust search mechanism for users to quickly locate
books, authors, and other library resources.
 Reporting and Analytics: Generating reports on library usage, circulation trends, and popular
genres to aid decision-making.
 Security and Access Control: Ensuring the security of sensitive data and implementing access
controls to manage user privileges.
2.3.3 Non Functional Requirement
A non-functional requirement specifies how a library management system should perform rather than
what it should do. For a library management system, these might include:
 Usability: Ensuring a user-friendly interface that promotes ease of navigation
and a positive user experience for both library staff and patrons.
 Scalability: Designing the system to accommodate growth in the library's
collection and user base over time.
 Performance: Meeting performance standards to ensure timely response
and efficient processing of library transactions.
 Reliability: Building a reliable system that minimizes downtime and ensures
the continuous availability of library services.
 Security: Incorporating robust security measures to protect against
unauthorized access, data breaches, and other security threats
 Maintainability: The system should be designed in a way that makes it easy to update and
maintain

9
 CHAPTER THREE: SYSTEM MODEL
3.1 System model overview
System modeling is a crucial phase in the development of a Library Management System (LMS). It
involves creating abstract representations of the system to understand, design, and document its
structure and behavior. These models serve as blueprints for developers and stakeholders, ensuring
that the system meets the specified requirements and functions efficiently.
3.2 Use case model
A use case model represents the functional requirements of a library management system through a
series of interactions between users (actors) and the system itself. It helps to identify and document
the specific functionalities that the system must provide to meet the needs of its users.
3.2.1 Identifing Actors
Here are some examples of library management system actors
 Librarian:Manages the overall operations of the library .Responsibilities include catalog
management, user registration, reporting, and overseeing library activities.
 Students: Registered users of the library. And they can borrow and return books, reserve books,
and access various library services
 Administrator:Manages system configuration and maintenance. Responsibilities include setting
up user roles, permissions, and ensuring the system runs smoothly
3.2.2 Identifing use cases
Here are some identifying uses case of library management system
Sign Up: Sign up is the process by which a new user registers to become a member of the library. This
involves creating a new account in the LMS.
Sign In: Sign in refers to the process of logging into an existing library account. This allows users to
access their personal account and use the library's digital services.
Sign Out: Sign out is the process of logging out of the library account once the user has finished their
session.
Book search: refers to the process of looking for specific books or types of books within a library or an
online catalog.
Book borrowing: within a Library Management System (LMS) refers to the process by which library
members can take books out of the library for a specified period.
book return: refers to the process of a library member bringing back borrowed books to the library.
Check in/Check out books: Handling the process of checking books in and out.

3.2.3 Identifing scenarios

Scenario: User Sign Up for Library Management Syste:
For this scenario student student x is an actor then the scenario of student x for library
management system and library management system
Preconditions for student x is:
 Student x has decided to join the library and access its resources.
 Student x has access to a device with an internet connection.
Main Success Scenario:
1,Student x navigates to the library's website or opens the library management system app.
2,Student x clicks on the "Sign Up" or "Register" button
3, The system displays a sign-up form requesting essential information such as:
Full name
Email adress
Password
Phone number

4, Student x fills in all the required fields.

5,Student x reads and agrees to the library's terms and conditions by checking a checkbox.

6, Student x clicks the "Submit" button.

10
7, The system validates the entered information. If any information is missing or incorrect, the system
prompts student x to correct it.

8,Upon successful validation, the system sends a verification email to student x provided email address.

9,Student x checks her or his email and clicks on the verification link.

10, The system verifies the email address and completes the registration process.

11, Student x receives a confirmation message on the screen, along with a welcome email containing
her membership details and instructions on how to access the library's resources .

 Post conditions
 Student x is now a registered member of the library.
 Student x can log in to the library management system using her email address and password.
 Student can access the library's resources and services based on her membership type.

Scenario: User Sign In for Library Management System.

For this scenario the actor is registered student x and library management system .
Precondtion
 Student x is a registered member of the library with a valid account.
 Student x has access to a device with an internet connection.
 Student x has the login credentials (email and password) for his account
Main successe scenario
1, Student x navigates to the library's website or opens the library management system app.
2, Student x clicks on the "Sign In" or "Login" button.
3, The system displays a sign-in form requesting the following information:
 Email Address.
 Password.
4, Student x enters hisor her email address and password.
5, Student x clicks the "Sign In" button.
6, The system validates the entered credentials. If the credentials are incorrect, the system prompts
student x to re-enter them.
7, Upon successful validation, the system grants student x access to his or her personal account.
8, Student x sees a welcome message on his or her dashboard and can now access the library's digital
services, such as:
 Viewing borrowed books.
 searching for available books.
 reserving books.
 accessing digital resources like e-books and audio books.
 managing account details.
Postconditions:
 Student x is successfully signed in to his library account.
 Student x can perform actions available to him or his based on his or her membership type and
account status.
Scenario: User Sign Out for Library Management System.
For this scenario the actor is registered student x and library management system .
Preconditions:
 Student x is currently signed in to her or his library account.
 Student x has finished her or his session and wishes to log out.
Main Success Scenario
1, Student x navigates to the library management system's website or app, where she or he is already
signed in.
2, Student x clicks on her or his profile icon or navigates to the account settings menu.
3, Student x clicks on the Sign Out or Log Out button.
4, The system prompts student x to confirm that he or she wants to sign out.

11
5, Student x confirms her or his intention by clicking "Yes" or "Confirm.
6, The system safely logs student x out of her or his account.
7, Student x sees a confirmation message indicating she or he has successfully signed out.
8, Student x is redirected to the library management system's homepage or sign-in screen.
Postconditions
 Student x is successfully signed out of her or his library account.
 Student x session is terminated, and her or his account is secure.
 Student x can sign in again whenever she or he wishes to access the library's services.

3.2.4 Identifying the relationship Among Actors and use-causes

Table _3__ The Relationship among actors and use cases

No Actor Use case

1 student Signup
log in
log out
Search book
Borrow book
Return book
Check in and chekout books

librarian Signup
Signin
2 Signout
Checkout a book of member
Add new book
Update book information
Check in return books
Delete books
Renew book for members
Manage member account
Generate reports

Administrator Signup
Signin
Signout
User management
3 System configration
Backup and restore
Policy management
Resource management
Event management

12
 3.2.5 usecase diagram

3.2.6 Descripitoin of usecase model

A use case model description is a visual representation of the interactions between users (actors) and
a system to achieve a goal.
The Use Case Model description serves the following purposes:
 -Identify Actors: It defines the different types of users (actors) who will interact with the system.
 -Define Use Cases: It describes the specific functionalities (use cases) that the system will
provide.
 Capture Interactions: It shows how actors interact with the system to achieve their goals.
 Clarify Requirements: It helps to clarify and validate the system's functional requirements.
 Guide Development: It provides a foundation for designing and implementing the system.
Table 3
No Actor Usecase name Usecase description
1 User Register user A new user registers in the system
Search book by providing personal details
Borrow book Users search book by
Return book titles,authors or category

2 User, Login Users login to the system using

libraria, their identity.
admin
3 Librarian Add book A librarian add a new book to the

13
 Delete book library catalogue
Update A library removes book from the
bookdetails library catalogue
A library update the detail of an
existing book
4 Admin Generate The system generate reports
reports An admin assignor update user
Manage user roles
roles

3.3 Class Diagram

3.4 Activity Diagram

14
3.5 Sequence Diagrams

15
 3.6 user Interface
In the context of a Library Management System (LMS), the term "user interface" (UI) refers to the
means by which users interact with the software. This includes all the visual elements, controls, and
overall layout that enable users to perform tasks within the system. A well-designed user interface is
crucial for ensuring that both library staff and patrons can efficiently navigate the system and access
the resources they need.

Key aspects of a user interface in a Library Management System include:

1. Accessibility: The UI should be easy to use for all users, including staff and library patrons,
regardless of their technical skill level.

2. Navigation: Clear menus, buttons, and links that allow users to easily find information about books,
journals, and other resources, as well as perform tasks such as checking out items or renewing loans.

3. Search Functionality: A robust search feature that allows users to search for materials by various
criteria (title, author, ISBN, etc.) and filter results effectively.

4. User Accounts: Interfaces for patrons to create and manage their accounts, check their borrowing
history, and view due dates or fines.

5. Admin Features: For library staff, the UI should include features for cataloging new materials,
managing inventory, tracking loans, and generating reports.

6. Responsive Design: The interface should be designed to work well on various devices, including
desktops, tablets, and smartphones.

7. Feedback Mechanisms: Elements that provide feedback to users about their actions (e.g.,
confirmation messages when an item is checked out or returned).

8. Visual Design: An aesthetically pleasing layout that aligns with the library’s branding and enhances
the user experience through appropriate use of colors, fonts, and graphics.

A user-friendly interface can significantly improve the efficiency of library operations and enhance the
overall experience for both staff and patrons

CHAPTER FOUR:SYSTEM DESIGN

4.1 INTRODUCTION
System design is a multifaceted process that transforms abstract ideas and requirements into a
structured plan for creating a functional and efficient system. It serves as the blueprint for the
construction of both hardware and software systems, ensuring that all components work seamlessly
together to meet specific needs. The importance of system design lies in its ability to provide a
comprehensive understanding of how different parts of a system interact, contributing to the overall
performance, scalability, and reliability of the final product.
4.2 Current software Architecture
The current library management system used by manual. Hence, there is no software architecture to
be described here.

4.3 Proposed Software Architecture

16
 Proposed Software Architecture is the foundation for system structure, behavior, and interaction.The
structure of the system involves organizing various components and their relationships to ensure
functionality and efficiency. The behavior aspect focuses on how these components interact and
respond to different inputs, ensuring the system performs as intended under various conditions.
Interaction encompasses the ways in which different parts of the system communicate and work
together to achieve the desired outcomes.

A well-defined software architecture ensures that these elements are aligned, allowing for seamless
integration, scalability, and maintainability. By laying down clear guidelines and frameworks, it
facilitates smoother development processes, easier debugging, and future enhancements. Overall, the
architecture is a critical blueprint that guides the entire software development life cycle, ensuring the
final product meets both user and business requirements efficiently.

4.3.1 System Decomposition

In a library management system, system decomposition helps to break down the system into
manageable component or modules, well-organized ,parts to ensure efficiency and clarity. This helps in
understanding the structure and functionality of the system more clearly, making development,
maintenance, and scalability easier.

Here’s a breakdown of the main components our library management system

1,User Management
 Authentication: Handles user login, logout, and password management.
 User Roles:Manages different user roles (e.g., Admin, Librarian, Member) and their permissions.
2,Catalog Management
 Book Database: Stores information about books, including title, author, genre, and availability.
 Search Functionality: Allows users to search for books using various filters like author, title,
generation, etc.
3,Borrowing and Returning
 Check-Out/Check-In: Manages the borrowing and returning of books, including due dates and
fines.
 Reservation System: Allows users to reserve books that are currently checked out.
4,Administration
 Report Generation: Generates various reports like overdue books, frequently borrowed books,
user activity, etc.
 System Maintenance: Includes database backups, user management, and system updates.
4.3.2 Deployment Diagram
A deployment diagram for a library management system shows the hardware
components (nodes) and the software components (artifacts) that are deployed on
those nodes. It helps in understanding the physical deployment of the system and
how different components interact in the real world.
Here is examples of deployment diagram for LMS

17
 4.3.3 Access Control and security
Access Control and Security in a library management system refer to the measures and mechanisms
put in place to protect data, ensure only authorized users can access specific resources, and prevent
unauthorized access, data breaches, and other security threats. To show this we use access control
matrix.

Access control matrix shows which functions are performed by which system users.

Table 4

Actor Function
Sign Sign sign Borrow Return Update Issue Recive Manage users
up in out book book catalogue book book
student     
librarian     
system  

18
 4.3.5 Package Diagram
A package diagram in the context of a library management system is a type of UML (Unified Modeling
Language) diagram that shows the structure and organization of the system into different packages or
modules. Each package represents a collection of related classes, interfaces, and other elements.
Package diagrams help in understanding the dependencies and relationships between different parts
of the system.

Chapter five(5) -conclusion and recommendation

5.1 conclusion
The Library Management System (LMS) project represents a significant advancement in how libraries
operate and serve their communities by addressing the limitations of traditional library management
systems. The new system is designed to provide a more efficient and engaging library experience for
both patrons and staff. The LMS modernizes library operations by using a cloud-based system to
improve accessibility and efficiency. The system is intended to transform the library into a dynamic
and accessible center for learning, meeting the evolving needs of users in the digital age. The LMS
addresses the limitations of the existing system, such as a limited number of books, insufficient space,
and difficulties in searching records. The system offers enhanced search capabilities, automated
inventory management, and mobile accessibility which empowers both patrons and staff. It provides a
user-friendly interface that is accessible from any location with internet access. The LMS also provides
access to digital collections of e-Books, audio-books, and journals. Automated inventory management
provides real-time stock levels and simplified reporting. The system offers advanced search capabilities
with personalized recommendations. Mobile apps for iOS and Android devices further extend
accessibility, allowing patrons to engage with the library on the go. Robust data analytic and reporting
tools provide valuable insights for data-driven decision-making, enabling libraries to better understand
user needs and optimize resource allocation. The LMS automates routine tasks such as book check-in
and check-out, reservation management, and overdue notifications. The project also prioritizes data
security and user privacy. The system is designed to be scalable and adaptable to the evolving needs of
the library. The project was developed using a waterfall model because the requirements were well
known, clear, and fixed. The LMS ensures that libraries remain relevant and vital
resources for information and knowledge in an increasingly digital world. Ultimately,
the modernized LMS ensures that libraries remain relevant and vital resources for
information and knowledge in an increasingly digital world.

19
 5.2 Recommendation

The Library Management System (LMS) project is recommended as a significant

advancement in how libraries operate and serve their communities, addressing the limitations of
traditional library management. The system's enhanced search capabilities, automated inventory
management, and mobile accessibility are key features that empower both patrons and staff, creating a
more efficient and engaging library experience. The LMS transforms the library into a dynamic and
accessible hub for learning, discovery, and community engagement in the digital age. The project aims
to modernize library operations by developing a cloud-based system that improves accessibility and
efficiency. The traditional library systems have outdated processes which limit accessibility. The new
LMS is designed to provide a better experience for both staff and patrons through a user-friendly
interface accessible from any location with internet access. The system is intended to transform the
library into a dynamic and accessible center for learning, meeting the evolving needs of users in the
digital age.

Additionally, the LMS addresses the limitations of the existing system, such as a limited number of
books, insufficient space, and difficulties in searching records. The new system offers enhanced search
capabilities, automated inventory management, and mobile accessibility, empowering both patrons and
staff. It provides a user-friendly interface accessible from any location with internet access. The LMS
also provides access to digital collections of e-Books, audi-obooks, and journals. Automated inventory
management offers real-time stock levels and simplified reporting. The system also offers advanced
search capabilities with personalized recommendations. Mobile apps for iOS and Android devices
further extend accessibility, allowing patrons to engage with the library on the go. Robust data analytic
and reporting tools provide valuable insights for data-driven decision-making, enabling libraries to
better understand user needs and optimize resource allocation. The LMS automates routine tasks such
as book check-in and check-out, reservation management, and overdue notifications. The project also
prioritizes data security and user privacy. The system is designed to be scalable and adaptable to the
evolving needs of the library. Data analytic and reporting tools provide valuable insights for data-
driven decision-making, allowing libraries to understand user needs and optimize resource allocation.

The project was developed using a waterfall model because the requirements were well known, clear,
and fixed. The LMS ensures that libraries remain relevant and vital resources for information and
knowledge in an increasingly digital world. Ultimately, this modernized LMS ensures that libraries
remain relevant and vital resources for information and knowledge.

20
 Reference
 Laudon, K. C., & Laudon, J. P. (2015). Management Information Systems:
Managing the Digital
Firm (13th ed.). Pearson Education.
 Sommerville, I. (2011). Software Engineering (9th ed.). Addison-Wesley.
 Date, C. J. (2004). An Introduction to Database Systems (8th ed.). Addison-
Wesley.
 IEEE. (1998). IEEE Recommended Practice for Software Requirements
Specifications (IEEE Std
830-1998). IEEE
 Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach (8th ed.).
McGraw-Hill.
 Schwalbe, K. (2015). Information Technology Project Management (8th ed.).
Cengage Learning.

21