LIBRARY MANAGEMENT SYSTEM

A minor project report submitted in partial fulfillment

of the requirements for the award of Degree in
Master of Computer Applications (MCA)
By

Department of Computer Science

GITAM Institute of Science
GITAM University
Visakhapatnam-530 045, A.P.
(2015)

C E R T I F I C AT E

This is to certify that the minor Project entitled LIBRARY MANAGEMENT

SYSTEM is a bonafide work done by Mr. Y. S. N. SATYANARAYANA, Reg.No:1223714116
December 2014 to April 2015, in partial fulfillment of the requirements for the award of degree
of Master of Computer Applications (MCA) in the Department of Computer Science, GITAM
Institute of Science, GITAM University.

Internal Guide

Head of the Department

DECLARATION

I, Y. S. N. SATYANARAYANA, Reg. No. 1223714116 hereby declare that the

project entitled LIBRARY MANAGEMENT SYSTEM is an original work done in the
partial fulfillment of the requirements for the award of degree of Mater of Computer
Applications (MCA) in GITAM Institute of Science, GITAM University.
I assure that this project work has not been submitted towards any other degree or
diploma in any other colleges or universities.

Y. S. N. SATYANARAYANA
1223714116

ACKNOWLEDGEMENT

I am very grateful to my project guide Mr. B. SRINIVASA RAO, Assistant

professor for giving his valuable time and constructive guidance in preparing the Project.
It would not have been possible to complete this project in short period of time without his kind
encouragement and valuable guidance.
I am very thankful to all, who have provided me their guidance and encouragement. This
includes the respected HOD, Dr. V. Naga Lakshmi, Principal, Prof. Lakshmana Das, and all
the teachers, without the help of whom I would have probably not been able to complete the task.

Y. S. N. SATYANARAYANA
Regd No. 1223714116

ABSTRACT
LIBRARY SYSTEM is a computerized system to maintain and controlling the
transactions in a library.
A Library Management System provides facilities like register, login, issuing and return books.
In current system it is very easy for searching the books related to the particular area. If faculty
mentioned any area of a book then it will automatically displays the details of related books that
are available in library. This system can be used to search for books, find out who is having a
particular book. The current system the Administrator can have all the rights adding and updating
the new books in the library. This projects main motto is to reduce the effort of Librarian and provide
better service to students and faculty.

Table of Contents
S.No.

Content Description

1.

Introduction
1.1
About the Project

2.

Requirements Analysis Document

2.1
Introduction
2.2
Existing System
2.3
2.4
2.5
2.6

3.

Page No.

Proposed System
Feasibility Analysis
Functional Requirements
Non Functional Requirements

System Design
3.1
Introduction
3.2
System Model
3.3
Tables
3.4
Normalization
3.5
ER Diagrams
3.6
Data Flow Diagrams

4.

About the Software ( if any )

5.

Testing And Implementation ( if any )

6.

Sample Code ( if any )

7.

Screens Shots ( if any )

8.

Conclusion

9.

Bibliography

INTRODUCTION
1.1

Overview of Project:

This Project Library Management targeted for the Library integrates the transaction
management and inventory management of the Library for better control and timely response.
This eliminates time delay and paper transactions being marked. The librarian is provided with a
better control over the transactions like Issuing and Returning of Books etc. and inventory
management like adding, updating and deleting Books in the Library, Calculating Penalty. This
projects main motto is to reduce the effort of Librarian and provide better service to students and
faculty.
The project is divided into five modules. They are

Students Module deals with student information in Library.

Faculty Module deals with faculty information in Library.

Administrator Module deals with privileges provided for Librarian.

Search Module deals with searching of information in the Library.

Reports Module deals with generating general & customized reports.

Requirements Analysis

2.1

Introduction:
The goal of this project is to develop a system for the computerization of the

Library. The common transactions of the library like issuing of Books, returning the same by
Students and Faculty and Inventory of Library like Books Stock etc. are stored into the databases
and reports are generated according to the user requirements.

2.2

Existing System:
The existing system of The College Library is run manually by entering data in
books and keeping track of all the data in the books.

The different processes involved are:

