This document is a project report for a Library Management System developed by Karan Singhal. It includes an abstract, scope, system requirements, architecture, design, and planning. The system was developed using Java and MySQL to automate library processes like book/member management, transactions, and reporting. The future sections will cover implementation details and testing results.

1. Page : 1/41
LIBRARY MANAGEMENT SYSTEM
by
KARAN SINGHAL
Submitted to the department of
Computer Science and Engineering
In partial fulfilment of the requirements
For the degree of
Bachelor of Technology
in
Computer Science and Engineering
RAJ KUMAR GOEL INSTITUTE OF TECHNOLOGY
A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY
MARCH, 2016

2. Page : 2/41
Declaration
I declare that this project entitled “Library Management System”
done at Raj Kumar Goel Institute Of Technology,Ghaziabad is a
record of project work submitted by me for the partial fulfillment of
the Dr. A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY under
the supervision and guidance of Mr. Manish Gupta.
The Project is genuine and not a reproduction of any project
previously done or submitted.
- Karan Singhal
1203310087

3. Page : 3/41
Acknowledgement
I extend my sincere thanks to our faculties which provided me with
the opportunity to fulfill my wish and achieve my goal.
I would like to express deep debt to Mr. Manish Gupta, project
guide for his vital suggestions, meticulous guidance and constant
motivation which went a long way in the successful completion of
this project.
On a moral personal note, my deepest appreciation and gratitude to
my beloved parents, who have been an inspiration and have
provided me with unrelenting encouragement and support.
- Karan Singhal

4. Page : 4/41
CERTIFICATE
This is to certify that the Dissertation entitled, Library
Management is a bonafide work done by KaranSinghal,Chitransh
Ahuja,Shubham Rathi,Prashant Kumar of B-Tech (Computer Science
andEngineering) during the academic session 2015-2016 has been
carried out under my direct supervision and guidance. This report or
a similar report on the topic has not been submitted for any other
examination and does not form a part of any other course undergone
by the candidate.
________________
Signature of Faculty
(Mr. Manish Gupta)

5. Page : 5/41
Table of Contents
CHAPTER 1
1.1
ABSTARCT.....................................................................................................................................................7
Scope and Features..........................................................................................................8
Master and Security module........................................................................................8
Transaction module....................................................................................................10
Drawbacks of Present System .......................................................................................11
Proposed System ...........................................................................................................11
Out of Scope .................................................................................................................12
Goal and objective.........................................................................................................13
Solution Concept............................................................................................................13
PROBLEM STATEMENT..........................................................................................................................14
Requirements Summary.................................................................................................14
Business Requirements..............................................................................................14
User Requirements.....................................................................................................14
Operational Requirements.........................................................................................15
SYSTEM ARCHITECTURE .....................................................................................................................16
High Level Solution Architecture..................................................................................16
Data Flow and Process Flow Chart................................................................................17
User Profiles...................................................................................................................18
Usage Summary.............................................................................................................19
SOFTWARE AND HARDWARE REQUIREMENT...............................................................................20
General Requirement for Server/Client:.................................................................20
........................................................................................................................................................................20
DEVELOPMENT TOOLS AND TECHNOLOGIES...............................................................................21
Front End.......................................................................................................................21
Back End........................................................................................................................21
Development Environment...........................................................................................22
DESIGN GOALS AND CONSTRAINTS..................................................................................................23
LIBRARY MANAGEMENT SYSTEM DATA DICTIONARY..............................................................24
1. EmployeeMaster....................................................................................................24
2. MemberMaster.......................................................................................................25
3. AreaMaster.............................................................................................................26
4. Category.................................................................................................................26
5. BookMaster............................................................................................................26
6. LibaryCardMaster..................................................................................................28
7. PublisherMaster.....................................................................................................29
8. UserMaster.............................................................................................................29
9. Transcation.............................................................................................................30

6. Page : 6/41
LIBRARY MANAGEMENT SYSTEM– DATA SCHEMA ER DIAGRAM.........................................31
ELIBRARY ER DIAGRAM........................................................................................................................32
ELIBRARY DFD (DATA FLOW DIAGRAM).........................................................................................33
Context Level DFD........................................................................................................33
0 LEVEL DATA FLOW DIAGRAM.........................................................................................................33
PLANNING AND SCHEDULING.............................................................................................................35
Planning.........................................................................................................................35
Gantt chart:.....................................................................................................................36
PERT chart:....................................................................................................................38
CONCLUSION AND FUTURE ENHANCEMENT.................................................................................39
BIBLIOGRAPHY.........................................................................................................................................40
Websites.........................................................................................................................40
Books.............................................................................................................................40

