Introduction of Library Management System

Draw Use Case Diagram Online
Library Management System Uml Diagrams
Use Case Diagram For Library Management System Using Rfid
Use Case Diagram For Video Library Management System
Use Case Diagram For Online Library Management System
Types Of Use Case Diagrams

Library Management System INTRODUCTION We are trying to develop an automation system which will provide lots of facilities to our University. The total automation system divided into many modules, here our parts is “Library Management System”.This is a small part of total automation System but The Library Management System will provide an environment which facilitate teachers & students. This Use Case Diagram is a graphic depiction of the interactions among the elements of Music Library Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Music Library Management System. This tutorial is regarding the development of usecase diagram for the library management system.-Please watch: 'Artificial Intelligence Learn.

Are you looking for a Library management system project? We are here to help you. You can contact us. The 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 to provide an easy to handle and automated library management system. This project also provides features and an interface for maintaining librarian’s records, student’s history of issues, 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 purposes 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 the 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 to the library.

You can also check these posts:

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 teacher’s login. Also, on top of all this, there is an admin who will be managing the entire application’s authorization and authentication, not no intruder can log in and modify the data, as a login for admin is also available.

Draw Use Case Diagram Online

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:

Library Management System Uml Diagrams

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 a 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, which means record the availability at a regular time interval.

Use Case Diagram For Library Management System Using Rfid

Librarian:

Playstation eye pc. 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

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 becomes 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 the 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 divisions 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 more specialties 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: