This document describes a library management system created by students to manage a library more efficiently than a manual system. It outlines the existing manual system and proposed computerized system. The computerized system would allow for automated tracking of books, user registration, searching for books, and generating reports. It would also make transactions like issuing and returning books much quicker. The document provides details on the system requirements, modules, UML diagrams, and system specifications to outline how the library management system would work.

1. LIBRARY MANAGEMENT SYSTEM
S.K. MAHABOOB BASHA(13KA1A0520),
B.YESWANTH AKHIL(13KA1A0525),
K.KAMALAKAR(13KA1A0530).
Under the esteemed Guidance of
Dr. B. ESWARA REDDY M.Tech, Ph.D
PROFESSOR
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
JNTUA COLLEGE OF ENGINEERING KALIKIRI-517234

2. Introduction
Existing System
Proposed System
System Requirements
Modules
UML Diagrams
System Specifications
Reference
CONTENTS

3. INTRODUCTION
A library management system, also known as an automated
library system, it is software that has been developed to
handle basic housekeeping functions of a library.
It’s a well organized software solution for a library.
It help to provide information on any book present in library to
the user as well as staff member.
It keeps a track of book issued, returned and added to library.

4. EXISTING SYSTEM
Manages all library information across ledgers and files.
All data related to books, borrowers and librarians is done
manually conventional manner.
Not effective and lead to mismanagement of data.
Difficult for a user to check availability of book and to make
reservations.

5. DISADVANTAGES
All the Transactions of Books are done manually.
Time taken for all transactions of library is more
Human efforts are more

6. PROPOSED SYSTEM
Computerized
Database Maintenance
Transaction Entry
Reports

7. ADVANTAGES
Automated Library Management System
Transactions of Library done quickly
All the manual difficulties in managing the Library has been
rectified
User friendly interface
Fast access to database

8. SYSTEM REQUIREMENTS
Non Functional Requirements
Efficiency Requirement: Easily access library
Reliability Requirement: Accurately performance
Usability Requirement: User friendly environment
Implementation Requirement: Front End:- Java(JSP),
Server:- Apache Tomcat 7.0,
Back End:- My Sql 6.0

9. Functional Requirements
User Login
Register New User
Register New Book
Search Book
Generate Reports
Issue & Return Books

10. MODULES
Registration Module
Librarian Module
Student Module
Faculty Module

11. Registration Module
Used for Register newly
Displays Credential Form must contain Email ID
and Phone
Get Popup message “ U Successfully Registered”

12. Librarian Module
Have Unique ID and Password
Can Access Entire System(Administrator)
Can Add Books, Journals, Magazines
Can Delete Books, Journals, Magazines
Perform Transactions

13. Faculty Module
Log In
Search For a Book
View Book Detail
Know Availability of Book
Know due date of borrowed book

14. Student Module
Log In
Search For a Book
View Book Detail
Know Availability of Book
Know due date of borrowed book

15. UML DIAGRAMS
Class Diagram

16. Use Case Diagram
Librarian

17. Use Case Diagram contd..
Faculty

18. Use Case Diagram contd..
Student

19. Activity Diagram
Admin

20. Activity Diagram contd..
Faculty

21. Activity Diagram contd..
Student

22. Sequence Diagram

23. Collaboration Diagram

24. SYSTEM SPECIFICATIONS
Hardware Requirements
Pentium-IV(Processor)
2 GB Ram
Hard disk 50 GB
Software Requirements
Operating System: Windows
Version
Programming language:Java(JSP)
Back-End : My SQL 6.0
IDE: Eclipse
Web Server: Tomcat Server 7.0

25. REFERENCE
Sharma, C. K.; Singh, Kiran (2005), Library
Management, ISBN 978-81-269-0452-5
McClure, C. R. (1980). "LIBRARY MANAGERS:
Can They Manage? Will They Lead?". Library
Journal: 2391.