7. Page : 7/41
ABSTARCT
Today most of the library is using either manual system for tracking
the day to day activity or they are using desktop, spread sheet like
MS Excel application to manage the day to day activity. In this
proposed Library Management System it will run in client server
mode and user can check the book availability, they can search the
books, library staff can issue, receive book, and management can
check the report. System will store historical data. Management can
anytime view the total book status, library card status.

8. Page : 8/41
Scope and Features
The Library Management System is designed & developed for a
receipt and issuance of books in the library along with the student’s
details. The books received in the library are entered in Books Entry
form and the new student is entered in the student entry form. When
the student wants to get the desired book the same is issued on the
availability basis to the student. The issuance and due date for the
returning of the book is also entered into the Book Issue form under
third menu Book Issue. The student has to pay the fine if any on the
basis of no. of days delayed deposit of the book in the library.
Any education institute can make use of it for providing information
about author, content of the available books. It can be used in offices
and modifications can be easily done according to requirements
From an end-user perspective, the Library Management System
Project consists of two functional elements: Master and Transaction
Module.
Master and Security module
Master and security module includes user security management,
login security, book details, member master, library card, library
transaction.

9. Page : 9/41
• Login – Check the user by user name and password, All user
needs to enter user name and password to access the system,
system check the user name and password and give access the
system resource only valid user.
• Main Screen – It display available options, menus and toolbars
to the logged user. System display option as per user rights. It
also show the name of user currently logged in.

10. Page : 10/41
Transaction module
Transaction module includes issuing, receiving book and transaction
report.
• Issuing Book – This form used to issue book to the member. In
this screen user selects book id, and library card id, system
display the book and card history. If book is already issued it
display message and details of last issued details. Same way
system display card history for the library card no, if book
already available it shows the message. If book is available and
there is no book pending for received then book is issued and
system saves the details. System also has powerful search
facility to find the book and member id.

11. Page : 11/41
Drawbacks of Present System
Some of the problems being faced in manual system are as
follows:
1. Fast report generation is not possible.
Proposed System
There will be three major components:
1. Stock maintenance.
2. Transaction entry.
3. Reports.
Proposed system provides with following solutions:
1. It provides "better and efficient" service to members.

12. Page : 12/41
Out of Scope
The following functions are considered out of scope for Version 1 of
the Library Management System. Versions 2.0 address items not in
scope and those are not feasible during V1.0.
Function
Comment Version
Linking and integration of
any legacy system for
accounting.
Required by
management to control
and maintain the
accounting activity
2

13. Page : 13/41
Goal and objective
This section presents a conceptual overview of the solution, and then
provides an introduction to its requirements.
Solution Concept
The Library Management System consists of:
• Master and Security Module:
Master and Security module includes user security
management, login security, book master, publisher master,
member master, library card, general settings.
• Transaction Module: Transaction module includes forms to
issue, receive books and display the library transaction details.

14. Page : 14/41
Problem Statement
Requirements Summary
The following preliminary lists are based on initial interviews
Business Requirements
The business goal for the application is to support an increase the
productivity and complete automation of existing manual or semi
automatic library management process. Business requirements are
discussed in the Scope section, with the following additional detail:
User Requirements
User requirements are categorized by user type.
System Users
• Able to search and view the member details.
• Able to find all the information like book details, book and
library card transaction details in one screen to give answer to
member query.
Supervisor
• Update book and member details.
• Modify library card details if required.

15. Page : 15/41
Operational Requirements
The following requirements provide a high-level view of how the
system will run:
• Processor usage should not exceed 80 percent during
concurrent uses.
• Backups will occur incrementally throughout the day.
• A full weekly backup is required to WORM drives.
• Ensure that information is easy to access either, and meaningful
for the system users and the company.
• Minimize the technical knowledge that systems users need to
access the

16. Page : 16/41
System Architecture
High Level Solution Architecture
High Level Solution Architecture of online Library Management
System

17. Page : 17/41
Data Flow and Process Flow Chart

18. Page : 18/41
User Profiles
The following user types are expected for the Library Management
System:

 
 
 
 

19. Page : 19/41
Usage Summary
Library Management System Version 1.0 will address the following
use cases. The complete usage scenarios will be completed during the
information-gathering process. Use cases will be created and
prioritized. Selected use cases will be expanded into usage scenarios
and features that are derived from both use cases and the usage
scenarios, as represented in the following diagram:
Usage summary use case

