A Project Report on

LIBRARY MANAGEMENT
SYSTEM
 Under the guidance of
Prof.Rahul.Pune

Department of Commerce
Sinhgad College of Science
Pune -41

Savitribai Phule Pune University

Partial fulfillment of
TYBCA
Submitted
by

Your name : RAJ ROHAN

Roll No. 3066

Partner name : TRIPATHI SHUBHAM RAMAYANPRASAD

Roll No. 3077

❖ introduction
Before the successful launching of computerized

Software , all work was done manually . The different jobs were

Maintaining Member Record

Maintaining Book Record

Maintaining Fine Record

Maintaining Borrow Book Record

 The useful information was kept in registers. It was very difficult to
maintain the register for long period of time. It is great pleasure to
introduce the concept of computerized.

“Library ManageMent SySteM”

Ultimately the concept of computerized “Library Management System “ is
bound to replace the manual work, as it will help in saving of precious time
money and energy.

❖ PROBLEM
DEFINITION
Our Existing system is totally manual and it has many problems.

◼ Time Consuming

◼ Take more time to search

◼ Not get efficient result.

◼ Cannot be left blank :

While entering a new record or while making

modifications notable can be kept if you have given the
constaints not nul for it .

Either BOF or EOF or Current record has been

deleted . The operation requires a current record :
The beginning of file should not be empty for navigation the
records there should massages will be displayed .

Negative numbers are not allowed :

Nagative numbers are not allowed in any of the
fields . If negative numbers are entered then it will not be
accepted .
❖ Need for
computeri
zation

As the existing system running manually, the whole system

should be computerized. The existing manual works in the present
system are laborious and it is difficult to generate required
information as per the demand of the management.The
advantages of new system are mention bellow:

RELIABILITTY:
As the existing system is maintained manually work as taking
stock, recording entries of members may prone to error due to
human intervention.

TIME:
A lot of times require to issue or return a book in manual
system.

REPORTS :
Manual reports are prepared in order to support
management in keeping track of various transactions taking place.

SECURITY :
In case of manual system there is no such
mechanism for the sake of security so there are so many chance
of data lost or getting data corrupted.

PAPER WORK :
As the existing system is totally manual so lot of
paper work is done. One which mean maintaining registers and
file .for the documents since the process require a lot of clerical
work and calculations it results in lots of paper wastage.
❖SCOPE OF
T HE
proposed
SYSTEM
 The proposed system is a more user friendly. Any
person knowing the computer will be able to work this system. In
environment of java , the online information can be facilities for
easy operation of the forms. With the help of Menu bar many
event like Add, Edit, Delete, Find and Save can be provided.
Online information can be retrieved through
queries so the user has to generate reports frequently ,this will
be time saving. The system is centralized through a menu. So the
user works on this system smoothly. The system will concentrate
on the issuing and receiving of books and should keep track of
fine collected and various reports required as and when required.
System includes the modules like :-

Book :-
2.1 Add Book.
2.3 Return Book.
2.3 Book Information.
2.4 Remove Book.
Member : -
3.1 Add Member.
3.2 Member Information.
3.4 Remove Member.
Transaction : -
4.1 Borrow a Book.
4.2 Renew a Book.
4.3 Return a Book.
❖ Objective
of the
system

Time Saving

Less time to search

Efficient result.
❖Fact
finding
techniques

The specific methods used for collecting data about

requirements are called Fact Finding Techniques .This includes:

Record Review
Interview
 Questionnaire
Observation

Record Review:

Records include writer policy manual, regulations and standard

operating procedures used by the organization. Records
inspection can be done at the beginning. Records and Reports
provide the valuable information.

Interview:

This technique is used to collect information from individuals or

from groups. The interview is the best method of introducing
qualitative information like opinion, policies and subjective
description of activities and problems.

Questionnaire:
This technique is used to collect information about
various features of propose system. Questionnaire demands that
we carefully consider the objective of questionnaires. And
determine what will be most useful
We ask following question.

