Draw both ER Diagram and UML notation for the following scenarios:

Scenario 1:

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

The university keeps track of each students name, student number, social security number, permanent address and several contact numbers, birth date, age, sex, and major, and degree program (B.A., B.S., . . ., Ph.D.).

Some user applications need to refer to the city, state, and zip code of the students permanent address and to the students last name. Both social security number and student number have unique values for each student.

1. 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.

2. A department can train other departments.

3. Each student must enroll in one department.

4. Each course has a course name, description, and course number, number of credit

hours, level. The value of course number is unique for each course.

5. Course may generate many sections, each has a se

mester, year, section number, and

references a single course. The section number distinguishes sections of the same

course that are taught during the same semester/year.

6. Each section may contain many students

Scenario 1: Consider the following set of requirements for a university database that is used to keep track of students' transcripts. The university keeps track of each student's name, student number, social security number, permanent address and several contact numbers, birth date, age, sex, and major, and degree program (B.A., B.S., ..., Ph.D.). Some user applications need to refer to the city, state, and zip code 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. 1. 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. 2. A department can train other departments. 3. Each student must enroll in one department. 4. Each course has a course name, description, and course number, number of credit hours, level. The value of course number is unique for each course. 5. Course may generate many sections, each has a semester, year, section number, and references a single course. The section number distinguishes sections of the same course that are taught during the same semester/year. 6. Each section may contain many students Scenario 1: Consider the following set of requirements for a university database that is used to keep track of students' transcripts. The university keeps track of each student's name, student number, social security number, permanent address and several contact numbers, birth date, age, sex, and major, and degree program (B.A., B.S., ..., Ph.D.). Some user applications need to refer to the city, state, and zip code 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. 1. 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. 2. A department can train other departments. 3. Each student must enroll in one department. 4. Each course has a course name, description, and course number, number of credit hours, level. The value of course number is unique for each course. 5. Course may generate many sections, each has a semester, year, section number, and references a single course. The section number distinguishes sections of the same course that are taught during the same semester/year. 6. Each section may contain many students