ENTITY RELATIONSHIP DIAGRAM IN INFORMATION MANAGEMENT

ERD - INFORMATION MANAGMENT

1. Entity – Relationship Diagram

2. Steps in Creating an ER Diagram Understand the Requirements Identify Entities Identify Attributes Determine Relationships Normalize Entities Draw the ER Diagram 2

3. Steps in Creating an ER Diagram Connect Entities with Relationships Refine and Review Validate Against Requirements Iterate if Necessary 3

4. Problem 1: Library System A university library system needs to be designed to manage student borrowing of books. Each student can borrow multiple books, and each book can be borrowed by multiple students. Each book loan has a due date, a return date, and a renewal date. For each book loan, a fine may be incurred, which consists of a fine amount and a status (paid/unpaid). Additionally, the system should calculate and track the total fine accrued by each student. Students are identified by their StudentID , and they have a name, email, and phone number. Books are identified by their ISBN and have attributes including title, author, and publication year. 4

5. Identify the entities, attributes: Student StudentID (PK), Name, Email, PhoneNo BookLoan LoanID (PK), DueDate, ReturnDate , RenewalDate , Fine – FineAmount and FineStatus , TotalFine Book ISBN (PK), Title, Author, PubYear

6. Entity Type, Attribute Type Student (?) StudentID (?) Name (?) Email (?) PhoneNo (?) BookLoan (?) LoanID (?) DueDate (?) ReturnDate (?) RenewalDate (?) Fine (?) FineAmount (?) Status (?) TotalFine Book(?) ISBN (?) Title (?) Author (?) PubYear (?)

7. Entity Type, Attribute Type Student - Strong StudentID - Simple Name - Simple Email - Simple PhoneNo – Simple/ Multivalue Note: The PhoneNo attribute can be classified as a simple attribute when only one value is permitted. Alternatively, it can be categorized as a multivalued attribute if a student is allowed to have multiple phone numbers.

8. Entity Type, Attribute Type BookLoan - Weak LoanID - Simple DueDate - Simple ReturnDate - Simple RenewalDate – Simple/ Multivalue Fine - Composite FineAmount - Simple Status - Simple TotalFine - Derive Note: The renewal date is considered a multivalued attribute because it can have multiple values associated with a single book loan instance. The TotalFine is Derived from the FineAmount attribute in the Book Loan entity, indicating the total fine accrued by a student.

9. Entity Type, Attribute Type Book - Strong ISBN - Simple Title - Simple Author – Simple/ Multivalue PubYear – Simple Note: The Author attribute can be deemed a simple attribute when it permits only one value for the author. However, there are instances where certain books may have multiple authors.

10. STUDENT BOOK BOOKLOAN StudentID Name EMail PhoneNo LoanID DueDate ReturnDate Renewal Date TotalFine Fine Fine Amount Status ISBN TItle Author PubYear Loan Associate

11. 9/3/20XX Presentation Title 11

12. Strong Student( StudentID , Name, Email) PhoneNo ( StudentID , PhoneNo ) Book( ISBN , Title, PubYear ) Author( ISBN , Author) Weak BookLoan ( LoanID , StudentID , ISBN , DueDate , ReturnDate , FineAmount , Status, TotalFine ) RenewalDate ( LoanID , RenewalDate ) 9/3/20XX Presentation Title 12

13. 9/3/20XX Presentation Title 13