Hello, my friends.
I would greatly appreciate it if you could review and provide suggestions on this database design.
Thank you.
- Staff: This entity represents the staff employed by the high school. It might have attributes such as ID, name, email address, and job title. The relationship might be many-to-one with the Courses entity, as a course can be taught by multiple staff members but a staff member can only teach one course at a time.
- Courses: This entity represents the courses offered by the high school. It might have attributes such as ID, name, description, start date, and end date. The relationship might be one-to-many with the Staff entity, as described above, and one-to-many with the Academic Reports entity, as a course can have multiple academic reports but an academic report can only be associated with one course.
- Payments: This entity represents the payments made by students or parents for tuition, textbooks, and other fees. It might have attributes such as ID, amount, date, and type. The relationship might be one-to-many with the Students entity, as a student can make multiple payments but a payment can only be associated with one student.
- Academic Reports: This entity represents the academic reports of the students for a course. It might have attributes such as ID, report type, grade, and date. The relationship might be many-to-one with the Courses entity, as described above, and one-to-one with the Students entity, as a student can have one academic report per course.
- Alumni: This entity represents the former students of the high school. It might have attributes such as ID, name, graduation year, and current occupation. The relationship might be many-to-one with the Courses entity, as described above, as alumni may have taken multiple courses during their time at the school.
- Parents: This entity represents the parents of the students. It might have attributes such as ID, name, and email address. The relationship might be one-to-many with the Students entity, as a student can have multiple parents but a parent can only be associated with one student.
- News and Events: This entity represents the news and events happening in the high school. It might have attributes such as ID, title, description, and date. The relationship might be many-to-many with the Courses entity, as a news or event might be related to one or more courses.
- CBT Exam: This entity represents the computer-based tests (CBT) taken by students. It might have attributes such as ID, name, duration, and passing score. The relationship might be one-to-many with the Courses entity, as a CBT exam can be associated with one or more courses, but a course can only have one CBT exam.
