GEETANJALI INSTITUTE OF TECHNICAL STUDIES

UDAIPUR

An

Internship Report

Submitted in partial fulfillment

for the award of the degree of

[Link].

in department of Computer science and Engineering

Submitted to: MONICA BHATT

Roll No. 22EGICS047

Submitted By: HEMENDRA SINGH PARIHAR

Internship carried out

At

Department of Computer Science and Engineering

Geetanjali Institute of Technical Studies, Udaipur

Rajasthan Technical University

July,2020
1
 CERTIFICATE

This is to certified that the project entitled “LIBRARY MANAGEMENT SYSTEM” has been submitted to the
Rajasthan Technical University, Kota fulfillment of the requirement for the award of the degree of Bachelor of
Technology in “Computer Science And Engineering” by following student of Second year [Link]. (Computer
Science And Engineering).

Hemendra singh parihar

22EGICS047

Guide Dr .Mayank Patel

Monica Bhatt (HOD.,CSE)

2
 VISION OF DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

To nurture the students to become employable graduates who can provide solutions to
the societal issues through ICT.

MISSION OF DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

M1: To focus on practical approach towards learning and exposing the students on the
latest ICT technologies.

M2: To foster logical thinking among the students to solve real-time problems using
innovative approaches.

M3:To provide state-of-the-art resources that contributes to inculcate ethical & life-
long learning environment.

3
 CANDIDATE’S DECLARATION

I hereby declare that the work, which is being presented in the Internship Report,
entitled “Library Management System” in partial fulfillment for the award of Degree
of “Bachelor of Technology” in Dept. of Computer Science & Engineering, and
submitted to the Department of Computer Science & Engineering, Geetanjali Institute
of Technical Studies, Rajasthan Technical University is a record of my own
investigations carried at Geetanjali Institute Of Technical Studies,Udaipur.

I have not submitted the matter presented in this Project Report any where for the award
of any other Degree.

Ankit Mod

Harshit Suthar

Hemendra singh Parihar

Abhay Soni

Roll No. 22EGICS047

GEETANJALI INSTITUTE OF TECHNICAL STUDIES

4
 ABSTRACT

The Library Management System (LMS) is a modern solution designed to streamline

library operations. It features an intuitive interface for users, facilitates online accessibility,
automates check-in/out processes, prioritizes security with advanced measures, ensures
user privacy, and provides valuable analytics for optimized resource utilization. This
system aims to elevate the library experience by combining efficiency, accessibility, and
security in a user-friendly interface.

5
 TABLE OF CONTENTS

Chapter Conten Page

t No.
Chapter 1 Certificate 2

Chapter 2 Candidate Declaration 4

Chapter 3 Abstract 5
Chapter 4 Introduction to Project (Project Description) 7
Chapter 5 PLAN Layout 9
Chapter 6 Feasibility Study 10
Chapter 7 SRS –Software Requirement Specification 11
Chapter8 ER Diagram 15
Chapter 9 DFD-Data Flow Diagrams 17
Chapter 10 Class And Object Diagram 18
Chapter 11 UMLDiagram 19
Chapter 12 Conclusion 20

4
 CHAPTER 1: INTRODUCTION TO PROJECT

The proposed project Library Management System deals with the aspect of providing
readers the books of various subjects and fields. This library system provide extra
characteristic of book sorting which enhances the importance of this website by using
this option a student can sort according to his requirements.

Problem Statement:

• Existing systems rely heavily on manual record-keeping processes, leading to

inaccuracies in cataloging, tracking, and managing library resources.

• Tracing a book is difficult.

• There is no proper regulation of fines and dues.

• Fast access is not possible as it is time consuming.

Existing Solution:

A Library Management System (LMS) is a software solution that automates library

processes, including catalog management, user tracking, check-in/out automation, and online
accessibility. It enhances security, provides resource utilization analytics, and offers
reporting for efficient library operations and improved user experience.

Proposed solution:
• User-Friendly Interface: Intuitive interfaces for both staff and patrons, ensuring ease
of use and accessibility.

• Online Accessibility: Enabling users to search, reserve, and renew materials

remotely, promoting a modern and convenient user experience.

• Automation of Check-out and Check-in Processes: Minimizing manual errors,

reducing waiting times, and optimizing resource utilization.

• User Management and Privacy: Securely managing user information, memberships,

and borrowing history, addressing privacy concerns.

7
• Advanced Security Measures: Implementing RFID technology, security alarms, and
user authentication to protect library assets.

• Resource Utilization Analytics: Providing insights into resource usage patterns for
informed decision-making and collection optimization
.
• Reporting and Analysis Tools: Generating comprehensive reports on library
activities, user trends, and inventory status to aid strategic planning.

8
CHAPTER 2: PLAN LAYOUT

