ERD Design and Mapping Database
تفاصيل العمل
To design an Entity-Relationship Diagram (ERD) and map the database for the school system based on the provided information, we can identify the following entities and their relationships:
Entities:
Student
Medical Report
Sibling
Parent(Mother/Father)
Teacher
Subject Head (Senior Teacher)
Class
Attributes for each entity:
Student:
Serial Number (Primary Key)
Full Name
Age
Gender
Date of Birth
Completion Certificate Copy
Division
Medical Report (FK)
Medical Report:
Report ID (Primary Key)
Weight
Length
Disease/Allergy Information
Sibling:
Sibling ID (Primary Key)
Student ID(FK)
Name
Discount
Parent:
Parent ID (Primary Key)
Parent Name
Relationship (Father/Mother)
Student Serial Number (Foreign Key to Student entity)
Teacher:
Teacher ID (Primary Key)
Name
Subject
Phone Number
Email Address
Monthly Salary
Subject Head (FK Student ID)
Class:
Class Name
Location (Building No(PK), Floor No(PK))
Class Capacity
Schedule
Relationships:
Each Student has one Medical Report. (One-to-One relationship)
Each Student belongs to one Division, but a Division can have many Students. (One-to-Many relationship)
Some Students may have Siblings in the school, leading to a Sibling entity. (Many-to-Many relationship, resolved with an associative entity Sibling)
Each Student has two Parents, but a Parent can have multiple Students. (One-to-Many relationship)
Each Teacher is associated with one Class, but a Class can have multiple Teachers. (Many-to-Many relationship, resolved with an associative entity Teacher_Class)
There is a Subject Head for each group of Teachers. (One-to-One relationship between Teacher and Subject Head)
Each Class is associated with one Division, and a Division can have multiple Classes. (One-to-Many relationship)