To maintain book issued details of Students and Faculty manually.
To maintain book return details.
To maintain details of the current books stock.
Calculating Penalty for Books.
To maintain the inventory details

2.3

Proposed System:
The proposed system tries to solve the problems mentioned above. The main objective of

the proposed system is to provide information instantly as and when it is required. The main
objective is to make the Library information details more efficient. This system should maintain
9

different data files, so that the data can be retrieved easily and in an efficient manner. The system
is very interactive. It should ensure process integration to the desired extent, various reports
should be generated as the need be. This system should also ensure that there is no redundancy in
the recorded data.

a) Advantages of proposed system:

1. Issue and returns of books etc. can be done quickly and efficiently, so that it provides
better services to users.
2. The proposed system provides efficient management of inventory in the library.
3. Redundancy is reduced; loss of data due to physical damages can be overcome by
taking the backup and recovery from the proposed system.
4. Because of computerization manual work is eliminated and manual errors can be
overcome easily.

2.4

Feasibility Analysis:
All projects are feasible given unlimited resources and infinite time

unfortunately, the development of computer-based system or product is more likely plagued by a

scarcity of resources and difficult delivery dates. It is both necessary and prudent to evaluate the
10

feasibility of a project at the earliest possible time. Months or years of effort, thousands or
millions of dollars, and untold professional embarrassment can be averted if an ill-conceived
system is recognized early in the definition phase.
Generally the feasibility study is used for determining the resource requirement cost,
benefits and whether the proposed system is feasible with respect to the organization.

2.5

Functional & Non Functional Requirements:

System analysis is an important activity that takes place when we are building a

new information system or changing existing ones. Analysis is used to gain an understanding
of an existing system and what is required of it. At the conclusion of analysis, there is system
description and a set of requirements for a new system. If there is no existing system, the
analysis defines only the requirements.
System models are used to gain precision and to avoid the ambiguities often found in
the natural language system descriptions. Modeling techniques used in system analysis avoids
ambiguity by using precise modeling constructors and process descriptions. They also assist
analysts to define precisely the requirements of the new system. Software tools that help
analyst in their work now often support system analysis. These tools are the models developed
during analysis and some convert these models to trail designs.
This phase is detailed appraisal of the existing system. The appraisal includes finding
how the system works and what it does. It also includes systems problems and what the endusers require for any new or changed system. After this phase, analyst should be familiar with
both the detailed operation of the system and what is required of the new system.
Analysts must spend considerable time in examining components of existing system.
Analysts have to find out what information is send between the end-users and the staff.
One of the most important factors in system analysis is to understand the system and its
problems. A good understanding of the system enables designers to identify and correct
problems and suggest realistic solutions for them. It also helps them to develop solutions that

11

satisfy all users and thus make the new system acceptable in an organization. System users are
the first information source investigated by the analysts.
From users it is to find out the existing system activities and to develop the users
objectives and requirements. A system analyst must spend a lot of time talking to users and
finding how they use the system, any problems they find with the system and what they expect
from it.
Thus a rule, system analysis is a difficult but rewarding job. There are many constraints
to be compiled within this work and many people to satisfy. But there is the reward of seeing of
a new system does its job perfectly.

12

System Design
3.1

Introduction:
Design is the first step in the development phase for any engineering product (or)

system. It may be defined as The process of applying various techniques and principles for the
purpose of defining a device, a process, or a system insufficient detail to permit its physical
realization.
Software design is an iterative process through which requirements are translated into a
Blue print for constructing the software. The design is represented at a high level of abstraction,
a level that can be directly translated to specific data, functional and behavioral requirements.
Preliminary design is concerned with the transformation of requirements into a data and
software architecture. Detail design focuses on refinements to the architectural representation.
That leads to detailed data structure and algorithmic representation for software.
In the design step, the element of the analysis model gets converted in to a data design, an
architectural design, an interface design and a procedural design.
The data design transforms the information domain model created during analysis into
the data structures that will be required to implement software.
The architectural design defines the relationship among major structural elements of the
program.

3.2

System Model:

Design process is in between the analysis and implementation process. The following
design diagrams (data flow diagrams and E-R diagrams) make it easy to understand and
implement.
13

The design process of software system has two levels.

