java library synopsis

Page : 1/40

LIBRARY MANAGEMENT SYSTEM

byKARAN SINGHAL

Submitted to the department ofComputer Science and Engineering

In partial fulfilment of the requirementsFor the degree of

Bachelor of Technologyin

Computer Science and Engineering

RAJ KUMAR GOEL INSTITUTE OF TECHNOLOGY

A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY

MARCH, 2016

Page : 2/40

Declaration

I declare that this project entitled “Library Management System” done at Raj Kumar Goel Institute Of Technology,Ghaziabad is a record of project work submitted by me for the partial fulfillment of the Dr. A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY under the supervision and guidance of Mr. Manish Gupta.The Project is genuine and not a reproduction of any project previously done or submitted.

- Karan Singhal1203310087

Acknowledgement

Page : 3/40

I extend my sincere thanks to our faculties which provided me with the opportunity to fulfill my wish and achieve my goal.I would like to express deep debt to Mr. Manish Gupta, project guide for his vital suggestions, meticulous guidance and constant motivation which went a long way in the successful completion of this project.On a moral personal note, my deepest appreciation and gratitude to my beloved parents, who have been an inspiration and have provided me with unrelenting encouragement and support.

-   Karan Singhal

CERTIFICATE

Page : 4/40

This is to certify that the Dissertation entitled, Library Management is a bonafide work done by KaranSinghal,Chitransh Ahuja,Shubham Rathi,Prashant Kumar of B-Tech (Computer Science andEngineering) during the academic session 2015-2016 has been carried out under my direct supervision and guidance. This report or a similar report on the topic has not been submitted for any other examination and does not form a part of any other course undergone by the candidate.

________________Signature of Faculty

(Mr. Manish Gupta)

Table of Contents

Page : 5/40

CHAPTER 11.1 ABSTARCT...............................................................7

1.1.1 Scope and Features...................................................81.1.2 Master and Security module....................................81.1.3 Transaction module.................................................9

1.1.4 Drawbacks of Present System..................................101.1.5 Proposed System.....................................................101.1.6 Out of Scope............................................................111.1.7 Goal and objective...................................................121.1.8 Solution Concept......................................................12

1.2 PROBLEM STATEMENT.......................................131.2.1 Requirements Summary..........................................13

1.2.2 Business Requirements.........................................131.2.3 User Requirements................................................131.2.4 Operational Requirements.....................................14

CHAPTER 22.1 SYSTEM ARCHITECTURE....................................15

2.1.1 High Level Solution Architecture..............................152.1.2 Data Flow and Process Flow Chart...........................16..........................................................................................162.1.3 User Profiles.............................................................172.1.4 Usage Summary.......................................................18

2.2 SOFTWARE AND HARDWARE REQUIREMENT.......192.2.1 General Requirement for Server/Client:................19

CHAPTER 33.1 DEVELOPMENT TOOLS AND TECHNOLOGIES.......193.2 DEVELOPMENT TOOLS AND TECHNOLOGIES.......20

3.2.1 Front End..................................................................203.2.2 Back End..................................................................203.2.3 Development Environment......................................21

3.3 DESIGN GOALS AND CONSTRAINTS....................22CHAPTER 44.1 LIBRARY MANAGEMENT SYSTEM DATA DICTIONARY...........................................................23

Page : 6/40

4.1.1. EmployeeMaster...................................................234.1.2. MemberMaster.....................................................244.1.3. AreaMaster...........................................................254.1.4. Category...............................................................254.1.5. BookMaster...........................................................254.1.6. LibaryCardMaster.................................................274.1.7. PublisherMaster....................................................284.1.8. UserMaster...........................................................284.1.9. Transcation...........................................................29

4.2 LIBRARY MANAGEMENT SYSTEM– DATA SCHEMA ER DIAGRAM..........................................................304.3 ELIBRARY ER DIAGRAM.....................................314.4 ELIBRARY DFD (DATA FLOW DIAGRAM)..............314.5 ELIBRARY DFD (DATA FLOW DIAGRAM)..............32

4.5.1 Context Level DFD...................................................324.5.2 0 LEVEL DATA FLOW DIAGRAM...................324.6 PLANNING AND SCHEDULING.............................34

4.6.1 Planning...................................................................344.6.2 Gantt chart:..............................................................354.6.3 PERT chart:...............................................................36

