A project report

On
Library Management System
Submitted to

Tribhuwan University
Kathmandu, Nepal

Submitted By
Saroj Thapa Magar (15381)
Tribhuwan Budha (15383)
Dipak Gurung (15362)

St. Lawrence College

Chabhil, Kathmandu

06 MAR, 2022
INTRODUCTION

Before discussing library management systems, it might help to talk about

systems. A system is something formed of parts, each of which interacts
with the other parts to achieve some common purpose. In the case of a
library management system, the parts work together to support the
management of library information resources: their acquisition,
representation and circulation. Each of the parts constitutes a subsystem
which in turn comprises a set of interconnected parts. In other words, each
of these subsystems can be broken down into yet smaller subsystems. It is
worth noting that vendors of library management systems often refer to
the main subsystems, such as acquisitions and circulations, as modules.

A library management system is an example of an information system. An

information system, whether it is computerized or not, is a system that
represents objects in a physical system, for example, information resources
in a library collection. A library management system also helps to maintain
the library in a systematic way.

The main goal of the library management system is to provide facilities to

the connect people , maintain and use the resources, entity, attributes etc in
such a way that it makes the library system useful and run in a systematic
way.
OBJECTIVES

The aims and objectives that we will be achieve after completion of

this case study are as follows:
To online book issue
To aequest column for librarian for providing new books
A separate column for digital library
A search column to search availability of books
To record of outgoing and incoming book
To interaction between the student, teacher and library
To assist formal, adult and self education.
BACKGROUND

Libraries attached to school, college, university or an institute learning is

known as academic libraries. They exist to support the goals of their parent
organizations. Variety of libraries have variety of purpose to serve their
readers. Academic library has also such purpose. It assists to the education
research, teaching and learning of the academic community.

In the context of Nepal, the history of academic library is not so long . Due
to various reasons, our educational condition is very background than
other countries. But it is in progress now than previous. Most of the school
libraries have found and looked like second hand book store house of
poorest type. Most of the academic libraries are managed still with poor
collection and without professional staffs. The concept of the library play
great role in achieving the goals and objectives the campus or institution of
higher education has still not realized. It is 10 necessary that all the
professional libraries should be organized to stimulate, to promote the
library development in Nepal. The biggest and reputed university library of
Nepal is Tribhuvan University Central Library Kirtipur.
DATA FLOW DIAGRAM (DFD)

A data flow diagram (DFD) maps out the flow of information for any
process or system. It uses defined symbols like rectangles, circles and
arrows, plus short text labels, to show data inputs, outputs, storage points
and the routes between each destination. Data flowcharts can range from
simple, even hand-drawn process overviews, to in-depth, multi-level DFDs
that dig progressively deeper into how the data is handled. They can be
used to analyze an existing system or model a new one. Like all the best
diagrams and charts, a DFD can often visually “say” things that would be
hard to explain in words, and they work for both technical and
nontechnical audiences, from developer to CEO. That’s why DFDs remain so
popular after all these years. While they work well for data flow software
and systems, they are less applicable nowadays to visualizing interactive,
real-time or database-oriented software or system.

Types of DFD
Physical DFD - This type of DFD shows how the data flow is actually
implemented in the system. It is more specific and close to the
implementation

Logical DFD - This type of DFD concentrates on the system process, and
flow of data in the system. For example in a Banking software system, how
data is moved between different entities.

Levels of DFD

Level - 0 diagram:
It is also known as context diagrams, which are the most basic data flow
diagrams. They provide a broad view but offer little detail. Level 0 data flow
diagrams show a single process with its relationship to external entities.

Level - 1 diagram:
They have more details then the context diagram. In 1-level DFD, the
context diagram is decomposed into multiple processes. In this level, we
highlight the main functions of the system and break down the high-level
process of 0-level DFD into sub-processes.
Level - 2 diagram:
In this level you go one step deeper into parts of level 1 DFD or simply
break processes down into more detailed sub-processes. You will reach in
depth of system functioning. It can be used to plan or record the specific or
necessary detail about the system’s functioning. In theory, DFDs could go
beyond level 3, but they rarely do.

Rules for Data Flow Diagram

 Data can not flow between two entities. –
Data flow must be from entity to a process or a process to an entity.
There can be multiple data flows between one entity and a process.

 Data can not flow between two data stores

Data flow must be from data store to a process or a process to an data
store. Data flow can occur from one data store to many process.

 Data can not flow directly from an entity to data store –