9
 CHAPTER 3: FEASIBILITY STUDY

▪ A feasibility study is an important stage in the development of business-related

services. The need for evaluation is great especially in large high-risk
information service development projects. A feasibility study focuses on the
study of the challenges, technical problems and way-out models of information
service awareness, analyses the potential solutions to the problems against the
requirements, evaluates their ability to meet the goals and describes and
rationalizes the recommended solution.
▪ The Feasible study can be divided into following:
1. ECONOMIC FEASIBILITY: This involves the question the new system that
is built, what will be the cost and will be beneficial also. We are eliminating paper
work and creating a web based system which will be cost effective and also
defining project in an environment with an effective supervision.

2. TECHNICAL FEASIBILITY: It defines technology required for system and

whether person using this has enough experience to use the technology. Our
project is implementing web application which requires knowledge about web
development.

3. SCHEDULE FEASIBILITY: It defines time required to build the system and

most important is it should be developed as soon as possible.

The system is time effective as we will be completing it within given time

constraint.

4. MARKET COMPETITORS: It defines the initial market and latest

technologies that are being used by competitors.

At initial level, the competitors are our college mates. But in near future we would
definitely be competing with others in the market.

5. ORGANISATIONAL FEASIBILITY: It involves the question like whether

the system has enough support to be implemented successfully or is it changing
to rapidly to absorb it.
We are providing a user friendly environment to our clients so that in future if
there any updations or improvements to be made can be easily implemented and
reflected
10
 CHAPTER 4: SOFTWARE REQUIREMENT
SPECIFICATION

The software requirements specification is produced at the culmination of the analysis task. The
function and performance allocated to software as part of system engineering are refined by
establishing a complete information description a detailed functional and behavioral description, a
indications of performance requirements and design constraints, appropriate validation criteria and
other data pertinent to requirements.

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Definition, Acronyms, Abbreviations

1.4 Overview

2. Overall Description

2.1 Product perspective

2.2 Product features

2.3 User characteristics

2.4 Operating environment

2.5 Assumption and Dependencies

11
1. INTRODUCTION

The project library management system deals with the aspect of providing books & its
details to readers of various subjects. It helps to enhance the manual library system by
creation of website. The website would update the readers with the details of books such
as availability ,max. limit of borrowing , due charges , etc.

1.1 Purpose

The main purpose of our project is to provide a friendly environment to the readers and
maintain easy circulation system using website.

1.2 Scope

Our project is especially designed for use for any education institute in order to provide
details of books. We can add new features as when we require which enhance the
flexibility of system.

1.3 Abbreviation

HTML : Hyper Text Markup Language

SQL : Structured Query Language

1.4 Overview

Library Management System basically deals with the enhancement of manual library
management system with the implementation of web applications.

The project mainly deals with the details of books, student account, librarian account
etc.

12
2. OVERALL DISCRIPTION

2.1 Product perspective

The projects gives the procedural approach of how the readers obtains the details of
the books ,its availability ,date of issuing ,date of returning ,fine details,etc.

2.2 Product features

The data represented in library management system application will perform

following major functions:

• Librarian details

• Student details

• Book details

• Reports

• Billing details

2.3 User characteristics

• The software is developed such that it will provide a friendly user interface.

• The operator will be provided with login id and password general users with basic
computer skills can use this software.

2.4 Operating environment

• We will use software that will support all known operating system such as
windows ,Linux,Mac,Android,ios etc. we will use computer with intel care is
processor,8GB RAM/512GB SSD/windows 10

2.5 Assumptions and Dependencies: 2.5 Assumptions and Dependencies The assumptions
are:- The coding should be error free  The system should be user-friendly so that it is
easy to use for the users
2.6  The information of all users, books and libraries must be stored in a database that is
accessible by the website  The system should have more storage capacity and provide
fast access to the database
2.7  The system should provide search facility and support quick transactions
2.8  The Library System is running 24 hours a day
3. Users may access from any computer that has Internet browsing capabilities and an,
13
 Engineering, Media Studies & Research Department of Information Technology Internet

connection 

4. Users must have their correct usernames and passwords to enter into their online accounts

and do actions The dependencies are:-  The specific hardware and software due to which

the product will be run  On the basis of listing requirements and specification the project

will be developed and run  The end users (admin) should have proper understanding of

the product  The system should have the general report stored  The information of all

the users must be stored in a database that is accessible by the Library System  Any

update regarding the book from the library is to be recorded to the database and the data

entered should be correct.

14
 **Risk Management and Monitoring Plan for Library
Management System (LMS)**

1. Risk Identification:

a. Technical Challenges:
- Risk: Unforeseen technical issues during system development.
- Mitigation: Regular code reviews, extensive testing, and a contingency plan for
technical glitches.

