MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

NIT’S LATE ANNASAHEB PATIL POLYTECHNIC,

NASHIK

MICRO PROJECT
Academic year: 2024-25

TITLE OF PROJECT
E-R Diagram of Library Management System

Program: Computer Engineering

Program code: CO
Course: Database Management System

Course code: 313302

 MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Certificate
This is to certify that Mr. /Ms.
of FOURTH Semester of Diploma in Computer Engineering of Institute Guru Gobind Singh Polytechnic, Nasik
(Institute Code: 1479) has completed the Micro Project satisfactorily in Subject Database Management
System (313302) for the academic year 2024-25 as prescribed in the curriculum.

Sr. No Enrollment No. Exam Seat No.

Place: Date:

Subject Teacher Head of the Dept. Principal

 MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION
NIT’S LATE ANNASAHEB PATIL POLYTECHNIC,
NASHIK

MICRO PROJECT
Academic year: 2024-25

TITLE OF PROJECT

E-R Diagram of Library Management System

Program: Computer Engineering

Program code: CO
Course: Database Management System
Course Code: 313302

Group Details:

Sr. No Name of group members Roll No. Enrollment No. Seat No.

Name of Guide:
 ANNEXURE II

Evaluation Sheet for the Micro Project

Academic Year: 2024-25 Name of the Faculty:

Course: Course code: Semester:
Title of the project: E-R Diagram of Library Management System.

COS addressed by Micro Project:

• CO1 - Apply number system and codes concept to interprete working of digital systems.
• CO2 - Apply Boolean laws to minimize complex Boolean function.
• CO3 - Develop combinational logic circuits for given applications.
• CO4 - Develop sequential logic circuits using Flip-flops.
• CO5 - Interpret the functions of data converters and memories in digital electronic systems.

Comments/Suggestions about team work /leadership/inter-personal communication (if any)

Marks out of Marks out of

15for 10for
Roll No Student Name performance performance in Total out of 25
in oral/ presentation
group activity (D5 Col.9)
(D5 Col.8)

(Name & Signature of Faculty)

 INDEX
1. Introduction.
2. E-R Diagram.
3. Explanation.
4. Conclusion
 INTRODUCTION
This ER diagram represents the flow and relationships in a Library
Management System. It captures the interactions between key
entities such as USER, ADMIN, BOOK, and BOOK RECORD,
which are involved in the borrowing and management of books
within the library.
• The USER entity contains attributes like Name, Branch, Mobile
number, and Library ID. Users borrow books from the library,
and the system tracks the number of books issued to them.

• The BOOK entity includes attributes like Title, Author, Book

Barcode Number, and Status, providing details about the books
in the library.

• The ADMIN entity represents administrators who manage book

records and have credentials like Login ID and Admin ID. They
maintain the book inventory by adding, updating, or deleting
records in the BOOK RECORD entity, which tracks the total
number of available books.
This ER diagram shows the process flow from a user logging in,
borrowing a book, and the admin overseeing the management of
book records. It represents the structure and functionality of a
typical library management system, making it efficient for managing
book lending and return processes.
E-R DIAGRAM
 EXPLANATION
The ER diagram outlines the architecture and processes involved in a
Library Management System, showcasing how different entities interact
and work together for smooth library operations. Below is a detailed
explanation of the diagram:
Key Entities and Relationships:
1. USER:
a. Attributes:
i. Name, Branch, Mobile number, Address: These attributes capture
the personal and academic details of the user.
ii. Library ID: Unique identifier assigned to each user to manage their
book transactions.
iii. No. of Books Issued: Tracks how many books a user has borrowed.
b. Actions:
i. A user has to login using their credentials (via LOGIN entity) and
can borrow books from the library.
2. LOGIN:
a. Attributes:
i. Login ID, Password: Required credentials for users and admins to
access the system.
b. Relationship:
i. Users must login to interact with the system.
ii. Admins also need to log in to manage records.
3. BOOK:
a. Attributes:
i. Title, Author, Book Barcode Number, Place: Basic details of the
book, such as title, author, barcode, and location in the library.
ii. Status: Indicates whether the book is currently issued or available.
b. Actions:
i. The book can be borrowed by the user.
ii. The book's issuance is managed by the admin.
4. ADMIN:
a. Attributes:
 i. Admin ID, Name, Phone number: Admin’s identity and contact
details.
b. Actions:
i. Admin is responsible for overseeing the Book Record entity and
managing books in the system.
ii. The admin maintains book records and can update, add, or delete
books from the system.
5. BOOK RECORD:
a. Attributes:
i. Total Books Available: Number of books currently present in the
library.
b. Actions:
i. Admin can update, add, or delete records of books as needed,
keeping the book inventory up to date.
Process Flow:
• User Interaction:

o A user logs into the system using their Login ID and Password.

o They can borrow books, which are tracked by the system, including

details like the No of Books Issued and the Library ID.

• Admin Role:

o Admin logs into the system using the Admin ID.

o Admin maintains the BOOK RECORD, including adding new

records when books are added to the library, updating existing ones,
and deleting records for books no longer in circulation.
o Admin also manages the book issuance process and can approve or

track which user borrowed which book.

• Book Borrowing:

o A user can borrow a book based on their Library ID.

o The system tracks the book’s status and the details of the book

issued, such as Title, Author, and Barcode Number.

o The admin oversees this transaction.
 CONCLUSION
The ER diagram effectively models the interactions within a Library
Management System, ensuring streamlined and organized
operations. By defining relationships between key entities like
USER, ADMIN, BOOK, and BOOK RECORD, the system can
efficiently handle tasks such as book issuance, user management,
and record maintenance. Users can easily borrow books, while
admins have the ability to manage the library’s inventory, keeping
track of available books and updating records as needed. This
diagram provides a clear visual representation of the system’s
structure, ensuring a smooth flow of operations in the library,
enhancing both user experience and administrative efficiency.