need a prper diagram for this datbase.

Consider the following set of requirements for a UNIVERSITY database that is used to keep track of students' transcripts. This is similar but not identical to the database shown in Figure 1.2:

(a) The university keeps track of each student's name, student number, social security number, current address, phone, email, residential state, residential country, birth date, sex, class (freshman, sophomore, junior, senior), major department, minor department (if any), and degree program (B.A., B.S., B.F.A., M.A. M.S.). Some user applications need to refer to the city, state, and zip of the student's permanent address, and to the student's last name. Both social security number and student number have unique values for each student.

(b) Each department is described by a name, department code, office number, office phone. Both name and code have unique values for each department.

(c) Each course has a course name, description, course number, number of semester hours, level, and offering department. The value of course number is unique for each course.

(d) Each section has an instructor, semester, year, course, begin date, end date, and section number. The section number distinguishes different sections of the same course that are taught during the same semester/year; its values are 1, 2, 3, up to the number of sections taught during each semester.

(e) A grade report has a student, section, letter grade, and numeric grade (0, 1, 2, 3,

4 for F, D, C, B, A, respectively).

Design an ER diagram for the above conditions.

Specify key attributes of each entity type and structural constraints (cardinality) on each relationship type. Note any unspecified requirements. Make appropriate assumptions to make the specification complete. Please return the ER diagram in pdf form.

3.16 Continued 15 points From the ER diagram in question 3.16, provide a fundamental dependency (FD) schema and normalize the FD schema to third normal form (3NF).