Database Design for Library Management System - Project Report

This assignment presents a database design for a library management system, focusing on the creation of an Entity-Relationship Diagram (ERD) and the definition of database attributes. The solution outlines the entities such as Books, Publishers, Authors, Students, and Borrow, with their corresponding attributes and primary/foreign keys. The design considers the importance of publisher and author data, and assumes that each book borrowing event creates a single record to reduce data redundancy. The assignment includes a detailed breakdown of table attributes and their roles, along with considerations for data management. The author also provides a bibliography of sources used. The project is a comprehensive guide to designing a relational database for a library, with a focus on practical considerations and data integrity.

Running head: DATABASE DESIGN OF LIBRARY MANAGEMENT SYSTEM
Database Design of Library Management System
Name of the Student
Name of the University
Author’s note:

1DATABASE DESIGN OF LIBRARY MANAGEMENT SYSTEM
Entity and Attributes:
Entity Name: Books
Attribute Names: bookID, bookTitle, isbn, publisherID, volume, shortDesc,
yearOfPublish, cost, availableCopies.
Entity Name: Publishers
Attribute Names: publisherID, publisherName, address, contact, email, fax,
contactPersonName
Entity Name: Authors
Attribute Names: authorID, authorName, contact, address, email, birthYear, shortDesc
Entity Name: BookAuthors
Attribute Names: authorID, bookID, priority
Entity Name: Students
Attribute Names: studentID, studentName, address, contact, email, class
Entity Name: Borrow
Attribute Names: borrowID, studentID, borrowDate, expectedReturnDate,
numberOfBooks, totalFine
Entity Name: BookBorrow
Attribute Names: borrowID, bookID, condition, actualReturnDate, fine
Entity Name: BookReserve

2DATABASE DESIGN OF LIBRARY MANAGEMENT SYSTEM
Attribute Names: reserveID, bookID, studentID, reserveDate, status
Entity Relationship Diagram:
Figure 1: Entity Relationship Diagram
(Source: Created by Author)

3DATABASE DESIGN OF LIBRARY MANAGEMENT SYSTEM
First consideration done for designing the entity relationship diagram was to consider the
importance of publisher and author data within library. The functionalities of library does not
involve use of publisher or author data. However, in real life, these data are extremely important.
Second one was to assume that each time user goes to borrow books, only a single borrow row
will be created. This will reduce redundancy of data. Borrow data and expected return date of all
books that student borrow at a time will be same. However, the different can be seen in return
date. Student may return different books on different dates. As fine will be imposed based on
return date, the fine attribute is placed within individual book borrowing entity. It is also
assumed that if library manager cancels a reservation, the data will not be removed from
database, rather it will be assigned status of cancel.

4DATABASE DESIGN OF LIBRARY MANAGEMENT SYSTEM
Bibliography:
Dunn, C. and Nel, L.D., 2017. Entity Relationship Diagram Mapping.
Yang, L. and Cao, L., 2016. The Effect of MySQL Workbench in Teaching Entity-Relationship
Diagram (ERD) to Relational Schema Mapping. International Journal of Modern Education and
Computer Science, 8(7), p.1.