PROJECT REPORT

ON

LIBRARY MANAGEMENT SYSTEM

Library management system project report – The main objective of the Library Management
system project is discipline of the planning, organizing and managing the library tasks. Our
project aims at making the task of library easy. Library Management is entering the records
of new book and retrieving the details of book available in the library. We can issue book to
the library member and maintain their records and can also checks how many book are issued
and stock available in the library. In the project we can maintain the late fine of library
member who return the issued book after the due date. This Library management system
project in JAVA and MS SQL server.

INTRODUCTION

Central Library is a large Books library which store Books, Publisher, Author and Issue
details of Library member. The Central Library needs to maintain record of its Member,
Books , Author and Publisher and the Issue details of books. The Library wants to develop
an application for the rental system. The DBMS they wants to use is MySql. The application
is to be coded using Java Net Beans.
The Central Library wants to be developed using Java Net Beans, is form based and should
have for the following :-
 Maintain Books Details
 Maintain Author Details
 Maintain Publisher Details
 Maintain Member details
 Issue Book
 Return Book
 Print Various Reports
Design a high level Project of Library Database Management System taking account of the
following things :-
A very brief account about System Requirements
Details on Normalized Tables
Constraints on Data Values
Referential Integrity Constraints
Design Forms and Reports
A Library Database Management System should contain the data of all the books present in
the Library. The books data should contain the Number of copies bought by the Library, the
data of Purchase and Book ID of the Book. The Database should have all the kinds of the
Students present in the University. The Project requires to Issues books to Students for
Fifteen Days. A Rupee is charges per day for all the extra days for which the book is kept.
Every Transaction should be recorded on the Database so that History could kept about the
Book. A Student should not be given more than two books at a time. Other books can be
provided after the Students return both the Books. A Person should give information of the
Employees working in the Library. The System should provide to query all the Books issued
by a particular Employees. The System should provide the reports of all the Students who
had the Book on a particular data.
The main purpose of this computerized package is to reduce service time to the Consumer is
to reduce service time to the Consumer with minimum risks of errors. This package is based
on the small scale. Similar modules can attached to the project to make it
ISSUE / RETURN
 When a member wants to issue a resource, he / she approaches the computerized
system ( counter)
 The autority –in-charge draws up the members account and if the system issuance
policy permits, issues the resource to tat members account
 When resources are returned , this is reflected back in the member’s account and
issued resources database.
SEARCH FACILITY
 The user may choose any one of the search types
 The relevant information to search is directly entered by te suer
 The system finds the best matches and displays the same for the user.
 Te system should also provide for graphical location of the resources on the library
map.
CASH MANAGEMENT
 Fines should be calculated without explicit execution
 Alerts should be indicated when a member has due fine
 Activities of this subsystem should be visible to te accounts department of the
organization
NON-FUNCTIONAL REQUIREMENTS
 Since the search facility is directly used by members, it should be easy to use and be
supported with the help function
 Issue / return of resources should be allowed only by authorized users. The same also
applies for cash manmagement
 Data warehousing should be provided for since it is not possible to keep all data
online
 Large memory is necessary to maintain an active database of operational resources
 The system is I/O intensive and not computation intensive since the major functions
include retrieval and modification of stored data
 Entryof user code, resource code etc should be as automatized as possible.
S/W MODULES
TRANSACTION MODULE
 Responsible for issue / return of books
 Fine calculation
 Reservation of resources
SEARCH MODULE
 Provides Keyword based search
 Provides graphical map of library to track resource
ACCOUNT MODULE
 Responsible for account creation / deletion / modification
 Account lock facility
RESOURCE MODULE
 Responsiblefor resource entry / maintenance
 Mapping of resources
FUNCTIONAL REQUIREMENT
The following services are provided by the sysem
ISSUE / RETURN
Library resources loaned to its members are kept track of by recording this information into
each one’s account. The systems account database and resources database serve this function
and should be password protected to avoid tempering by unauthorized persons
SEARCH FACILITY
Any of the Library resources can be easily located using this facility. The search can be
carried out in one of thefolowing manners :-
 Generaic Search :- Any keyword matching a resources title , author, publication and
other metadata is located
 Search by Author :- Used when a use wants to list or located resources by authors
name
 Search by Title :- Usually a resources title is the one knownto the user.
Project category :

RDBMS

Language and software tool used :

 Front End : Java

 Operating System : Window 7
 Back End : My SQL

Structure of the project:

Proposed System:

In the proposed system, we assume that each member will be having a identity card which
can be used for the library book issue, fine payment etc. whenever library member wish to
take a book, the book issued by the library authority will be check both the book details as
well as the student details and store it in library database. In case of retrieval of book much of
human intervention can be eliminated.