b. User Resistance:
- Risk: Resistance from library staff and users to adapt to the new system.
- Mitigation: Comprehensive training programs, user feedback channels, and change
management strategies.

c. Data Security Breach:

- Risk: Potential unauthorized access leading to a data breach.
- Mitigation: Implement robust security protocols, encryption, and regular security
audits.

d. Integration Issues:
- Risk: Challenges integrating the LMS with existing library infrastructure or third-party
systems.
- Mitigation: Thorough compatibility assessments, pilot testing, and collaboration with
IT experts.

2. Risk Assessment:

a. Impact and Probability Assessment:

- Assess the potential impact and likelihood of each identified risk.
- Prioritize risks based on severity and probability.

b. Risk Tolerance Levels:

- Define acceptable levels of risk for different aspects of the LMS implementation.
- Establish thresholds for when risk responses need to be activated.

3. Risk Response:

a. Contingency Plans:
- Develop contingency plans for identified high-impact risks.
- Define roles and responsibilities for implementing contingency measures.
b. Communication Strategy:

15
 - Establish a clear communication plan for informing stakeholders about identified risks
and mitigation efforts.

4. Risk Monitoring:

a. Regular Assessments:
- Conduct regular risk assessments throughout the development and implementation
phases.
- Update risk assessments based on changes in project scope or external factors.

b. Key Performance Indicators (KPIs):

- Define KPIs to monitor the effectiveness of risk mitigation strategies.
- Use KPIs to trigger adjustments in risk management approaches if necessary.

5. Documentation and Reporting:

a. Risk Register:
- Maintain a comprehensive risk register detailing identified risks, mitigation strategies,
and current status.
- Regularly update the risk register and share with relevant stakeholders.

b. Reporting Mechanism:
- Establish a reporting mechanism for team members to report potential risks promptly.
- Hold regular risk review meetings to discuss any emerging concerns.

By implementing this Risk Management and Monitoring Plan, the Library Management
System project aims to proactively identify, assess, and mitigate potential risks, ensuring a
smooth development and implementation process while maintaining the security and
functionality of the system.

16
 CHAPTER 6: ER DIAGRAM

Data Modeling: Data modeling defines the primary data objects, their attributes and
their relationships other primary data objects. It also defines relationships between
objects and the processes transform them. In order to define the objects and their
relationship, it make use of entity relationship diagrams (ERD). ERD helps in
defining as well as identifying them and relationship using graphical notations. ERD
defines all the data that are stored, entered, transformed and produced within an
application.
Entity – Relationship Diagram: Entity – Relationship Diagram represents the
Object Relationship pairs in graphical forms. Thus, we can say that the primary goal
of ER diagrams is to represent Data objects along with their relationships

The ER Diagram represents objects relationship pair. The various

components are:
SYMBOL NAME

Strong Entity

Weak entity

Relationship

Attributes

Derived Attribute

A Primary Key

17
E R Total Participation

Multivalued Attribute

Modality

Weak Relation

Total Generalization
IS A

1
M
Relation
M M

18
19
 CHAPTER 7: DFD DIAGRAM

A Data Flow Diagram is a graphical representation that depicts the

information flow and the transforms that are applied as data moves
from input to output. It can be used to represent a software at any
level of abstraction. It fact, DFD’s may be partitioned into levels
that represent increasing information flow and functional detail.
Therefore, it provides mechanism for functional modeling as well
as information flow modeling.

Symbols used in DFD :

1. Bubble : A circle or bubble is used to depict a process. Both input and output to
a process are dataflows.
2. Arrows : Data flows are represented by a line with arrow. 3. Ward and mellor
Extension : Conventional DFD notation does not make any distinction between
discrete data and time continuous data. Ward and mellor used single head arrow to
represent discrete data and double headed arrow to use time continuous data.
4. Rectangle : Rectangle are used to represent the entities and are outside the
system. Designers do not have any control over them. They either supply or receives
data. In Fig.4, two entities supplies and receives are shown as rectangles. So, supplier
entity A supplies some stock delivered to the receiver entity B. Even a single entity
can both supply and receive data. 5. Parallel Lines : Parallel lines are used to
depict data stores. Process may store or receive data from data
stores. Data cannot flow between two data stores. An arrow
towards data store indicates writing data to data store and an
arrow from data stores depicts retrieval of data from it.

0 LEVEL DFD DIAGRAM

20
1 LEVEL DFD DIAGRAM

21
 CHAPTER 8

Object Qriented Design :- Object oriented design works around the entities
and their characteristics instead of functions involved un the software system.
This design strategies focuses on entities and its characteristics. The whole
concept of software solution revolves around see the engaged entities.

Here we see the important concepts Object Oriented Design:

1) Objects :- All entities involved in the solution design objects for are known as