20. Page : 20/41
Software and Hardware Requirement
General Requirement for Server/Client:
Type Software Hardware
Work Station/
Node
1. Windows XP
2. JAVA
1. P-4
2. RAM -256 MB
Database Server MySQL 1.P-4
2.RAM- 2GB
3.Hard Disk-160GB
4.RAID
Application
Server
1.Win 2000 Advance
Server
1.P-4
2.RAM- 1GB
3.Hard Disk-40GB
Application ServerData Base Server
Workstation 1 Workstation 2 Workstation 3 Workstation N

21. Page : 21/41
Development Tools and Technologies
Front End
1. JAVA
Why Java?
Back End
• MySQL
Why MySQL?

22. Page : 22/41
Development Environment
1. NetBean
2. MySQL Query Browser

23. Page : 23/41
Design Goals and Constraints

24. Page : 24/41
Library Management System Data Dictionary
1. EmployeeMaster
Sr. Field Name Type Primary
Key
Foreign Key
1 E_Id Number Y
2 E_Sname Text(50)
3 E_Name Text(50)
4 E_Fname Text(50)
5 E_Religion Text(50)
6 E_Caste Text(50)
7 E_Nationality Text(50)

25. Page : 25/41
2. MemberMaster
Sr. Field Name Type Primary
Key
Foreign Key
1 HolderID Number Y
2 Dor Date/Time
3 Title Text

26. Page : 26/41
3. AreaMaster
Sr. Field Name Type Primary
Key
Foreign Key
1 Area Text Y
4. Category
Sr. Field Name Type Primary
Key
Foreign Key
1 Category Text Y
5. BookMaster
Sr. Field Name Type Primary
Key
Foreign Key
1 BookId Number Y
2 Title Text
3 PublishYear Number

27. Page : 27/41

28. Page : 28/41
6. LibaryCardMaster
Sr. Field Name Type Primary
Key
Foreign Key
1 LibID Number Y
2 HolderType Text

29. Page : 29/41
7. PublisherMaster
Sr. Field Name Type Primary
Key
Foreign Key
1 PubID Number Y
2 CompanyName Text
8. UserMaster
Sr. Field Name Type Primary
Key
Foreign Key
1 UM_Name Number Y

30. Page : 30/41
9. Transcation
Sr. Field Name Type Primary
Key
Foreign Key
1 TrnNo Number Y
2 Type Text

31. Page : 31/41
Library Management System– Data Schema ER Diagram

32. Page : 32/41
eLibrary ER Diagram

33. Page : 33/41
eLibrary DFD (Data Flow Diagram)
Context Level DFD
Context Flow Diagrams give us the complete details about
the inputs and outputs for a given system.
0 Level Data Flow Diagram
USER
eLibrary
Login
Accesses
View
Transcation
DBMS

34. Page : 34/41
1 Level Data Flow Diagram

35. Page : 35/41
Planning and Scheduling
Planning
Planning is very important in every aspect of development work.
Software project plan indicated scope of the project, milestones and
deliverables, project estimates, resource allocation, risk management,
scheduling techniques and quality control and standard. Software
project plan can be viewed as the following:

36. Page : 36/41
Gantt chart:

37. Page : 37/41

38. Page : 38/41
PERT chart:

39. Page : 39/41
Conclusion and future enhancement
This project was developed to fulfill user and business requirement;
however there are lots of scopes to improve the performance of the
Library Management System in the area of user interface, database
performance, and query processing time. Etc.
So there are many things for future enhancement of this project. The
future enhancements that are possible in the project are as follows.
• Linking and integration of any legacy system for accounting.
• Integration with bank database through Web Services
• Connection to third-party OLAP applications
• Implement Bar code reader
• Web interface for members
• In the area of data security and system security.
• Provide more online tips and help.
• To optimize the query which is embedded in the system.

40. Page : 40/41
Bibliography
Websites
• http://www.google.com
• http://www.microsoft.com
• http://www.programmer2programmer.net
• http://www.codeproject.com
• http://www.msdn.com.
• http://www.vb123.com
• http://www.vbcode.com
• http://www.sqltuner.com
Books
• Mastering Visual Basic 6 (Paperback)
• Mastering Visual Basic .NET (Paperback)
• Visual Basic Black Book (Paperback)
• SQL Bible, 2nd Edition (Paperback)
• Database Development in Visual Basic

41. Page : 41/41
You can get complete synopsis, project report with all diagrams, project source
code, MySQL database script and installation guide of
JAVA MySQL Library System only INR Rs. 2000/-
You can buy online at
http://www.readymadeproject.com/quickPay.aspx
For project demo and details please check project no 75
http://www.readymadeproject.com/aj/academic_project_list.htm
For further details please contact at
Email ajprofessionals@gmail.com or info@redaymadeproject.com or
call +91-9920329254