Develop an ER schema for the following database application. Specify key attributes for each entity type and structural constraints on each relationship. Please indicate any unspecified requirements and create appropriate assumptions in order to make the specification complete.

Consider the following set of requirements for a UNIVERSITY database that is used to keep track of students' transcripts.

The university stores the following information about each student: name, college ID number, social security number, current address and phone, permanent address and phone, birthdate, sex, class $($freshman$,$ sophomore, $...,$ graduate$),$ major department, minor department $($if any$),$ and degree program $($B$.$A$.,$ B$.$S$.,...,$ Ph$.$D$.).$

Some user applications need to refer to the city, state, and zip of the student's addresses, and to the student's last name. Both social security number and college ID number have unique values for each student.

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

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.

Each section has an instructor, semester, year, course, 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.

Each instructor has a name, a college ID number, a rank $($instructor$,$ asst. prof, assoc. prof, prof.$)$ and a research specialty. An instructor belongs to only one department.

A grade report has a student, section, letter grade, and numeric grade $(0,1,2,3,4$ for F$,$ D$,$ C$,$ B$,$ A$,$ respectively$).$

Develop an ER schema for the following database application. Specify key attributes for each entity type and structural constraints on each relationship. Please indicate any unspecified requirements and create appropriate assumptions in order to make the specification complete.

Consider the following set of requirements for a UNIVERSITY database that is used to keep track of students' transcripts.