ex. person, banks, company and customers are treated as objects. Every entity
attribute associated to it and has some methods to perform on the attributes.

2) Classes :- A class is a generalized description of an object is an instance of a

class defines all the attributes which an object can have and methods, which de-
fines the functionality of the object. In the solution design, attributes are stored
variables and functionalities defined by means of methods or procedures.

3) Encapsulation :- In OOD , the attributes (date variables) and methods (opera-

tion on the data) are bundled together is called encapsulation. It is not only bun-
dles important information of object an together, but also restricts access of the
data & methods from the outside world. This is called information hiding

4) Inheritance :- OOD allows similar classes to stack uр in hiearchical manner

where the lower or sub classes can import, implement and re-use allowed varia-
bles and methods from their immediate super classes. This property of OOD is
known as inheritance.

5) Polymorphism - OOD languages provide tasks but a mechanism where meth-

ods performing similar Takes but vary in arguments, can be assigned same name
. this is called polymorphism, which allows a single interface performing tasks
for different types.
Introduction to OOAD :-

22
● Analysis :- Analysis is a creative activity an investigation of the problem and re-
quirements.

Ex. To develop is Banking system.

Analysis - How the system will be used?

Who are the users ? What are its functionalities?

● Design :- Design is to provide conceptual solution that satisfies the requirements a given.
problem

Ex . for Book Bank System

Design:- Bank (Bank name, Address , No of members )

Student (Membership No, Name, Book Name, Amount

Paid)

● Object Oriented Analysis (OOA) :- Object oriented analysis is a process of identifying

classes that plays important rate in achieving system goals and requirements. Ex . for Book
Bank system, classes or a objects identified are Book – details , Student - details, Member-
ship - Details.
● Object Oriented Design (000) :- is to design the classes identified during analysis phase
and to provide the relationship that exists between them that satisfies the requirements. Ex
- Book Bank System

class name Book - Bank (Back Name, No-of Members,

Address) Student (Name, Membership No, Amount Paid)

● Object Oriented Analysis And Design (OOAD) :- OOAD is a Software Engineering

approach that models an applications by a set of Software Development Activities. OOAD
emphasis on identifying, describing and defining the software objects and shows how they
collaborate with one another to fulfill the requirements by applying the object oriented par-
adigm and visual modeling throughout the development life cycles.

23
 CHAPTER 10
UML DIAGRAM
CLASS DIAGRAM

OBJECT DIAGRAM

24
UML DIAGRAM

25
26
 SEQUENCE DIAGRAM
Sequence diagram describes an interaction by focusing on the sequence of messages
that are exchanged, along with their corresponding occurrence specifications on the
lifelines.

27
 USE CASE DIAGRAM

Use case diagrams are used to describe a set of actions (use cases) that some system
or systems should or can perform in collaboration with one or more external users
of the system (actors). Each use case should provide some observable and valuable
result to the actors or other stakeholders of the system.

28
ACTIVITY DIAGRAM

29
 COLLABORATION DIAGRAM

Collaboration or Communication diagram is also used to model the

dynamic behaviour of the system. It emphasizes on structural organization
of the objects that send and receive messages.

Book

Librarian Member
Record

Account
Record

Fines/Dues
Record

30
 COMPONENT DIAGRAM

Component diagram are used to model physical aspects of a system (element like
executables, files etc.) . Component diagrams are used to visualize the organization
and relationship among the components in a system.

31
 DEPLOYEMENT DIAGRAM

● Deployment diagram is defined as assignment of concrete software artifacts

(executable files) to computational nodes (processing services).
● Deployment of software elements to the physical architecture and the communication
(network) between physical elements.

32
 CHAPTER 11: CONCLUSION

The project Library Management System is for digitalizing the manual work in
library. The proposed software takes care of all the requirements of a library is
capable to provide easy and effective storage of information related to books
and users.

It makes entire process online where student can search books, staff can
generate reports and do payment transactions. It also has a facility for student
login where student can login and can see status of books issued as well request
for book or give some suggestions. It has a facility of librarian and staff login
where they can access the student and book info and also update them.

33
 CHAPTER 12: FUTURE SCOPE

Library management system is used to operate and manage the huge amount of
data generated from libraries. It is also used to track bills, books, and customers
who have borrowed books from the library. It includes some operations such as
filtering the data, sorting, finding information across the huge data field and
editing of data.

The project is especially designed for institutes in order to upgrade the manual

work of library. It can be used in other organizations by modifying and updating

as per requirements of clients. This shows the flexibility of system.

The global library management system market is mainly driven by rise in need
for automation of library management functions to manage informational
resources. Increasing demand for automatic database management systems in
libraries, mainly in public libraries is another driving factor which is anticipated
to boost the growth of the library management system market.

34