Reference no: EM13329201

Problem 1: Entity-Relationship (ER) Model

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

(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 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 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).

(1A) Using the General notations to design an ER diagram. 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.

(1B) Convert the ER diagram in (1A) to relational database schemas.

(1C) Draw the ER diagram using Industral-style notations by ER-Assistant Tool.

Problem 2: Entity-Relationship (ER) Model

Composite and multi-valued attributes can be nested to any number of levels.

Suppose we want to design an attribute for a STUDENT entity type to keep track of previous college education. Such an attribute will have one entry for each college previously attended, and this entry is composed of: college name, start and end dates, degree entries (degrees awarded at 2 that college, if any), and transcript entries (courses completed at that college, if any). Each degree entry is formed of degree name and the month and year it was awarded, and each transcript entry is formed of a course name, semester, year, and grade. Design an attribute using the General notations to hold this information.

Problem 3: Entity-Relationship (ER) Model

Show an alternative design using the General notations for the attribute described in Problem 2 that uses only entity types (including weak entity types if needed) and relationship types.

Problem 4: (Enhanced Entity-Relationship Model)

Given the following EER diagram of the Museum Database.

(4A) List the requirements for this EER diagram.

(4B) Convert this EER diagram to relational database schemas.