What are the problems in current

system?
How much time is required to borrow a
book?
Whether you get answer to your queries
 in short time?
How to maintain the member as well as
book Information?
What you expect from system?
In Case of book lost from member,which
procedure Follow library?
In Case of library card lost from
member, which Procedure Follow library?

Observation:
It allows the analyst to get
information, which cannot be obtained from any other techniques.
Through this the analyst can get the first hand information of
how things are actually carried out.
❖ Feasibility
study

The feasibility study is useful to evaluate the cost and benefits

of the system requested. There are three aspects in the
feasibility study:

Technical Feasibility
 Economical Feasibility
Operational Feasibility

Technical Feasibility:

The Technical Feasibility always focuses on the existing

computer hardware, software and the other components. It also
includes the need of above and possibility of installing such
facility.

Economical Feasibility:

It considered the cost/benefit analysis of the proposed

project. It is helpful to find the system development cost and
checks whether it is justifiable? With the help of this we also
find investigation cost,software & hardware cost, training cost,
salaries and maintenance cost etc.

Operational Feasibility:

It considered the acceptability of the system. It checks

whether system be used if it is developed and implemented? Are
the users of the system able to handle the system? Whether the
proposed system causes any trouble? Etc.
❖ Requireme
-nt
analysis

Hardware specification :

Processor: Pentium l or more for optimum

 Hard Disk: Minimum 5GB
RAM: Minimum 32MB
Input Devices: Keyboard, Mouse, Printer

Software specification:

Operating System: Windows

Front End Used: Vb.net 2008
Version: 5.0 or more compatible version
Back End Used: MS.Access
❖ SYSTEM
DESIGN

Entity Relationship DIAGRAM

DFD
 SEQUENCEM DIAGRAm

M : member Nu : Normal user B : Book system A : admin Bm : book master

login add/cancel`s

book

sent ack. sent ack.

gives info. and details

check fine and

sent ack.

check availability
issuing of book if present gives book

book is issued

renewing of book give`s detail to admin check due date

check
due
date
book renewed book renewed

