Introduction to Database Design – ER
modeling
lab notes
Example: E-R diagram for a
car-insurance company with the following information:
-
–people own one or more cars
each.
-
–A car can does not have multiple
owners
-
•People
with attributes driver-id, name, address
-
•Car
with attributes license, model, year
-
Each car has associated with it
zero to any number of recorded accidents.
-
•Accident
with attributes report-number, location, date
-
The car owner might not be the driver of
the car involved in the accident
-
–For each accident record the damage-amount
Step one - Define Entity set
-
People - driver-id, name, address
-
Car - license, model, year
-
Accident - report-number, location, date
Step two - Relationship sets
Step tree - Build ER diagram
Exercise
2.3 Consider the following
information about a university database:
- Professors
have an SSN, a name, an age, a rank, and a research specialty.
- Projects
have a project number, a sponsor name (e.g., NSF), a starting date, an
ending date, and a budget.
- Graduate
students have an SSN, a name, an age, and a degree program (e.g., M.S. or
Ph.D.).
- Each
project is managed by one professor (known as the project’s principal
investigator).
- Each
project is worked on by one or more professors (known as the project’s
co-investigators).
- Professors
can manage and/or work on multiple projects.
- Each
project is worked on by one or more graduate students (known as the
project’s research assistants).
- When
graduate students work on a project, a professor must supervise their work
on the project. Graduate students can work on multiple projects, in which
case they will have a (potentially di.erent) supervisor for each one.
Departments have a department number, a department name, and a main office.
- Departments
have a professor (known as the chairman) who runs the department.
- Professors
work in one or more departments, and for each department that they work in,
a time percentage is associated with their job.
- Graduate
students have one major department in which they are working on their
degree.
- Each
graduate student has another, more senior graduate student (known as a
student advisor) who advises him or her on what courses to take.
Design
and draw an ER diagram that captures the information about the university. Use
only the basic ER model here, that is, entities, relationships, and attributes.
Be sure to indicate any key and participation constraints.
Solution
Exercise
2.5 Notown Records has decided
to store information about musicians who perform on its albums (as well as other
company data) in a database. The company has wisely chosen to hire you as a
database designer (at your usual consulting fee of
$2,500/day).
- Each
musician that records at Notown has an SSN, a name, an address, and a phone
number. Poorly paid musicians often share the same address, and no address
has more than one phone.
- Each
instrument that is used in songs recorded at Notown has a name (e.g.,
guitar, synthesizer, flute) and a musical key (e.g., C, B-.at, E-.at).
- Each
album that is recorded on the Notown label has a title, a copyright date, a
format (e.g., CD or MC), and an album identifier.
- Each
song recorded at Notown has a title and an author.
- Each
musician may play several instruments, and a given instrument may be played
by several musicians.
- Each
album has a number of songs on it, but no song may appear on more than one
album.
- Each
song is performed by one or more musicians, and a musician may perform a
number of songs.
- Each
album has exactly one musician who acts as its producer. A musician may
produce several albums, of course.
Design and draw an
ER diagram for your schema. The following information describes the situation
that the Notown database must model. Be
sure to indicate all key and cardinality constraints and any assumptions that
you make. Identify any constraints that you are unable to capture in the ER
diagram and briefly explain why you could not express them.
Solution