3.16 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 and phone, permanent address and phone,

birthdate, sex, class (freshman, sophomore, ..., graduate), major department,

minor department (if any), and by Shopping Sidekick">degree program (B.A., B.S., ..., Ph.D.). 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 by Shopping Sidekick">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, and college. 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, 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 schema for this by Shopping Sidekick">application, and draw an ER diagram for that schema.

Specify key attributes of each entity type and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete.

Consider the university database described in Exercise 7.16 of the Elmasri/Navathe text. Enter the ER schema for this database using a data-modeling tool such as ERWin. Reference: Elmasri, R., & Navathe, S. B. (2010). Fundamentals of Database Systems, 6th ed. New York, NY. Pearson Addison-Wesley. ISBN: 0-136-08620-9 / 978-0-136-08620-8. LAB exercise 7.31 PG 241