1. Systems Design or Top Level Design.
2. Detailed Design or Logical Design.
System Design or Top Level Design:
In the system design the focus is on deciding which modules are needed for the
system, the specification of these modules and how these modules should be
interconnected.
Detailed Design or Logical Design:
In detailed design the interconnection of the modules or how the
specifications of the modules can be satisfied is decided . Some properties for a software
system design are

Verifiability.
Completeness.
Consistency.
Traceability.
Simplicity/understandability.

Tables
Membership:
14

S. No.

Column Name

Data Type

Length

Description

1.

Id_no

Number

50

2.

Name

Varchar

30

3.

Address

Varchar

100

4.

Date of Issue

Date

5.

Date of Expiry

Date

6.

Status

Varchar

30

Unique
identification of
the member.
Name of
Members.
Location of
Members.
Date of
Registration.
Registration
expiry date.
Permanent/
Temporary.

Add Books:
S. No.

Column Name

Data Type

Description

1
2

Book Name
Book code

Varchar2(30)
Varchar2(20)

3
4

Author
Date of arrival

Varchar2(30)
Date

5
6
7
8

Price
Rack No
Number of books
Subject code

Number
Varchar2(30)
Number(30)
Varchar2(20)

Title of the book

Book identification
number
Author of book
Date on which book
was received
Cost of the book
Almirah No
Quantity of books
Unique identification
number of particular
subjects

15

Issue of Books:
S. No.

Column Name

Data Type

Id no

Number

2
3

Book name
Issue date

Varchar2(30)
Date

Date expiry

Date

Book code

Varchar2(30)

S. No.

Column Name

Data Type

Id no

Number

2
3

Book name
Issue date

Varchar2(30)
Date

Date expiry

Date

Book code

Varchar2(30)

Description
User identification
number
Title of books
Date on which book
is issued
Due date on which
book is to be
returned
Book identification
number

Return of Books:

3.4

Normalization:
16

Description
User identification
number
Title of books
Date on which book
is issued
Due date on which
book is to be
returned
Book identification
number

Normalization of relation schema is done to eliminate insertion and deletion anomalies

that exist in databases.
Normalization is a step-by-step reversible process of converting given collection of
relations to some more desirable form in which the relations have a progressively simpler and
more regular structure. No information is lost in normalization process.
The objectives of Normalization are

To make it feasible to represent any relation in the database.

To obtain powerful retrieval algorithms based on a simpler collection of relational

operations than would otherwise be necessary.

To free relations from undesirable insertions, update and deletion dependencies. To

make the collection of relations neutral to query statistics where these statistics are
liable to change as time goes by.

A relation R is said to be in 1NF if all underlying domains contain atomic values only.
A relation R is said to be in 2NF if and only if it is in 1NF and every non-key attribute is
non-transitively dependent on the primary key.
A relationship is said to be in 3NF if and only if it does not feature any non-trivial
functional dependencies between non-prime attributes. A non-prime attribute is one that does not
belong to any candidate key.

E-R DIAGRAM:
17

LIBRARY

CONTAINS

Book Name
No of books

Book code

Rack No

Author

Subject code

BOOKS

Price

ISSUE
Status
Date of Issue

ID

Date of expiry

Name

Subject code

MEMBERS

Type

Address

RETURN

ISSUE

ID
ID

Book code

Book code

STATUS OF
RETURN

STATUS OF ISSUE

Book Name

Book Name
Date of Issue
Date of Expiry

Date of Issue

4.4 Data Flow Diagram (DFD):

Date of Expiry
18

The data flow diagram (DFD) is one the most important modeling tools. It is used to
model the system components. These components are the system process, the data used by the
process, an external entity that interacts with the system and the information flows in the system.
DFD shows how the information moves through the system and how it is modified by a
series of transformations. It is a graphical technique that depicts information flow and those
transformations that are applied as data moves from input to output.
DFD is also known as bubble chart. A DFD may be used to represent a system at any
level of abstraction. DFD s may be partitioned into levels that represent increasing information
flow and functional details.
A level 0 DFD, also called as the context diagram, represents the entire system as a
single module with input and output data indicated by incoming and outgoing arrows
respectively. Additional process and information flow paths are represented, as the level 0 DFD
is partitioned to reveal more details.
A level 1 DFD, also called as top-level DFD, represent the system with major modules
and data stores. The other levels will show each module in the top-level DFD in a more detailed
fashion.
Notation:
Data Flow: Data move in a specific direction from an origin to a destination . The data flow is
a packet of data.

