Library Management System

CHAPTER 1

INTRODUCTION

1.1 ABOUT LIBRARY MANAGEMENT SYSTEM

Library Management System (LMS) is automated library management

software which provides a simple GUI (Graphical User Interface) for the Library Staff
to manage the function of the library effectively and for Student to see information. In
a manual system, when a book is returned to issued, it is noted down in a register to
update the status of the books in a moderate scale. This process takes some time and
proper updating cannot be guaranteed. Such anomalies in the updating process can
cause loss of books. So a more user friendly interface which could update the
database instantly has a great demand in libraries. The goal of this project is to
provide simplicity as well as effective software for the management system software
stores the database information on a local computer, which ensures that all the data is
present on a single and back up can be taken time to time.

1.2 EXISTING SYSTEM

 In our existing system all the transaction relating to borrowing the books are done
manually, taking more time for transaction like borrowing a book or returning a
book and also for searching of students and books.
 Another major disadvantage is that to prepare the list of books borrowed and the
available books in the library will take more time. Currently it is being done as a
one day process for verifying all records.
 This type of maintenance usually causes errors due to delay in updating and
mistakes during large data entry.
 So after conducting the feasibility study we decided to make the manual Library
Management System to be computerized.

DOS IN CS&E UBDTCE , Davangere Page 1

Library Management System

1.3 PROBLEM DEFINITION

The problem in hand was to develop Windows based software to help the library
staff to maintain and organize a library. There is a need to develop a Library
Management System which provides an easy to use user interface to make the
existing system more efficient.

 It is difficult to catch defaulters in a manual library system. LMS should solve this
problem by providing message to the administrator about the fine to be paid and
books to be returned.
 When the administrator tries to issue a book to a student, LMS should check
whether the student is allowed to barrow books respective to his/her limit.
 If the book has no restriction it should be issued to the student, and also the
students details should be updated with the books that he has just borrowed.
 Administrator can search a book with its different attributes.
 Result should be generated for available books, issued books or number of books
borrowed by each student.

1.4 OBJECTIVES

The objective of this project is to develop a windows application, designed

to help users maintain and organize library. This software is easy to use for both
beginners and advanced users. It features a familiar and well though-out, attractive
user interface, combined with strong searching, insertion and reporting
capabilities. The report generation facility of library system helps to get a good
idea of which are the books borrowed by the students, which are the books
available in the library and to calculate the precise fine amount for the defaulters.

DOS IN CS&E UBDTCE , Davangere Page 2

Library Management System

1.5 PROPOSED SYSTEM

 In Library Management System, the processing of transaction is done with the
help of computer.
 LMS provides a very simple GUI.
 Through LMS, updating to the database is very efficient and instantly done.
 LMS provides security, i.e. only the administrator can update any information
to the database.
 Error generation for Authentication purpose and also for constraints on the
number of books allowed for a particular student.
 Member can be a Student, or Lecturer or Nonteaching Staff, and respective
limits for borrowing books for each type of member is set.
 Student can see his/her details.
 Student can see his/her History of Borrowed or Returned books.

DOS IN CS&E UBDTCE , Davangere Page 3

Library Management System

CHAPTER 2

LITERATURE SURVEY

A literature survey is text of scholarly paper, which includes the current

knowledge including substantive findings, as well as theoretical and methodological
contributions to a particular topic. Literature survey are secondary sources, and do not
report new or original experimental work. Literature survey is basis for research in nearly
every academic field.