Module Description:

1. User Module:

In this module student can check availability of the book…

The following are the sub module in the user module.

 Book return: Here student will return the books to the library…

2. Administrator Module:

This is the main module in the proposed project. The administrator can read and write
information about any member. The administrator can also update, create and delete the
record of membership as per requirement and implementation plans.

The following are the sub module in the administrator module.

  Register student: Allow the administrator to register new student and update the
student records.

 Book details: Allow administrator to entered book details.

 Book issue: Here administrator issues the books to the student from library.

Future scope of the project:

We can consider much future scope to this application. The following are some of there.

 Online use of the library can be good feature for the Library Management system.
 Advanced fine payment system can be added.
 Inventory system can be used to maintain the books of the library.

Hardware requirement :

 Operating system: Window 7

 Hard disks: 40GB
 RAM: 256 MB

Software requirement :

 Java language
 Net beans IDE 7.0.1
 MS SQL server 2005
 DATABASE DESIGN

A database is a collection of information or data. A database contains different tables that will
have a unique identity. The data will be stored in the form of rows and columns in these
tables. The fields that are stored in the tables will be having different data types like integer,
varchar, date/time etc. The entity relationship diagram will give logical structure of the
database. Model is an approach that is commonly used in the database design. The ER
diagram will give the relationships between various entities in the database. Entity is
represented as rectangular shape and the relationship is represented in diamond shape. Entity
is a thing through which the information is stored. Relationship is the connection between
entities. Attributes are the properties of entities. The databases that are included in the library
management system are as follows:

 Book details: This database contains the field names like account number, author,
title, publication, edition, number of copies, volume price status etc.
 Student: This database contains the field names like name, register number, date of
issue, addresses, date of return, course, account number and gender.
 Issue: This database contains the field names like register number, date of issue
books, date of return books, account number, name, course, author, volume and
edition.
 Return: This database contains the field names like register number, date of issue
books, date of return books, account number, name, course, author, volume and
edition.
Library Management System Database design:
Student details:

In this form the users have to enter the details about the student like name, regno,
course…etc. If the proper details are not entered at the same time error message will be
displayed and record will not be stored...And if the entered register number is already exist
then the details can’t be stored and error message will be displayed.

Delete student details:

In this case admin can delete individual student details by entering his register
number .If the Register no is not entered at same time message will be displayed and record
will not be stored…And if the entered number is already deleted then it will be giving the
message.

Book issue:

In this form the Liberian can issue the books to the student. If the books are already
distributed to students then Liberian can’t issue those particular books.

Book return:

Here the user must return the book on given date... Otherwise fine will be calculated...

Calculate fine:

In this case we can maintain the late fine of library member who return the issued book
after the due date…
Private void srchNameRBActionPerfomed(java.awt.event.ActionEvent evt)
{
If(srchNameRB.isselected())
{
dispLabel1.setText(“Enter name”);
dispLabel2.setEnabled(false);
UpperTF.setEnabled(false);
}
Else
{
dispLabel1.setText(“Enter lower limit”);
dispLabel1.setEnab(tru);
UpperTF.setEnabled(true);
}
}
Private void ConfirmBtnActionPerformed(java.awt.event.ActionEvent evt)
{
Int qtyA=Integer.parseInt(tQtyLbl.getText());
Int qtyO=Integer.parseInt(ordQtyTF.getText());
If(qtyO>qtyA)
JoptionPane.showMessageDialog(rootPane,”Only” + “Items of “ +tcodeLbl.getText()+”are in
Stock !\n SORRY, Cannot Take Your Order”);
Else
{
Float amt = qtyO * Float.parseFloat(tPriceLbl.getText());
Float total=Float parseFloat(totAmtLbl.getText());
defaultTableModel model=(DefaultTabModel)orderTbl.getModel();
int tc=Integer.parseInt(tcodeLbl.getText());
String qry=”UPDATE TOYS SET QTYINSTOCK=qtyinstock”+qtyO+”WHERE
toyCode=”+tc+”;”;
Try
{
Class.forName(“java.sql.Driver”);
Connection con=DriverManager.getConnection(“jdbc:mysql://localhost/test”,”root”,”xyz”);
Statement smt=con.CreateStatement();
Smt.executeUpdate(qry);
Model.addRow(new Object[]
{
tcodeLbl.getText(),tNameLbl.getText(), tPriceLbl.getText(), orderQtyTF.getText(),amt});
total=total+amt;
totAmtLbl.setText(“+total);
}
Catch(Exception e)
{
JOptionPane.showmessageDialog(null,”Error in Connectivity”);
}
ordqtyTF.setText(“ “);
ordQtyTF.setEnabled(false);
buyCB.setSeleceted(false);
}
}

Private void searchBtnActionformed(java.awt.event.ActionEvent evt)

{
emptyList();
String filter=” “;
If(scrhNameRB.isSelected())
Filter=”WHERE name=’”+lowerTF.getText()+”’”;
Else if(srchPriceRB.isSelected())
{
Float priceL=Float.parseFloat(lowerTF.getText());
Float priceF=Float.parseFloat(UpperTF.getText());
Filter=”WHERE Price>=”+priceL+”and price<=”+priceF;
}
Else if(srchAgeRB.isSelected())
{
Int age=Integer.parseInt(lowerTF.getText());
Filter=”WHERE agegrouplowerlimit<=”+age+”and ageupperlimit>=”+age;
}
Int count=0;
String query=”SELECT name from toys”+filter+”;”;
DefaultListModel model=(DefaultListModel)toysList.getModel();
Try
{
Class.forName(“java.sql.Driver”);
Connection con=DriverManager.getConnection(“jdbc:mysql://localhost/test”,”root”,”xyz”);
Statement stmt=con.CreateStatement();
ResultSet rs=stmt.executeQuery(query);
While(rs.next())
{
Model.add(count, rs.getString(“name”);
Count++;
}
Rs.close();
Stmt.close();
Con.close();
}
Catch(Exception e)
{
JOptionPane.showMessageDialog(null,”Error in Connectivity”);
}
ordQtyTF.setEnabled(false);
}
Private void srchAgeRBActionPerformed(java.awt.event.ActionEvent evt)
{
If(srchAgeRB.isSelected())
{
dispLabel1.setText(“Enter Age”);
displabel2.setEnabled(false);
UpperTF.setEnabled(false);
}
Else
{
dispLabel1.setText(“Enter lower limit”);
displabel2.setEnabled(true);
UpperTF.setEnabled(true);
}
}
Private void exitBtnActionPerformed(java,awt.event.ActionEvent evt)
{
JOptionPane.showMessageDialog(rootPane,” Thank you using the E-Business application “);
System.exit(0);
}
Private void toyListValueChanged(javax.swing.event.ListSelectionEvent evt)
{
String selVal=(String) toyList.getSelectedValue();
String query=”SELECT * FROM Toys WHERE name=’”+setVal+”’;”;
Try
{
Class.forName(java.sql.Driver”);
Connection con=DriverManager.getConnection(“jdbc:mysql://localhost/test”,”root”,”xyz”);
Statement stmt=con.CreateStatement();
ResultSet rs=stmt.executeQuery(query);
Rs.next();
{
tcodeLbl.setText(“’””+rs.getInt(1));
tNameLbl.settext(rs.getString(2));
tDesLbl.setText(rs.getyString(3));
tqtyLbl.setText(“”+rs.getInt(4));
tageGrpLbl.setText(“’”+rs.getInt(5)+”to”+rs.getInt(6));
tPriceLbl.setText(“’”+rs.getFloat(8));
}
Rs.close();
Stmt.close();
Con.close();
}
Catch(Exception e)
{
JOptionPane.showMessageDialog(“null,”Error in Connectivity”);
}
}
Private void buyActionPerformed(java.awt.event.ActionEvent evt)
{
If(buyCB.isSelected())
ordQtyTF.setEnabled(true);
}
Private void srchPriceRBActionPerformed(java.awt.event.ActionEvent evt)
{
If(srchPriceRB.isSelected())
dispLabel2.setEnabled(true);
UpperTF.setEnabled(true);
}
}
Private void submitBtnActionPerformed(java.,awt.event.ActionEvent evt)
{
defaultTableModel model=(DefaultTableModel)orderTbl.getModel();
int count=model.getRowCount();
String total=totAmtLbl.getText();
JOptionPane.showMessageDialog(rootPane,”You have ordered for “ + count + “ items \n and
your b ill amount is Rs.”+total);
}
<BODY>
<H3>Online Order Form</H3>
<P>Please enter your Name, Billing address and Shipping Address. Please do not forget the
order number from our online catlog listings. Thanks for Shopping </P>
<FORM METHOD="SEND" ACTION="http://www.fakecorp.con/ccgi.bin/order">
<HR>
Please Enter a Full name and Address for BILLING Purpose <BR>
First Name : <INPUT TYPE="Text" Name="first" SIZE=25" MAXILENGTH="24"><BR>
Last Name : <INPUT TYPE="Text" Name="last" SIZE=25" MAXILENGTH="24"><BR>
Address Name : <INPUT TYPE="Text" Name="address" SIZE=25"
MAXILENGTH="24"><BR>
City Name : <INPUT TYPE="Text" Name="cityt" SIZE=25" MAXILENGTH="24"><BR>
State Name : <INPUT TYPE="Text" Name="state" SIZE=25" MAXILENGTH="24"><BR>
<HR>
<INPUT TYPE="CHECK BOX" NAME="same_add">Check if Shipping Address is
Different from Mailing Address
<HR>
<TEXTAREA NAME="ship_add" ROWS="3" COLS="60" WARP="PHYSICAL">
Enter Shipping Address here if Different from above.
</TEXTAREA>
<HR>
Please enter the code for the product you wish to purchase<INPUT TYPE="TEXT"
NAME="prod_num" SIZE="7" MAXLENGTH="6">
<HR>
How would like to pay for this ><BR>
<SELECT NAME="credit">
<OPTION SELECTED VALUE="must">MasterCard
<OPTION VALUE="Visa">Visa
<OPTION VALUE="disc">Discover
</SELECT>
Please Enter the Card Number:<INPUT TYPE="TEXT" NAME="card_num" SIZE="17"
MAXLENGTH="16"<BR>
<BR>
Please take <BR>
<INPUT TYPE="reset">
<BR>
<INPUT TYPE="submit" VALUE="Submit Order">
</FORM>
</BODY>

BODY>
<H3>Online Order Form</H3>
<P>Please enter your Name, Billing address and Shipping Address. Please do not forget the
order number from our online catlog listings. Thanks for Shopping </P>
<FORM METHOD="SEND" ACTION="http://www.fakecorp.con/ccgi.bin/order">
<HR>
Please Enter a Full name and Address for BILLING Purpose <BR>
First Name : <INPUT TYPE="Text" Name="first" SIZE=25" MAXILENGTH="24"><BR>
Last Name : <INPUT TYPE="Text" Name="last" SIZE=25" MAXILENGTH="24"><BR>
Address Name : <INPUT TYPE="Text" Name="address" SIZE=25"
MAXILENGTH="24"><BR>
City Name : <INPUT TYPE="Text" Name="cityt" SIZE=25" MAXILENGTH="24"><BR>
State Name : <INPUT TYPE="Text" Name="state" SIZE=25" MAXILENGTH="24"><BR>
<HR>
<INPUT TYPE="CHECK BOX" NAME="same_add">Check if Shipping Address is
Different from Mailing Address
<HR>
<TEXTAREA NAME="ship_add" ROWS="3" COLS="60" WARP="PHYSICAL">
Enter Shipping Address here if Different from above.
</TEXTAREA>
<HR>
Please enter the code for the product you wish to purchase<INPUT TYPE="TEXT"
NAME="prod_num" SIZE="7" MAXLENGTH="6">
<HR>
How would like to pay for this ><BR>
<SELECT NAME="credit">
<OPTION SELECTED VALUE="must">MasterCard
<OPTION VALUE="Visa">Visa
<OPTION VALUE="disc">Discover
</SELECT>
Please Enter the Card Number:<INPUT TYPE="TEXT" NAME="card_num" SIZE="17"
MAXLENGTH="16"<BR>
<BR>
Please take <BR>
<INPUT TYPE="reset">
<BR>
<INPUT TYPE="submit" VALUE="Submit Order">
</FORM>
</BODY>
Library Home

Book Search
Issue of Book

Return Book
New Book Details

Barrower Details
Book Details
CONCLUSION:

The package was designed in such a way that future modifications can be
done easily. The following conclusions can be deduced from the development of
the project.

 Library Management System of the entire system improves the efficiency.

 It provides a friendly graphical user interface which proves to be better when
compared to the existing system.
 It gives appropriate access to the authorized users depending on their
permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is necessary.
Future scope of the project:

We can consider much future scope to this application. The following are some of there.

 Online use of the library can be good feature for the Library Management system.
 Advanced fine payment system can be added.
 Inventory system can be used to maintain the books of the library.

BIBLIOGRAPHY

 IvanBayross, “MySql Developer 2000”, BPB Publication 2001, 2rd Edition

 Kevin Loney & George Koch ,” MySql 8i”, Tata Mc Graw Hills Publications 2000,2 nd Edition
 Sliberschatz, Korth and Sudarshan – Database System Concepts 3rd Edition
 Univ. Books ( Java Net Beans )
 Mastery in Java Net Beans 6.0.
 Java Net Beans Complete Reference
 Data Base Programming using MySql.