Process: People, procedures or devices that produce data. The physical component is not
identified.

Source or Destination of data: External sources or destinations of data, which may be

people or organizations or other entities.
19

Data Store: Here, the data referred by a process in the system.

3.6

Data Flow Diagram:

DFD Level-0

Input

USER

Library
Management

20

Output

USER

DFD Level-1

21

DFD Level-2
Facuty

Student

Books

Student
Details

Books

Total & Issued Books

ISSUE

Generate Reports
User

Books

Return

Facult
Fa
Faculty

Details

User

22

Software Implementation
Introduction:
Implementation is the process of assuring that the information system is operational and
then allowing users take over its operation for use and evaluation. Implementation includes the
following activities:
Obtaining and installing the system hardware.
Installing the system and making it run on its intended hardware.
Providing user access to the system.
Creating and updating the database.
Training the users on the new system.
Documenting the system for its users and for those who will be responsible for
maintaining it in the future.
Making arrangements to support the users as the system is used.
Transferring ongoing responsibility for the system from its developers to the
operations or maintenance part.
Evaluating the operation and use of the system.
The most visible component of implementation process is the system conversion. The
four basic conversion strategies include:
Direct Conversion
Parallel Conversion
Pilot Conversion
Phased Conversion

23

Software Requirements:
Operating Environment

: Windows200/Xp-SP2

RDBMS Package

: oracle 10g

Front End

: J2EE API, JSP, Servlets

Browser

: IE7

Server

: Tomcat5.1

Hardware Requirements:
CPU

: Pentium 4, 1.7 GHz

RAM

: 512 MB

Hard disk

: 80 GB

24

Screens Shots

25

26

27

Conclusion
At the time of the beginning of the development of this project we had kept certain goals
in the mind, and it is great pleasure that the system is meeting most of its requirements. In this
project report we have mentioned all the details of the system, which includes all the stages of
the system.
The goals that are expected to achieve by the software are:
Simplification of the operation.
Less processing time and increasing the productivity.
Each transaction is updated and processed immediately.
Avoiding the errors by minimizing human interaction through user friendly screens to enter
data and retrieve the information from tables on like messages.
Portable and flexible for further enhancement.
The system is also tested in Windows xp and found to be running smoothly. It is
recommended to run the system with Windows 2000 and later versions.

Scope for expansion:

The system is developed in a modular fashion with different function performing their
jobs. If any changes have to be done to the system then they can be easily achieved by making
the changes to the functions and they wont affect the remaining part of the system.

28

Dear Students,
The hard copy of the above pages, front-end and back end design, Entity
Diagram, and any further development in the project should be shown during review time.
You should bring the report in spiral binding for the second review.
THE HARD COPY OF THE PROJECT MUST BE SHOWN TO THEIR RESPECTIVE
GUIDES BEFORE COMING TO THE SECOND REVIEW.
The Students should follow these rules:
1. The sheets to be used are A4.
2. The normal text font style should be Times New Roman with font size 12.
3. The headings should be Times New Roman, with font size 14.
4. Line spacing:
a) Use 1.2 spacing between the lines.
b) Use 2 spaces between consecutive Paragraphs.
c) Use 1.5 spacing between the title of the section/sub-section and the text.
5. Margins: A margin of 3.75 cm (1 and half inches) to be given on the binding edge while
On the other sides it is 2.5cm (1 inch).
6. Page Numbering: Page numbers should be centered at the bottom of the pages.
7. Justification: Right and left margins should be justified.
(giving straight edge to the text on both sides).
8. Heading like Introduction, Requirements Analysis Documents, System Design, About the
Software, Testing and Implementation, Sample Code, Screen Shots. For Each Section heading a
separate page with no page numbers which should be there before the concept starts. This should
be the heading as shown above INTRODUCTION.

29