Assignment 1
Assignment 1
Problem One:
Create an entity relationship diagram for a chain of automobile workshops. We are interested in:
-
(Database Systems: Concepts, Languages, and Architectures, Atzeni, Ceri, Paraboschi, Torlone, ISBN 0-07235952-8)
To get full credit: (1) create diagram and in addition (2) list, describe, and describe the cardinatlity for each
relationaship, (3) list each attribute and describe the domain of the attribute
Problem Two:
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 the figure above.
a)
The university keeps track of each students name, student nubmer, 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 refere 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.
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 the course number is unique fore each course.
d) Each section ahs an instructor, semester, year, course, and section number. The section number
distinguishes 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 or 4).
Design an ER schema for this application, and draw an ER diagram for that schema. Specify key attributes for
each entity type, and structural constraints on each relationship type. Note any unspecified requirements, and
make appropriate assumptions to make the specification complete.
To get full credit: (1) create diagram and in addition (2) list, describe, and describe the cardinatlity for each
relationaship, (3) list each attribute and describe the domain of the attribute
Problem Three:
This diagram shows a simplified schema for an airline reservations system. Extract from the ER diagram the
requirements and constraints that produced this schema. This problem is an exercise in reverse engineering an
ER Diagram. If you showed this diagram to a group of non-technical people, how would you describe what it
means? If you read your answer to this problem, would you be able to recreate the ER Diagram?
Requirements describe the entities, attributes, and relationships between entities.
Constraints describe attribute domains and relationship cardinalities.