Library Management System

1. INTRODUCTION

1.1 AIM

The aim of the Library Management System project is to create information about the books for
members and administration. There are registered people in the system is economical and it is
developed within the required time, which includes task such as:

 Adding new users, Books, PDF.

 Updating users, books and magazines.
 Deleting users, books and magazines.
 Searching for books.
 We will use software name Dreamweaver which will help to design the module present in
it.

This project “Library Management System” of gives us the complete information about the
library. We can enter the record of new books and retrieve the details of books to the students and
maintain their records and can also check how many books are issued and stock available in the
Library.

1.2 OBJECTIVES

 To eliminate the paper work in library.

 To record every transaction in computerized system so that problem such as record file
missing won’t happen again.
 To implement Barcode, SMS technologies into the system.
 To design a user friendly graphical user interface which suit the user.
 To complete the system according to project schedule.
 To produce technical report that documents the phases, tasks and deliverables in the project.
 Maintain User Friendly, Robust and User Customizable software product.

1.3 VISION
All residents of students will have equal access to excellent library service.

1
 Library Management System

2. PROJECT/PROBLEM SELCTION
The major Project was designed to approach the aims and solve the problems which book readers
are dealing with when it comes to Library; it covers the design, implementation and solutions.
What caught my interested in this project is the desire to help and or facilitate the iterations
between the Libraries and the readers, as we can see in nowadays when we go to the library we do
not know if the book that we want is there and if it is available, thenceforth that is why I aim to
build an Enterprise Application that will help the libraries and readers in the future. In this
document I will describe witch technologies I will use, the data base structure, programming
language and all the diagrams which will explain each process or workflow that is implemented in
the application. At the end of this project the application that I have built will help and or
facilitate the communication among Libraries and readers.

The basic problems goes around the inter-communication among libraries and readers, and as we
know libraries are a little distant from the readers, plus have a lot of books, making it a bit
difficult to find a specific book. Another problem I could find was revolving around the
management of books, the problem is when we want to loan some book, the readers goes to
library and discovers that the book he want is borrowed, and the readers does not know when the
book will return to become available, and he can goes back to the library another day but he can
comes across with a borrowed book again.

Among the problems I found, I marked three very interesting to highlight are:

 Many readers are omitted information that are in books or papers with electronic
information
 When the libraries have a lot of book and according to the amount of books it is bit
difficult to manage the loan
 Staffs of the libraries use papers to record information about the loan, and when they want to
search some information about the loan it become difficult.

2
 Library Management System

3. PROJECT MONITORING SYSTEM

3.1 PERT CHART

3
 Library Management System

4. SYSTEM STUDY
4.1 EXISTING SYSTEM ALONG WITH DEFICIENCIES

 To check the availability of the book.

 Manual System.
 The librarian has to perform each task.
 Time manipulation.
 Updating is tedious work.
 Issuing and receiving of the books.
 Penalty is very complex.
 Generating report is complex

4.2 PROPOSED SYSTEM WITH INTENDED OBJECTIVE

As we have seen in earlier topic, the existing system follows which create the
need for the system.

 To eliminate the paper work in library.

 To record every transaction in computerized system so that problem such as record file
missing won’t happen again.
 To implement Barcode, SMS technologies into the system.
 To design a user friendly graphical user interface which suit the user.
 To complete the system according to project schedule.
 To produce technical report that documents the phases, tasks and deliverables in the project.
 Maintain User Friendly, Robust and User Customizable software product.

4.3 FEASIBILITY STUDY

Whatever we think need not be feasible. It is wise to think about the feasibility of any problem we
undertake. Feasibility is a study of impact, which happens in the organization by the development
of the system. The impact can be either positive or negative when the positive nominates the
negative the system is consider to be feasible.

4
 Library Management System

Types of feasibility:

4.3.1 Technical:

We can strongly say that it is technically feasible, since there will not be much difficulty
in getting required resources for the development and maintaining the system as well. All
the resources needed for the development of the software as well as the maintenance of the
same is available in the organization.

4.3.2 Economical:
Development of this application is highly economically feasible. The organization needed
not spend much money for the development of the system already available, the only thing
is to be done in making an environment for the development with an effective supervision.

4.3.3 Operational:
Creation of a major software system makes demand on the development team.
Does the team have management expertise?
Does the team have technical expertise?
Can the team accommodate changes in personnel, project requirements, work flow?

5
 Library Management System

5. SYSTEM ANALYSIS

5.1 REQUIREMENT SPECIFICATION

The software requirement specification document consistent of all necessary requirements
required for project development. To achieve this we need to continuous communication with
customers to gather all requirements.

HARDWARE SPECIFICATION:
Hard Disk: 20 GB and above.
RAM: 512 MB and above.
Processor: Pentium 4 and above, or any other equivalent processor.

SOFTWARE SPECIFICATION.

Operating System: Windows XP and above.

Documentation tool: Microsoft Word 2007.
TECHNOLOGIES USED

Operating system: Windows XP.

Development Tools: Visual Basic 6.0, Oracle 9.0 for backend.

5.1.1 FUNCTIONAL REQUIREMENT

