ER Design Problem $[75$ points$]$ ER Design Problem $[75$ points$]$

University Database System Design:

Design an ER diagram for a university database system that manages student enrollment,

course offerings, course sections, instructors, and grades. The system should meet the

following requirements:

Students: Each student has a unique student ID$,$ name, date of birth, and contact

information. A student can enroll in multiple courses.

Courses: Each course has a unique course ID$,$ course name, and course

description. Each course can have multiple sections.

Course Sections: Each course section has a unique section ID$,$ associated course

ID$,$ semester $($e$.$g$.,$ Fall $2024),$ and a section schedule $($days and times$).$ Each

section is taught by one instructor and can have multiple students enrolled.

Instructors: Each instructor has a unique instructor ID$,$ name, department, and

contact information. An instructor can teach multiple sections of different courses.

Enrollment: A student can enroll in multiple course sections, and a course section

can have multiple students. For each enrollment, the system should track:

Enrollment Date

Final Grade: The final grade a student receives for the course section.

Departments: Each instructor belongs to a department, which has a unique

department ID and department name. A department can have multiple instructors.

Grades: The system should maintain a record of each student's final grade in a

section. Grades should be tracked for historical records, even after the student

completes the course or the course is no longer offered.

Create an ER diagram representing the entities, relationships, and attributes based on the

above specifications. Include primary keys, participation constraints $($partial or full$)$ and

indicate key constraints $($such as $1-$to$-1,1-$to$-$n$,$ or n$-$to$-$m$)$ where applicable. Use only one

notation for the ER diagram and do not mix notations.

University Database System Design:

Design an ER diagram for a university database system that manages student enrollment,

course offerings, course sections, instructors, and grades. The system should meet the

following requirements:

$1.$ Students: Each student has a unique student ID$,$ name, date of birth, and contact

information. A student can enroll in multiple courses.

$2.$ Courses: Each course has a unique course ID$,$ course name, and course

description. Each course can have multiple sections.

$3.$ Course Sections: Each course section has a unique section ID$,$ associated course

ID$,$ semester $($e$.$g$.,$ Fall $2024),$ and a section schedule $($days and times$).$ Each

section is taught by one instructor and can have multiple students enrolled.

$4.$ Instructors: Each instructor has a unique instructor ID$,$ name, department, and

contact information. An instructor can teach multiple sections of different courses.

$5.$ Enrollment: A student can enroll in multiple course sections, and a course section

can have multiple students. For each enrollment, the system should track:

o Enrollment Date

o Final Grade: The final grade a student receives for the course section.

$6.$ Departments: Each instructor belongs to a department, which has a unique

department ID and department name. A department can have multiple instructors.

$7.$ Grades: The system should maintain a record of each student$$s final grade in a

section. Grades should be tracked for historical records, even after the student

completes the course or the course is no longer offered.

Create an ER diagram representing the entities, relationships, and attributes based on the

above specifications. Include primary keys, participation constraints $($partial or full$)$ and

indicate key constraints $($such as $1-$to$-1,1-$to$-$n$,$ or n$-$to$-$m$)$ where applicable. Use only one

notation for the ER diagram and do not mix notations.