CHAPTER 55.1 CONCLUSION AND FUTURE ENHANCEMENT.........37BIBLIOGRAPHY.......................................................38

Websites...........................................................................38Books................................................................................38

Page : 7/40

ABSTARCT

Today most of the library is using either manual system for tracking the day to day activity or they are using desktop, spread sheet like MS Excel application to manage the day to day activity. In this proposed Library Management System it will run in client server mode and user can check the book availability, they can search the books, library staff can issue, receive book, and management can check the report. System will store historical data. Management can anytime view the total book status, library card status.

Page : 8/40

Scope and FeaturesThe Library Management System is designed & developed for a receipt and issuance of books in the library along with the student’s details. The books received in the library are entered in Books Entry form and the new student is entered in the student entry form. When the student wants to get the desired book the same is issued on the availability basis to the student. The issuance and due date for the returning of the book is also entered into the Book Issue form under third menu Book Issue. The student has to pay the fine if any on the basis of no. of days delayed deposit of the book in the library. Any education institute can make use of it for providing information about author, content of the available books. It can be used in offices and modifications can be easily done according to requirementsFrom an end-user perspective, the Library Management System Project consists of two functional elements: Master and Transaction Module.

Page : 9/40

Master and Security moduleMaster and security module includes user security management, login security, book details, member master, library card, library transaction.

Login – Check the user by user name and password, All user needs to enter user name and password to access the system, system check the user name and password and give access the system resource only valid user.

Main Screen – It display available options, menus and toolbars to the logged user. System display option as per user rights. It also show the name of user currently logged in.

Page : 10/40

Transaction moduleTransaction module includes issuing, receiving book and transaction report.

Issuing Book – This form used to issue book to the member. In this screen user selects book id, and library card id, system display the book and card history. If book is already issued it display message and details of last issued details. Same way system display card history for the library card no, if book already available it shows the message. If book is available and there is no book pending for received then book is issued and system saves the details. System also has powerful search facility to find the book and member id.

Page : 11/40

Drawbacks of Present System

Some of the problems being faced in manual system are as follows: 1. Fast report generation is not possible.

Proposed System

There will be three major components: 1. Stock maintenance.2. Transaction entry.3. Reports.

Proposed system provides with following solutions: 1. It provides "better and efficient" service to members.

Page : 12/40

Out of ScopeThe following functions are considered out of scope for Version 1 of the Library Management System. Versions 2.0 address items not in scope and those are not feasible during V1.0. Function

Comment Version

Linking and integration of any legacy system for accounting.

Required by management to control and maintain the accounting activity

2

Page : 13/40

Goal and objective

This section presents a conceptual overview of the solution, and then provides an introduction to its requirements.

Solution Concept

The Library Management System consists of:

Master and Security Module: Master and Security module includes user security management, login security, book master, publisher master, member master, library card, general settings.

Transaction Module: Transaction module includes forms to issue, receive books and display the library transaction details.

Page : 14/40

Problem Statement

Requirements SummaryThe following preliminary lists are based on initial interviewsBusiness RequirementsThe business goal for the application is to support an increase the productivity and complete automation of existing manual or semi automatic library management process. Business requirements are discussed in the Scope section, with the following additional detail:

User RequirementsUser requirements are categorized by user type.

System Users Able to search and view the member details. Able to find all the information like book details, book

and library card transaction details in one screen to give answer to member query.

Supervisor

Update book and member details. Modify library card details if required.

Page : 15/40

Operational RequirementsThe following requirements provide a high-level view of how the system will run:

Processor usage should not exceed 80 percent during concurrent uses.

Backups will occur incrementally throughout the day. A full weekly backup is required to WORM drives. Ensure that information is easy to access either, and

meaningful for the system users and the company. Minimize the technical knowledge that systems users

need to access the

Page : 16/40

System Architecture

High Level Solution Architecture

High Level Solution Architecture of online Library Management System

Page : 17/40

Data Flow and Process Flow Chart

Page : 18/40

User ProfilesThe following user types are expected for the Library Management System:

Page : 19/40

Usage SummaryLibrary Management System Version 1.0 will address the following use cases. The complete usage scenarios will be completed during the information-gathering process. Use cases will be created and prioritized. Selected use cases will be expanded into usage scenarios and features that are derived from both use cases and the usage scenarios, as represented in the following diagram:

Usage summary use case

Page : 20/40

Software and Hardware Requirement

General Requirement for Server/Client:

Type Software HardwareWork Station/ Node

