INTRODUCTION OF LIBRARY MANAGEMENT SYSTEM

Are you looking for Library management system for your final year project? We are here to help you. You can contact us

Library management system is all about organizing, managing the library and library-oriented tasks. It also involves maintaining the database of entering new books and the record of books that have been retrieved or issued, with their respective dates.

The main aim of this project is providing an easy to handle and automated library management system. This project also provides features and interface for maintaining librarian’s records, student’s history of issue and fines.

The owner can easily update, delete and insert data in the database with this project.The following are some of the features provided by this project:

The issue of books by online mode.

Columns provided to search book online.

Requests to the librarian can be sent to provide new books in the column.

Login portal for a student for security purpose of the library.

Homepage for the student which has different buttons to navigate to pages containing the date of issue, date of return, fine charges etc.

Columns for teachers to get book issued if desired.

Requests column for teachers to ask for the introduction of new or essential books in the library.

Maintaining records of the librarian and other library staff.

Feedback page to be viewed and monitored by the college authority, to which student

The teacher can mention any misbehave or feedback for the library.

PROPOSED SYSTEM OF LIBRARY MANAGEMENT SYSTEM

The project Library Management System aims at developing a fully functional computerized system to maintain all the day to day activity of a library

This project has many features which such as the facility of user login and teachers login. Also on the top of all this, there is an admin who will be managing the entire application’s authorization and authentication, not any intruder can login and modify the data, as a login for admin is also available.

The various modules of this system areas:

User Module:

This module is further divided into various sub-modules describing the user in a better way:

New user register:

To sign up a new user to this system

Student Login:

So as to confirm that only an authenticated user is using the project.

Search book:

The user can search book based on book id, book name, or by author name.

Issue Book:

To help the user get the required books issued.

Return Book:

To return the book before the last date without fine, or after the specified time duration with a late fine.

Admin Module:

It is to be operated by the admin with unique id and password. The admin is the person who decides authentication and authorization for all the different users of the application. It further can be subdivided as:

Register user

Issue Book

Maintain books in a stack, means record the availability at regular time interval.

Librarian:

Includes all the library staff who are required to enter the records in the system and keep an eye on the various activities like the issue of the book, the return of the book, non-availability of books etc. through the developed system.

SYSTEM DESIGN OF LIBRARY MANAGEMENT SYSTEM

Hardware requirement of library management system:

Operating system: Windows 7 (or above can be used) since it is stable

Hard disks: 40GB

RAM: 1GB as it will give faster performance throughput.

Software requirement of library management system:

Java language

Net beans IDE 7.0.1 or eclipse neon

MySQL

PhpMyAdmin: As it can also easily handle server-side queries if any as well as compatible with tools for website designing.

ER DIAGRAM OF LIBRARY MANAGEMENT SYSTEM

ER DIAGRAM OF LIBRARY MANAGEMENT SYSTEM

The ER diagram provides the description of all the physical objects involved in the application like the library, books, user etc. It also briefs the operations to be done on these entities. This will minimize all the redundancy and attempt to store all the required information in as small a space as possible. The various entities are described as:

Library:

The main part of the organization for which this application has been designed. It has attributes like:

Name:

The name of the library to distinguish it from all the libraries available in any campus, uniquely.

Address:

This defines the address of the library as such the block number or lane number etc.

Books:

These are the basic building block of this system as well as any library. In other words the main purpose of any library and the cause to develop systems like this.

Book_Name:

The name of the book which is almost unique in some way.

Book_Code:

A number to use for sorting and arranging the book, as well as identifying it in the library.

Author:

The one who has written the book. As sometimes the book’s series become more popular by the author’s name rather than the book name.

Price:

The market value of the book is also required to maintain in the record, as sometimes it is needed to arrange and sort based on this, secondly, it is also required for compensation in case of loss or damage, as fine charges.

Quantity:

This is to indicate the availability of each book individually, so as to know whether last copy should be issued or kept as a reference piece. Also to maintain the number of books.

Rack_No:

To get the exact location of the book, so as it becomes easy to search it and sort it at the time of binding up work.

Subject_Code:

As there are various further division and subcategories of any subject. So, in that case, this is the unique id to distinguish the books, arrange them, and sort them. Like in computer science there are further many specialities like core java, advanced java, HTML, html5 etc.

User:

The next is the beneficiary, by whom the library is being accessed and who serves as a purpose for this system. Its attributes include:

Name:

The name of the student or teacher, who will get the book issued, or who will return the book.

Id:

The user’s unique college or university roll number i.e. the id. The same is applicable to teachers also, with their unique id.

Address:

This refers to the user’s physical area of residence. It is a composite attribute. As it further contains the house number and lane number.

Fine_Amount:

To indicate the amount of fine he/she has to deposit and keep it up to date so that he/she is aware of the payment to be made at the end of the year or session.

Issue Status:

It makes to the notice of the librarian as well as to the student or teacher that ow many books they have already got issued and how much more can they get at the current point of time. It includes attributes as:

Book_Name:

The name of the book which is almost unique in some way.

Book_Code:

A number to use for sorting and arranging the book, as well as identifying it in the library.

Id:

The user’s unique college or university roll number i.e. the id. The same is applicable to teachers also, with their unique id. To know which user has been issued the book and for what time limit, that is what time the user is supposed to return the book, and if not will be charged fine.

Date_Issue:

The date on which user got the book issued to read from it.

Return_Date:

It indicates the date on which user is supposed to be returning the book, that is it is the date after the duration completed for which the user has been issued the book.