Producing a literature survey may also be part of graduate and post-graduate student
work, including in the preparation of a thesis dissertation, or a journal article. Literature
surveys are also common in a research proposal or prospectus (the document that is
approved before a student formally begins a dissertation or thesis.

1.Mysql JDBC DRIVER: It is an open source java JDBC driver implementation

that allows java developers and JDBC client programs to read or write mysqldatabases.
Because it is a pure java implementation it runs on both windows and non-windows
operating systems.

 Supported access formats: 2000,2002/2003,2007,2010/2013/2016 databases.

2. Java Swing, 2nd Edition By Robert Eckstein: This thoroughly covers all the
features available in Java 2 SDK 1.3 and 1.4.More than simply a reference, this new
edition take a particular approach. It is a book by developers for developers, with
hundreds of useful examples from beginning level to advanced, covering every
component available in swing. Whether you’re a seasoned Java developer or just trying to
fine out what Java can do, you’ll find Java Swing ,2nd edition an indispensible guide.

DOS IN CS&E UBDTCE , Davangere Page 4

Library Management System

CHAPTER 3

SYSTEM REQUREMENTS

3.1 HARDWARE REQUIREMENTS

Hard Disk : 20 GB and More

RAM : 512 MB and More
Processor : Pentium 4 and above, or any other equivalent processor.

3.2 SOFTWARE REQUIREMENTS

Operating System : Windows XP/Windows 7/Windows 8/Windows 10

Runtime Environment : Java 2 Runtime Environment
Back end/Database : Mysql 2003 and above
Development Tools : JDK 8.1, NetBeans IDE 8.1
Documentation Tool : Microsoft Word 2007 and above

DOS IN CS&E UBDTCE , Davangere Page 5

Library Management System

CHAPTER 4

SYSTEM ANALYSIS
System Analysis is a detailed study of the various operations performed by
a system and their relationship within and outside of the system. Here the key
question is what all problems exist in the present system? What must be done to
solve the problem? Analysis begins when a user or manager begins a study of the
program using existing system. During analysis, data collected on the various
files, decision points and transaction handled by the present system. The
commonly used tools in the system are Data Flow Diagram, interviews, etc.
Training, experience and common sense are required for collection of relevant
information needed to develop the system.
The success of the system depends largely on how clearly the problem is
defined, thoroughly investigated and properly carried out through the choice of
solution. A good analysis model should provide not only the mechanisms of
problem understanding but also the frame work of the solution. Thus it should be
studied thoroughly by collecting data about the system. Then the proposed system
should be analyzed thoroughly in accordance with needs.

System analysis can be categorized into four parts.

 System planning and initial investigation
 Information Gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/Benefit analysis.

4.1 SOFTWARE REQUIREMENT SPECIFICATION(SRS)

This is the Software Requirements Specification (SRS) for the LMS
(Library Management System). The purpose of this document is to convey
information about the application’s requirements, both functional and
nonfunctional, to the reader. This document provides:

DOS IN CS&E UBDTCE , Davangere Page 6

Library Management System

(a) A description of the environment in which the application is expected to

operate.
(b) A definition of the application’s capabilities.
(c) A specification of the application’s functional and nonfunctional
requirements.

The document is intended to serve several groups of audiences:

 First, it is anticipated that the SRS will be used by the application

designers. Designers will use the information recorded here as the basis
for creating the application’s design.
 Second, the client for the project, the library manager in our case, is
expected to review this document. The SRS will serve to establish a basis
for agreement between the client and development team about the
functionality to be provided by the application.
 Third, the application maintainers will review the document to clarity
their understanding of what the application does.

The purpose of this software development project is to create a new

application called: Library Management System. The Library Management
System will be a desktop application allowing library staff members to
manage the book inventory and user database. The application will provide
the following capabilities:

 The application will be accessible via a computer in the Library. It

will be a standalone application. Library staff will be able to manage
library user accounts including add, delete, and modify.
 Library staff will be able to manage the book inventory database
including add, delete, modify and list.
 Library staff will be able to issue and return books.
 The application will generate reports for administrative purposes.
 The application will provide search function on books based on title,
publisher or author, and search function on students based on name
course and register number.

DOS IN CS&E UBDTCE , Davangere Page 7

Library Management System

4.2 E-R DIAGRAM

USN Library

Name Management

Year System

Branch 1
Username
Receipt no

Date Student Name

*
Validity year 1 1 *
Stores Staff Password

Contact no

Email Security
question
Book can issue

Answers
Category

BorrowDate
2
te

ReturnDate Borrows

Fine

* Book
Accession no
Availability

Book title Column no

Author name Row no

v
Bookselfno
publisher

Department
ISBN
Class number Edition

DOS IN CS&E UBDTCE , Davangere Page 8

Library Management System

4.3 SEQUENCE DIAGRAMS

4.3.1 ADD STUDENT/BOOK

User LMS Database

Click add book/student

Show add book/student form

Fill book/student form Verify data and store in database

Display status Show store status

DESCRIPTION

When user clicks on add book/student menu item/tool then LMS will gives
internal frame of the addBook module. Then he will fill the information of the book then
those all information will be verified and stored in the database. After he got a dialog box
and it will show status of entered data.

DOS IN CS&E UBDTCE , Davangere Page 9

Library Management System

4.3.2 LIST BOOKS/STUDENT

User LMS LM Database

Click list books/student Fetch book/student data

Display data Send book/student data

DESCRIPTION

When user clicks on the list books/student menu item/tools. Then LMS will fetch
the book/student data, database will send that stored data to the LMS software that will be
display the stored book/student data.

DOS IN CS&E UBDTCE , Davangere Page 10

Library Management System

4.3.3 BORROW BOOK

User LMS Database

Click borrow book

Display borrow book form

Enter BookNo and Verify and save borrow

RegNo,Click Borrow details in database

Display status send status

DESCRIPTION

When user clicks on the borrow book menu item/tool then LMS will display the
internal frame for entering the information of the BookNo ,RegNo and finally click on
borrow button. LMS will be verify the save data for borrowing book to student in
database. After verifying saved data, database send the status to the LMS it will display
status to the user.

DOS IN CS&E UBDTCE , Davangere Page 11

Library Management System

4.3.4 RETURN BOOK

User LMS Database

Click return book

Show return book form

Enter bookNo,RegisterNo,
and click ok Verify and calculate fine

Display fine Show status and fine details

DESCRIPTION

When user clicks the return book menu item/tool, LMS will show the returnBook
internal frame for entering the information of the bookNo, RegNo, fine per day and
finally click return button, database will calculate the fine and it will send a status and
fine details to LMS software. LMS will display the fine of the student.

DOS IN CS&E UBDTCE , Davangere Page 12

Library Management System

4.3.5 SEARCH

User LMS Database

Click search button

Display search form

Select search criteria and enter search string Fetch data based on search string

Display search status Send search result to system

DESCRIPTION

When user clicks on the Search menu item/tool, then LMS will display the search
internal frame then user can able to select search criteria and enter search string. Database
will search data based on searching string then it return search result to the LMS software,
software can display the searched result list.

DOS IN CS&E UBDTCE , Davangere Page 13

Library Management System

4.3.6 EDIT

User LMS Database

Click edit menu option

Display edit form

Enter BookNo/RegNo Fetch details of Book/Student

Display edit form with pre-filled data S Send data to LMS

Make changes to data and click save Save data to the database

Display status Send status

DESCRIPTION

When user clicks on the edit menu item, LMS will display edit internal frame for
entering the BookNo/RegNo and modifying the student/book details. Database will fetch
the details of book/student and send it to the LMS software, LMS will display the edit
form with pre-filled data, here user can able to make changes the data and save edit data
by clicking Save button. After clicking save button it will update the data in database, and
saved status will be displayed to user.

DOS IN CS&E UBDTCE , Davangere Page 14

Library Management System

4.4 USE CASE DAIGRAM

Add /Delete/Modify the

Book/Student Details

List Book/Student

Search Book/Student

Issue /Return Book

Add/and list Staff Details

Library Staff

LMS

DOS IN CS&E UBDTCE , Davangere Page 15

Library Management System

Search Books

List borrowed Books/Late

fee

List Borrowed History

List the Return History

Library Student

LMS

DOS IN CS&E UBDTCE , Davangere Page 16

Library Management System

CHAPTER 5

TECHNOLOGY USED

5.1 JAVA SWING

The Library Management System is developed using the Java Swing API. Swing
is based on MVC Design pattern. A design pattern is a way of designing code that
benefits from experience of other developers. Design patterns are rules of thumb and
best practices. Swing components are designed as Model View Controller
components. It means separating the implementation of an application into layers or
components.

 Model – The data structure that represents something like a Book or a

student or a staff
 View- one or more visual representations of that data or object.
 Controller- The user interface logic for manipulating the data.

Swing is a set of classes (part of JFC) that support platform independent

GUI (Graphical User Interface). It is a successor of AWT (Abstract Window
Toolkit), components of which are platform dependent

MVC Model
Encapsulate application states
Respond to state queries
Exposes application functionality
Notifies views of changes


State Query
Change
Notification

View Controller
Render the model Defines application behavior
View Selection Maps user action to model
Request updates from model
Sends user gestures to updates
controller User Gestures
Selects view for response
Allows controller to select view One for each functionality

Method Invocation
Events
DOS IN CS&E UBDTCE , Davangere Page 17
Library Management System

 The swing component class is the view and controller.

 A separate class is the model. Most components come with a default model
 We can set the model to our own model for a control.
 Several controls could share a model.

Swing uses Events to communicate between swing components. An event is just a

method call on the receiving object by the sending object. The method passes the event
object. In swing multiple components or objects can subscribe for a single event.

Some important swing components used in this application are:

 JFrame
 JTabbedPanel
 JMenuBar
 JButton
 JMenuItem
 JComboBox
 JTextField
 JLabel
 JTable
 JPasswordField

5.2 XAMPP

Xampp Control Panel is a computer application used to create and manage

computer-based databases on desktop computers and/or on connected computers.
Mysql can be used for personal information management, in a small business to
organize and manage data. In LMS application, Mysql is used as a back end to store
the data.

DOS IN CS&E UBDTCE , Davangere Page 18

Library Management System

5.3 NetBeans IDE

NetBeans is an open-source project dedicated to providing rock solid software

development products (the NetBeans IDE and the NetBeans Platform) that address
the needs of developers, users and the businesses that rely on NetBeans as a basis for
their products; particularly, to enable them to develop these products quickly,
efficiently and easily by leveraging the strengths of the Java platform and other
relevant industry standards.

An IDE is much more than a text editor. The NetBeans Editor indents lines,
matches words and brackets, and highlights source code syntactically and
semantically. It lets you easily refractor code, with a range of handy and powerful
tools, while it also provides code templates, coding tips, and code generators. It
automatically takes care of correct spacing and alignment, while supporting in-place
editing, as well. The GUI builder is very easy to use and intuitive. Since the cost of
buggy code increases the longer it remains unfixed, NetBeans provides static
analysis tools, especially integration with the widely used FindBugs tool, for
identifying and fixing common problems in Java code. NetBeans support for
multiple languages for development. It also provides cross platform support with rich
set of community provided plugins.

DOS IN CS&E UBDTCE , Davangere Page 19

Library Management System

CHAPTER 6

SYSTEM IMPLEMENTATION

6.1 APPLICATION MODULES

The Library Management System contains following entities and modules related to
those entities:
 Book
 Add Book
 List All/Available/Issued Books
 Edit a Book
 Delete a Book
 Search Book
 Generate Book report
 Student
 Add Student
 List All Students
 Edit a Student
 Delete a Student
 Search Student
 Add Staff
 Borrow/Return
 Borrow a Book
 Return a Book
 List Books Borrowed by a Student
 List Books Returned by a Student
 Search Book
 Search Book by Name/AccessionNo/Department/ISBN
 Search Student
 Search Student by USN/Name/Department/Year

DOS IN CS&E UBDTCE , Davangere Page 20

Library Management System

Based on the type of task being performed, we can re classify these

modules into six basic functionalities:

 Adding data to the database: In this module a new data is added to the
database by getting the information from the user through forms containing
text fields. User enters the information about the book, student or staff and
the new information will be added to the database after making the necessary
checks.
 Fetching the data and displaying as a list: In this module the data is fetched
from the database based on the menu selected. For example, user can select
list all books, list issued books, list of available books in the library, list of
books borrowed by the students etc. The corresponding data is fetched from
the database through database connection and the obtained ResultSet data is
directly fed to a table model present in the frame. The table model will get the
data as well as metadata of the ResultSet and the data will be displayed as a
scrollable table. The data present in the table is read only.
 Editing the contents of database: In this module the user can edit the data
present in the database. The user might have entered a wrong data by
mistake. This can be rectified by editing the data based on the Book Number
and Register Number. User can delete the data from the tables. We can also
make the student eligible or ineligible based on whether they have taken
admission in the current academic year or not.
 Borrowing and returning the books: In this module the library staff can
issue the books to the student or staff. The borrow details include the book
number, register number of the student, issue date and due date. The books
should be returned on or before the due date. If the book is returned after the
due date, fine will be calculated and displayed so that the fine amount can be
collected from the students.

DOS IN CS&E UBDTCE , Davangere Page 21

Library Management System

6.2 DATABASE STRUCTURE

1.Account:

Field Name Data type Description

Username Varchar Primary key
Name Char ---
Password Varchar ---
Security_question Varchar ---
Answer Varchar ---

2.Book:

Field Name Data type Description

ID Int Primary key
AccessionNo Int ---
Booktitle Char ---
Author Char ---
Publisher Varchar ---
ISBN Bigint ---
ClassNO Float ---
Edition Int ---
Department Char ---
BookselNo Varchar ---
RowNo Int ---
ColumnNo Int ---
Availability Char ---

DOS IN CS&E UBDTCE , Davangere Page 22

Library Management System

3.Borrow:

Field Name Data type Description

ID Int Primary key
USN Varchar ---
Name Char ---
AccessionNo Int ---
ISBN Bigint ---
Year Varchar ---
Department Char ---
BookTitle Char ---
Edition Int ---
BorrowDate Date ---
ReturnDate Date ---

4.Return details:

Field Name Data type Description

USN Varchar ---
AccessionNo Int ---
ISBN Date ---
BorrowDate Date ---
ReturnDate Date ---
DateofSubmission Date ---
Latefee Int ---

DOS IN CS&E UBDTCE , Davangere Page 23

Library Management System

5.StudentBorrow:

Field Name Data type Description

USN Varchar ---
Name Char ---
AccessionNo Int ---
ISBN Bigint ---
Year Varchar ---
Department Char ---
BookTitle Varchar ---
Edition Int ---
Borrowdate Date ---
Returndate Date ---

6.StudentReturn:

Field Name Data type Description

USN Varchar ---
AccessionNo Int ---
ISBN Bigint ---
Borrowdate Date ---
Returndate Date ---
DateOfSubmission Date ---
Latefee Int ---

DOS IN CS&E UBDTCE , Davangere Page 24

Library Management System

7.StudentData:

Field Name Data type Description

USN Varchar ---
Email Varchar ---
Password Varchar ---

8.StudentReg:

Field Name Data type Description

USN Varchar ---
Name Char ---
Year Varchar ---
Branch Char ---
ReceiptNo Int ---
Date Date ---
ValidityYear Varchar ---
ContactNo Bigint ---
Email Varchar ---
Category Varchar ---
BookCanIssue Int ---

DOS IN CS&E UBDTCE , Davangere Page 25

Library Management System

6.3 DATABASE CONNECTION

For connecting the LMS application to the Mysql Database, an open

source library called Mysql JDBC Driver is used. It is a jar file that contains
several classes to create a database, to obtain the connection to the database and
closing the database connection. The Mysql JDBC Driver.jar files needs to be
included in the project to make its classes available to the LMS classes.. For
obtaining the connection to the database, the following code snippet is used:

public class javaConnect {

Connection conn;
public static Connection ConnecrDb(){
try{

Class.forName("com.mysql.jdbc.Driver");
Connection
conn=DriverManager.getConnection("jdbc:mysql://localhost:3306/librarynew?z
eroDateTimeBehavior=convertToNull","root","");
return conn;
}catch(Exception e){
JOptionPane.showMessageDialog(null, e);
return null;
}
}

DOS IN CS&E UBDTCE , Davangere Page 26

Library Management System

CHAPTER 7

TESTING
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. Preparation of
the test data plays a vital role in the system testing. After preparation the test data,
the system under study is tested with those test data. Errors are found and
corrected by using the following testing steps and corrections are recorded for
future references. Thus, series of testing steps is performed on the system before it
is ready for implementation.

7.1 RESULTS OF UNIT TESTING

LOGIN FORM:

SL No Test Case Expected Result Test Result

1 Enter valid password Software should display main Successful

and click ok window.
2 Enter invalid password Software should not display Successful
main window.

ADD BOOK FORM:

SL No Test Case Expected Result Test Result

The user have to fill all fields
with proper data, if any error

1 On the click of Insert is found then it gives proper Successful

Information Button. message otherwise Adds
Record to the database.
2 On the click of Insert If the entered book already
Information Button exists, error message is Successful
displayed.

DOS IN CS&E UBDTCE , Davangere Page 27

Library Management System

SEARCH BOOKS AND STUDENTS FORM:

SL No Test Case Expected Result Test Result

User selects Search The Search result should be
1 criteria, enters the displayed which matches the Successful
search string and clicks search criteria..
Search button.

BORROW BOOK:

SL No Test Case Expected Result Test Result

User enters the book The software should check
1 number and register whether book is available or not Successful
number of the student. and whether the student has
reached the limit of borrowing
books.
2 User enters a book Error message should be
which is already issued. displayed that the book is not Successful
available.
3 User enters a register Error message should be
number of the student displayed that the student Successful
who has already cannot borrow another book.
borrowed his/her
maximum no. of books
he/she can borrow

DOS IN CS&E UBDTCE , Davangere Page 28

Library Management System

RETURN BOOK:

SL No Test Case Expected Result Test Result

User enters the book The software should check

1 number and register whether Successful
number of the student. Particular student has
borrowed the entered book or
not ,and appropriate fine
amount should be displayed.
3 User enters the USN No Result should be
which has already displayed for that student Successful
returned all books

DOS IN CS&E UBDTCE , Davangere Page 29

Library Management System

CHAPTER 8

INPUT OUTPUT SCREENS

8.1STAFF SIDE

8.1.1Login

8.1.2 HOMEPAGE(Staff)

DOS IN CS&E UBDTCE , Davangere Page 30

Library Management System

8.1.3 Add Book

8.1.4 EDIT BOOK

DOS IN CS&E UBDTCE , Davangere Page 31

Library Management System

8.1.5 ADD STUDENT

8.1.6 EDIT STUDENT

DOS IN CS&E UBDTCE , Davangere Page 32

Library Management System

8.1.7 LIST ALL BOOKS

8.1.8 LIST OF ALL STUDENTS

DOS IN CS&E UBDTCE , Davangere Page 33

Library Management System

8.1.9 BORROW BOOK

8.1.10 RETURN BOOK

DOS IN CS&E UBDTCE , Davangere Page 34

Library Management System

8.1.11 BORROW LIST

8.1.12 RETURN LIST LIST

DOS IN CS&E UBDTCE , Davangere Page 35

Library Management System

8.1.13 SEARCH BOOK

8.1.14 SEARCH STUDENT

DOS IN CS&E UBDTCE , Davangere Page 36

Library Management System

8.2 STUDENT SIDE

8.2.1 LOGIN

8.2.2 STUDENT DETAILS

DOS IN CS&E UBDTCE , Davangere Page 37

Library Management System

8.2.3 SEARCH BOOK

8.2.4 HISTORY

DOS IN CS&E UBDTCE , Davangere Page 38

Library Management System

CHAPTER 9

LIMITATIONS AND FUTURE ENHANCEMENTS

9.1 LIMITATIONS

 Library Management system is a standalone application, designed for use on a

single machine.
 The software will be installed in a windows system and database will also be
created on that machine .Hence use of this software on multiple systems will
lead to data redundancy and confusion among the library staff.
 This software cannot be used in networked environment.

9.2 FUTURE ENHANCEMENTS

 LMS Software can be enhanced to work in a networked environment in which

database can be stored in a single system and multiple LMS applications running
on different machines can access this database.
 Several new features can be added such as generating reminders for defaulters at
the time of opening the application, barcode reading for adding the books etc.
 Currently only library staff can use the application for internal use. It can be
enhanced to support student login to search the books.

DOS IN CS&E UBDTCE , Davangere Page 39

Library Management System

CHAPTER 10

CONCLUSION
After we have completed the project we are sure the problems in the existing
system would overcome. The “LIBRARY MANAGEMENT SYSTEM” process made
computerized to reduce human errors and to increase the efficiency. The main focus of
this project is to lessen human efforts. The maintenance of the records is made efficient,
as all the records are stored in the ACCESS database, through which data can be retrieved
easily. The navigation control is provided in all the forms to navigate through the large
amount of records. If the numbers of records are very large then user has to just type in
the search string and user gets the results immediately. The editing is also made simpler.
The user has to just type in the required field and press the update button to update the
desired field.

The Books and Students are given a particular unique id no. So that they can be
accessed correctly and without errors. Our main aim of the project is to get the correct
information about a particular student and books available in the library.

The problems, which existed in the earlier system, have been removed to a large
extent. And it is expected that this project will go a long way in satisfying user’s
requirements. The computerization of the Library Management will not only improves the
efficiency but will also reduce human stress thereby indirectly improving human
recourses.

DOS IN CS&E UBDTCE , Davangere Page 40

Library Management System

CHAPTER 11

REFERENCES

OPEN SOURCE LIBRARIES:

1. JTattoo-1.6.10.jar: JTattoo consists of several different Look and Feels for Swing
applications- http://www.jtattoo.net

BOOKS
1.Java Swing,2nd Edition By Marc Loy,Robert Eckstein,O Reilly Media

2 Java The complete Reference,8th Edition By Herbert Schildt,McGraw Hill

WEBSITES
1 http://www.oreilly.com/catalog/jswing2/

2 https://docs.oracle.com

3 http://www.stackoverflow.com

DOS IN CS&E UBDTCE , Davangere Page 41