1. Windows XP2. JAVA

1. P-4 2. RAM -256 MB

Database Server

MySQL 1.P-42.RAM- 2GB3.Hard Disk-160GB4.RAID

Application Server

1.Win 2000 Advance Server

1.P-42.RAM- 1GB3.Hard Disk-40GB

Application ServerData Base Server

Workstation 1 Workstation 2 Workstation 3 Workstation N

Page : 21/40

Development Tools and Technologies

Front End

1. JAVA

Why Java?

Back End MySQL

Why MySQL?

Page : 22/40

Development Environment1. NetBean2. MySQL Query Browser

Page : 23/40

Design Goals and Constraints

Page : 24/40

Library Management System Data Dictionary

1. EmployeeMaster

Sr.

Field Name Type Primary Key

Foreign Key

1 E_Id Number Y2 E_Sname Text(50)3 E_Name Text(50)4 E_Fname Text(50)5 E_Religion Text(50)6 E_Caste Text(50)7 E_Nationality Text(50)

Page : 25/40

2. MemberMaster

Sr.

Field Name Type Primary Key

Foreign Key

1 HolderID Number Y2 Dor Date/Time3 Title Text

Page : 26/40

3. AreaMaster

Sr.

Field Name Type Primary Key

Foreign Key

1 Area Text Y

4. Category

Sr.

Field Name Type Primary Key

Foreign Key

1 Category Text Y

5. BookMaster

Sr.

Field Name Type Primary Key

Foreign Key

1 BookId Number Y2 Title Text3 PublishYear Number

Page : 27/40

Page : 28/40

6. LibaryCardMaster

Sr.

Field Name Type Primary Key

Foreign Key

1 LibID Number Y2 HolderType Text

Page : 29/40

7. PublisherMaster

Sr.

Field Name Type Primary Key

Foreign Key

1 PubID Number Y2 CompanyName Text

8. UserMaster

Sr.

Field Name Type Primary Key

Foreign Key

1 UM_Name Number Y

Page : 30/40

9. Transcation

Sr.

Field Name Type Primary Key

Foreign Key

1 TrnNo Number Y2 Type Text

Page : 31/40

Library Management System– Data Schema ER Diagram

Page : 32/40

eLibrary ER Diagram

Page : 33/40

eLibrary DFD (Data Flow Diagram)

Context Level DFD

Context Flow Diagrams give us the complete details about the inputs and outputs for a given system.

0 Level Data Flow Diagram

USER

eLibrary

Login

Accesses

View Transcation

DBMS

Page : 34/40

1 Level Data Flow Diagram

Page : 35/40

Planning and Scheduling

PlanningPlanning is very important in every aspect of development work. Software project plan indicated scope of the project, milestones and deliverables, project estimates, resource allocation, risk management, scheduling techniques and quality control and standard. Software project plan can be viewed as the following:

Page : 36/40

Gantt chart:

Page : 37/40

PERT chart:

Page : 38/40

Conclusion and future enhancement

This project was developed to fulfill user and business requirement; however there are lots of scopes to improve the performance of the Library Management System in the area of user interface, database performance, and query processing time. Etc.

So there are many things for future enhancement of this project. The future enhancements that are possible in the project are as follows.

Linking and integration of any legacy system for accounting.

Integration with bank database through Web Services Connection to third-party OLAP applications Implement Bar code reader Web interface for members In the area of data security and system security. Provide more online tips and help. To optimize the query which is embedded in the

system.

Page : 39/40

Bibliography

Websites

http://www.google.com http://www.microsoft.com http://www.programmer2programmer.net http://www.codeproject.com http://www.msdn.com. http://www.vb123.com http://www.vbcode.com http://www.sqltuner.com

Books

Mastering Visual Basic 6 (Paperback) Mastering Visual Basic .NET (Paperback) Visual Basic Black Book (Paperback) SQL Bible, 2nd Edition (Paperback) Database Development in Visual Basic

Page : 40/40

You can get complete synopsis, project report with all diagrams, project source code, MySQL database script and installation

guide of

JAVA MySQL Library System only INR Rs. 2000/-

You can buy online athttp://www.readymadeproject.com/quickPay.aspx

For project demo and details please check project no 75http://www.readymadeproject.com/aj/academic_project_list.htm

For further details please contact atEmail ajprofessionals@gmail.com or info@redaymadeproject.com or

call +91-9920329254