Return Status:

This tells the library management authority about the status of returned books per user. Whether a particular user has returned the book or not, on or before the last date. If not, in that case, the fine will be charged from him/her as a penalty for late submission.

Book_Name:

The name of the book which is almost unique in some way.

Book_Code:

A number to use for sorting and arranging the book, as well as identifying it in the library.

Id:

The user’s unique college or university roll number i.e. the id. The same is applicable to teachers also, with their unique id. To know which user has been issued the book and for what time limit, that is what time the user is supposed to return the book, and if not will be charged fine.

Date_Issue:

The date on which user got the book issued to read from it.

Return_Date:

It indicates the date on which user is supposed to be returning the book, that is it is the date after the duration completed for which the user has been issued the book.

USE CASE DIAGRAM OF LIBRARY MANAGEMENT SYSTEM

 

USE CASE DIAGRAM OF LIBRARY MANAGEMENT SYSTEM

Use Case Diagram Description:

The above-mentioned use case diagram depicts the functionality of the library management system in a brief and satisfactory way.

In this diagram, the user has been shown more specifically as a student who will the first login to the system, to get access to the application. After getting the authentication and being authorized, the user will use the system with ease and security.

There is a database maintained for storing the records of books that are available in the stock, books that have been issued to some user, then the return date of each issued book.

After logging in the user will search for the books in the library using the subject code, book code, and therefore access to the rack number becomes easy, so ultimately using the rack number user finds the book, if it is available or not.

Once the book has been found, if wanted the book, the user can get it issued easily with their unique college or university id.

Now since the book has been issued it needs to be returned after a defined duration of time as a part of the system procedure.

At a regular interval of time user can check if there is any fine charged on him/her or not.

The librarian will also monitor all these activities at its end.

And along with this, there is some additional work for the librarian to be done like, adding new books in the rack, updating the book availability status time to time, checking the user’s identity is valid or not for a particular time period.

There may be some cases at times when for example say a student has been suspended due to some disciplinary action and therefore has been blocked from using any service provided by the university normally.

In this case, it becomes the duty of the librarian to check the identity is valid to issue books or not. Also similar is the case when a student has already passed out from the university.

SYSTEM REQUIREMENT OF LIBRARY MANAGEMENT SYSTEM

To show the comprehensive information for the intended purpose and about the system to be developed.

Non-Functional Requirement of library management system

These are those that specify some criteria that can be used to evaluate the performance of a system in some particular conditions.

Efficiency Requirement:

Through this system, the students or teachers and the librarian gets a way to ease their work. Through this system, the student can search and get the book issued easily.

Also, less time will be needed to spend by the librarian to handle this. Therefore the throughput is faster processing of library management system.

Reliability Requirement:

The system does its work with more accuracy like user registration to the system, user validation and authorization, book search and issue operation, return status, and updating the database by synchronizing between database and application.

Usability Requirement:

The proposed library management system provides a user-friendly environment to the users so that the librarians, as well as the students, can utilize the system in an effective manner for ease of work.

Delivery Requirement:

There is always some time duration specified to develop a project. Similarly, this system is expected to be complete within 6 months of time. This launch will be used for improving the performance, as it will be evaluated by the users and then the problems that are occurring with the system will be solved.

System Implementation Requirement:

To develop this system PHP, the server side scripting language has been used along with HTML 5 for designing the system layout. Also, PHP has been used since it is easy and effective for database connectivity. For the backend part which includes the database itself, MySQL has been used.

Functional Requirement of library management system

On the other side, there are those that deal with all type of technical functioning of the system.

Login :

he is to authenticate a user, that is to know whether he or she can get access to the system. At the time of login, the user will be required to enter their user id and password.

If for any user these fields don’t match, then the user will not be allowed to use the system. For this, the user id is stored at the time of registration.

This library managememt system must only allow a user with valid id and password to become the beneficiary.After this authorization takes place, to know what all are the levels a particular user can access to.

Also after finishing the work user must log out of the system to prevent the transaction from any intruder.

User Sign Up:

This is performed when the user is new to the system and wants to become a part, that wants to create a new account. For this system must verify all the user’s information. And also the information must be removed if found invalid or irrelevant.

Adding New book in the library:

This feature is used to add new books to the library by the authority. The system must enter and maintain the number of copies of each individual book.Also, the system must allocate unique id to individual books carefully.

Search operation:

The system must provide the facility of searching books based on their unique identity, the name of the book, author name. There must be some filters available to search with keywords. Some table view of the searches must be available.

Issue and Return book:

This is for issuing and returning books and also maintaining the issue and return status in the database timely. The system must be performing well with storing the issue data into the database. The update number of books feature must be working fine.

Before issuing any book, the system must firstly check for its availability, if it is available in stock or not. Along with issuing the books, the return dates must be shared with the students and must be entered into the database also.

Fine charge:

In case of failure in return on or before the last date, the student will be charged penalty fine, based on the per day rate multiplied by the number of days. The system must update this status time to time.

Also once the fine has been paid, the status must be updated again shortly.

ONLINE LIBRARY MANAGEMENT SYSTEM PROJECT

One add-on feature for this application is the option of providing online notice board, this feature can be used by the librarian for uploading announcements related to an event going on in the university or any book fair which is about to held in the nearby future.

Also, information like the sale of old books can be shared.

Another feature can be adding lecture notes, the teacher can create some lecture notes and upload it in pdf format in the application. So as the students will find the application more interesting and beneficial.

The lecture notes part will play a major role in gaining the popularization for this system.