R.1: Register

 Description: First the user will have to register/sign up. There are two different type of users.
 The library manager/head : The manager have to provide details about the name of library
address, phone number, email id
 Regular person/student: The user have to provide details about his/her name of address, phone
number, email id.

R.1.1: Sign up

 Input: Detail about the user as mentioned in the description.

 Output: Confirmation of registration status and a membership number and password will be
generated and mailed to the user.
6
 Library Management System

 Processing: All details will be checked and if any error are found then an error message is
displayed else a membership number and password will be generated.

R.1.2: Login

 Input: Enter the membership number and password provided.

 Output: User will be able to use the features of software.

R.2: Manage books by user.

R.2.2: Books issued.

 Description: List of books will be displaced along with data of return.

R.2.2: Search

 Input: Enter the name of author's name of the books to be issued.

 Output: List of books related to the keyword.

R.2.3: Issues book

 State: Searched the book user wants to issues.

 Input: click the book user wants.
 Output: conformation for book issue and apology for failure in issue.
 Processing: if selected book is available then book will be issued else error will be displayed.

R.2.4: Renew

 bookState: Book is issued and is about to reach the date of return.

 Input: Select the book to be renewed.
 Output conformation message.
 Processing: If the issued book is already reserved by another user then error message will be
send and if not then conformation message will be displayed.

R.2.5: Return

 Input; Return the book to the library.

 Output: The issued list will be updated and the returned book will be listed out.

R.2.6; Reserve book

 Input; Enter the details of the book.

7
 Library Management System

 Output: Book successfully reserved.

 Description: If a book is issued by someone then the user can reserve it ,so that later the user
can issue it.

R.2.6 Fine

 Input: check for the fines.

 Output: Details about fines on different books issued by the user.
 Processing: The fine will be calculated, if it crossed the date of return and the user did not
renewed if then fine will be applied by Rs 10 per day.

R.3 Manage book by librarian

R.3.1 Update details of books

R.3.1.1 Add books

 Input: Enter the details of the books such as names ,author ,edition, quantity.
 Output: confirmation of addition.

R.3.1.2 Remove books

 Input: Enter the name of the book and quantity of books.

 Output: Update the list of the books available.

8
 Library Management System

5.1.1 USE CASE DIAGRAM

9
 Library Management System

5.1.2 CLASS DIAGRAM

10
 Library Management System

5.1.3 SEQUENCE DIAGRAM

11
 Library Management System

5.1.4 COLLABORATION DIAGRAM

5.1.5 COMPONENT DIAGRAM

12
 Library Management System

5.1.6 ACTIVITY DIAGRAM

13
 Library Management System

5.2 System Flowchart

Start

Administration Enter user name Enter user password

Stop
Is user name Verification
& pwd
Disconnect correct
correct user
jjjjjjcorrect &

Layout
User Register

Add user Update user info Delete user Search Book

Search by title
Add user detail Modify user detail Delete User info

Retrieve Detail

Show detail

Stop
14
 Library Management System

5.3.1 DATAFLOW DIAGRAM

Books
Management
Library
management Authors
management

LIBRARY
Publisher MANAGEMENT
SYSTEM System user
management
management

Log in
management

15
 Library Management System

5.3.2 E-R DIAGRAM:

Book_id author

Pub_id
title
address

Published
price books
by Publisher

name
available

Expiry_date
Name

Due date

Borrow by Member
Address

Return
date Memb_type
Issue

Memb_id
Memb_date

16
 Library Management System

5.4 SOURCES OF DATA

Libraries already working with activity data have identified a range of sources for the purposes of
Collection Management, Service Improvement, Recommender Services and Student Success.
Potential uses of data will be limited where the user is not identified in the activity

17
 Library Management System

6. SYSTEM TESTING
Testing is one of the important steps in the software development phase. Testing is performed to
identify errors and is an integral part of the entire development and maintenance process. The
Library Management System has been put under rigorous testing so as ensure the correctness of
its design. The two basic testing strategies that were used:

1. Unit Testing
2. Integration Testing.

6.1 UNIT TESTING

Unit testing was conducted to verify the functional performance of each modular component of
the software. Unit testing focuses on the smallest unit of software design i.e. the module. White-
box testing were heavily employed for unit testing.

6.1.1 LOGIN TEST CASE

18
 Library Management System

6.2 INTEGRATION TESTING

“Unit testing” focuses on testing a unit of the code. “Integration testing” is the next level of
testing. This level of testing focuses on testing the integration of “units of code” or components.

The Library Management System was tested as a whole

6.2.1 Circulation and Remove Member Test Case

19
 Library Management System

7. FUTURE SCOPE
 To make the software platform-independent.
 To make the software general accessibility to the users.
 Giving inner topics highlights of the book searched.
 Providing space for online suggestions.
 To add more features and graphics making it user friendly.

20
 Library Management System

REFERENCES
1. https://nevonprojects.com>akshadham project

2. https://www.javatpoint.com>library-management-project

3. https://www.scribd.com>doc>library

4. https://sourceforge.net>

5. https://gitthub.com

6. Library System. https://www.researchgate.net/publication/304571194_Library_System

DIKSHANT GUPTA (dikshantgupta.1998@gmail.com)

21