returning of book give`s detail to admin book returned

 Use case diagram

Login
login

request book
Request book

admin
Checks
check boo
book

issue book
Issues
book
student
Book System

renewed
book

return
book

pay fine

log out
❖data
DICTIonary
Table Name: Admin

Field Type Null Key Default Extra

Unm Text Yes Null
Pwd Text Yes Null

Table Name: Faculty

Field Type Null Key Default Extra

Fno Int(11) No P.K. Null
Fname Text Yes Null

FMoNo int(11) Yes Null

Table Name: Department

Field Type Null Key Default Extra

Dno Int(11) NO P.K. NULL
Dname text YES NULL
HOD Int(11) YES NULL
Mobno Int(1!) YES NULL
Fno Int(11) YES NULL
Table Name: staffacc

Field Type Null Key Default Extra

Lid Int(11) No P.K. Null auto_increment
name Text Yes Null

mobno int(11) Yes Null

Table Name: studacc

Field Type Null Key Default Extra

Lid Int(11) NO P.K. NULL auto_increment
name text YES NULL
Class text YES NULL
rno Int(1!) YES NULL
Mobno Int(11) YES NULL
Table Name: Member

Field Type Extra

Null Key Default
mild Int(11) NO P.K. NULL auto_increment
Int(11) YES NULL
mcglid
Set(‘Student’,’teaching YES NULL
mtype staff’,’Non-Teaching
staff’)
text YES NULL
mfaculty
text YES NULL
mdept

Table Name: bookcpoies

Type Extra
Field Null Key Default
bnm Int(11) YES P.K. NULL auto_increment
bcode Varchar(11) YES NULL

bcopies Varchar(16) YES NULL

status Set(‘Available’,’Issued) YES NULL

Table Name: book

Field Type Null Key Default Extra

bno int(11) No PRI NULL auto_increment
bname Text YES NULL
bcode Varchar(12) YES NULL
bauthor Text YES NULL
bpub Text YES NULL
bvolume int(11) YES NULL
bprize float YES NULL
No_of_copy Int(11) YES NULL
Copyright Int(11) YES NULL
edition Int(11) YES NULL

Table Name: account

Type Extra
Field Null Key Default
Mild Int(11) NO P.K. NULL auto_increment
text YES NULL
Mname
Set(‘Student’,’teaching YES NULL
mtype staff’,’Non-Teaching
staff’)
Int(11) YES NULL
Mclgid
text YES NULL
Mclass
Rno Int(11) YES NULL
mbno Int(11) YES NULL
Table Name: issue

Field Type Null Key Default Extra

bnm Text YES NULL
bcode Varchar(11) YES NULL
bno Varchar(16) YES NULL
curdate Date YES NULL
idt Date YES NULL
rtdt Date YES NULL
mild Int(11) YES NULL
status Text YES NULL
flag Int(11) YES NULL
fine float YES NULL

Table Name: member1

Field Type Null Key Default Extra

mno Int(11) NO P.K. NULL auto_increment
mlid Int(11) YES NULL
mtype text YES NULL
mfaculty text YES NULL
mdept text YES NULL
mclass text YES NULL
Date text YES NULL
❖TESTING
STRATEGIE
 Testing is the process of detecting errors. Testing
performs a very critical role for quality assurance and ensuring
the reliability of software. The results of testing are used later
on during maintenance also.

Unit Testing :
Individual component are tested to ensure that they

operate correctly.Each component are tested to ensure that they

operate correctly.

Module Testing:
A module is collection of dependent components such

as object class,an abstract data type or some looser collection

.Each module is tested individually.

System Testing:
The sub-system is integrated to make the entire

system. It is concern with validating that system meet its

functional & non functional requirements.

Acceptance Testing:
This is the final step in testing process . It is also

referred as Beta Testing .In this the system is tested by user or

client.Some Types of testing are:

1. White box testing

2. Black box testing

 3. stress testing

4. Performance testing

5. Alpha & Beta testing

White Box Testing :

• Local paths through code are tested.

1. Conditionals
2. Loops
3. Branches.
• Status is examined in terms of expected values.

• It is impossible thoroughly exercise all paths. So it can

be practical if a limited number of important paths are
evaluated and examine and test the important data
structures.

Black Box Testing :

• For the software Black box testing is testing the
interface.

1.W hat is input to the system ?

2.What you can do from outside to change the
system .
3. What is output from the system.
• It test the functionality of the system by observing its
external behaviour.

• No knowledge of how it goes about meeting the goals.

❖ INPUT
SCREEN
❖ User
manual
The user requires computerized library management system,
so that processing becomes faster.

All information must be stored on a database.

They require a standard format for the main report.

They want to eliminate duplicate of data entry.

❖LIMITATION
AND
DRAWBACK`S
LIMITATIONS:

This system is design to be a

standalone and dose not Work on
Network site.
The system does not make use of
Status bar to provide on Line
support.
This system does not provide
barcode scanning facility.

DRAWBACKS:

Only authorized person can use this project.

This project is limited for school and college library only.
This project is not apt for industrial work.
The small library database system will be used by the
various department of a local college to track the borrowing
of books and other forms of media .Software`s secretary
will operate the system and will responsible for checking out
book`s to student and faculty members.
❖FuTURE
ENHANCEME
NTS
 This application is not fully perfect in
views of client server application as well as
online application.

In feature this system also provides

barcode facility along with online information
❖ CONCLUSION
 This application is useful to reduce the time
which is required to Borrow, Return & Renew etc. in
manual System & Computerized system also provide
facility for checking member photos along with
maintaining time of transactions. This system also
provide automate generation of return dates (Only
calculate working days) & in spite of calculate fine also.