Scribd
Upload
4 views31 pages

Ch03 - The Enhanced E-R Model

The document discusses various modeling techniques in database management, focusing on supertype/subtype notation and generalization/specialization concepts. It illustrates how different entities can share attributes through supertype relationships and how to apply completeness and disjointness constraints. Additionally, it highlights the use of entity clusters for improved readability in data models.

Uploaded by

anhpnk24411
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views31 pages

Ch03 - The Enhanced E-R Model

The document discusses various modeling techniques in database management, focusing on supertype/subtype notation and generalization/specialization concepts. It illustrates how different entities can share attributes through supertype relationships and how to apply completeness and disjointness constraints. Additionally, it highlights the use of entity clusters for improved readability in data models.

Uploaded by

anhpnk24411
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 31

Modern Database Management

12th Edition
Global Edition

Jeff Hoffer, Ramesh Venkataraman,


Heikki Topi
Figure 3-1 Basic notation for supertype/subtype notation

a) EER
notation
Figure 3-1 Basic notation for supertype/subtype notation (cont.)

b) Microsoft
Visio
Notation

Different modeling tools may have different notation for the same
modeling constructs.
Figure 3-2 Employee supertype with three subtypes

All employee subtypes


will have employee
number, name, address,
and date hired

Each employee subtype


will also have its own
attributes
Figure 3-3 Supertype/subtype relationships in a hospital
Figure 3-4 Example of generalization
a) Three entity types: CAR, TRUCK, and MOTORCYCLE

All these types of vehicles have common attributes


Figure 3-4 Example of generalization (cont.)
b) Generalization to VEHICLE supertype

So we put
the shared
attributes in
a supertype

Note: no subtype for motorcycle, since it has no unique


attributes
Figure 3-5 Example of specialization

a) Entity type PART

Only applies to
manufactured parts

Applies only to purchased parts


Figure 3-5 Example of specialization (cont.)
b) Specialization to MANUFACTURED PART and PURCHASED PART

Created 2
subtypes

Note: multivalued composite attribute was replaced


by an associative entity relationship to another entity
Figure 3-6 Examples of completeness constraints
a) Total specialization rule
Figure 3-6 Examples of completeness constraints (cont.)
b) Partial specialization rule
Figure 3-7 Examples of disjointness constraints

a) Disjoint rule
Figure 3-7 Examples of disjointness constraints (cont.)
b) Overlap rule
Figure 3-8 Introducing a subtype discriminator (disjoint rule)
Figure 3-9 Subtype discriminator (overlap rule)
Figure 3-10 Example of supertype/subtype hierarchy

Employee Type (
Employee?: Y-N
Alumnus?: Y-N
Student?: Y-N)
Figure 3-13a
Possible entity
clusters for Pine
Valley Furniture in
Microsoft Visio

Related
groups of
entities could
become
clusters
Figure 3-13b EER diagram of PVF entity clusters

More readable,
isn’t it?
Figure 3-14 Manufacturing entity cluster

Detail for a single cluster


Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in
a universal data model
(a) Basic PARTY universal
data model

Packaged data
models are
generic models
that can be
customized for a
particular
organization’s
business rules.
Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in
a universal data model

(b) PARTY supertype/subtype hierarchy

You might also like