Data Flow from entity must be processed by a process before going to
data store and vice versa.

 A process must have atleast one input data flow and one output
data flow –
Every process must have input data flow to process the data and an
output data flow for the processed data.

 A data store must have atleast one input data flow and one output
data flow –
Every data store must have input data flow to store the data and an
output data flow for the retrieved data.

 Two data flows can not cross each other.

 All the process in the system must be linked to minimum one data
store or any other process.
ENTITY DIGRAM (E-R)

ER diagram stands for Entity Relationship Diagram, also known as ERD is a

diagram that displays the relationship of entity sets stored in a database. In
other words, ER diagrams help to explain the logical structure of databases.
ER diagrams are created based on three basic concepts: entities, attributes
and relationships.ER Diagrams contain different symbols that use
rectangles to represent entities, ovals to define attributes and diamond
shapes to represent relationships. At first look, an ER diagram looks very
similar to the flowchart. However, ER Diagram includes many specialized
symbols, and its meanings make this model unique. The purpose of ER
Diagram is to represent the entity framework infrastructure.

Fig. Component of ER Diagram

USE CASE DIAGRAM
A use case diagram is a graphical depiction of a user's possible interactions
with a system. A use case diagram shows various use cases and different
types of users the system has and will often be accompanied by other types
of diagrams as well. The use cases are represented by either circles or
ellipses. The actors are often shown as stick figures.

Components of use case diagram includes:

Actors: The users that interact with a system. An actor can be a person, an
organization, or an outside system that interacts with your application or
system. They must be external objects that produce or consume data.

System: A specific sequence of actions and interactions between actors

and the system. A system may also be referred to as a scenario.

Goals: The end result of most use cases. A successful diagram should
describe the activities and variants used to reach the goal
Fig: Use case diagram of Library Management System
SEQUENCE DIAGRAM
A sequence diagram simply depicts interaction between objects in a
sequential order i.e the order in which these interactions take place. we can
also use the term event diagrams or event scenarios to refer to a sequence
diagram. sequence diagram describe how and in what order the object in a
system function .these diagram are widely used by businessman and
software developers to document and understand requirements for new or
existing system. It shows interaction of object arranged in time sequence.
Sequence diagrams are typically associated with use case realizations in the
logical view of the system under development.

Fig: Sequence diagram of Library Management System

Gantt Chart

A Gantt chart is a type of bar chart that illustrates a project schedule. This

chart lists the tasks to be performed on the vertical axis, and time intervals
on the horizontal axis. The width of the horizontal bars in the graph shows
the duration of each activity. Gantt charts illustrate the start and finish
dates of the terminal elements and summary elements of a project.
Terminal elements and summary elements constitute the work breakdown
structure of the project. Modern Gantt charts also show the
dependency (i.e., precedence network) relationships between activities.
Gantt charts can be used to show current schedule status using percent-
complete shadings and a vertical "TODAY" line.
Gantt charts are sometimes equated with bar charts. Gantt charts are
usually created initially using an early start time approach, where each task
is scheduled to start immediately when its prerequisites are complete. This
method maximizes the float time available for all tasks.

S.N. Tasks Duration 1 2 3 4 5 6 7 8

1. Idea Presentation 1 week

2. Background Study 2 week

3. Requirement gathering 1 week

4. System Design 2 week

5. Feasibility study 2 week

6. Testing & Debugging 2 week

7. Documentation 8 week

Tasks Completed

Fig . Gantt chart

CONCLUSION
In this case study we analyzed the library management by the help of
different tools and techniques likes ER diagram, DFD models, Waterfalls
models etc. With the helps of tools and techniques we show that the library
system is connected or interact with different attributes and entity within
the library. We also meet the goals and the objectives of this case study, to
maintained the library, link with different attributes , incoming and
outgoings of the books . This case study helps to design the model of library
and also helps to develops different system and applications to managed
and analyzed the library works.

Hence from this case study we can managed the library system and makes
them user friendly. We also meet the aims and objectives of this case study.
So in this way we complete the case study base on the library management
system.

REFERENCES

https://whatis.techtarget.com/definition/use-case-diagram
https://www.geeksforgeeks.org/
http://107.170.122.150:8080/xmlui/bitstream/handle/123456789/58/p
rint%202%20%281%29.pdf?sequence=2&isAllowed=y