taking a ________ to modeling data and relationships in a business process is important because of
standardized approach, the complexity involved
enhanced ER diagram
ER diagram that shows subtypes and supertypes of entities and identifies relationships between them
supertype
entity type that includes distinct subtypes that needs to be represented in data model
subtype
subgrouping of entities in an entity type that is meaningful to org and shares common attributes/relationships distinct from other subgroups
how to show subtype and supertype on EER diagram
example of sub and supertypes
supertype: employee, all entity instances have employee ID, name, address, and date hired
subtypes: hourly (hourly rate attribute), salaried (annual salary and stock option attributes), consultant (contract number and billing rate attributes)
first steps to EER diagram
relationships at the supertype level indicate that
all subtypes will participate in the relationship
if a relationship is shown at the subtype level
only instances part of that subtype participate in relationship
2 processes for identifying supertypes and subtypes
generalization and specialization
generalization
process of minimizing the differences between entities by identifying their common features and aggregating them into a supertype, with subtypes for leftover attributes
generalization is a
bottom-up approach (creates smaller number of entity types from a larger number)
potential downside of generalization
being too general and having too few entity types, leaving out important details
specialization
identify relevant differences between entities and splitting them into necessary subtypes
specialization is a
bottom-down approach
potential byproduct of generalization
realizing an entity had no particular distinguishing characteristics and has no need to be a subtype
subtype discriminator
attribute of supertype whose values determine target subtype
example of subtype discriminator
attribute Employee_type can be H, S, or C, each representing 3 subtypes of employee supertype
why use subtype discriminator
speed up data retrieval if there are large number of subtypes
constraints are
intuitive, help us manifest business rules and incorporate them into EER design
participation constraint
dictate whether every member of superclass must participate as a member of a subclass
disjoint constraints
define whether it is possible for an instance of a superclass to be a member of one or more subclasses simultaneously
disjoint rule
disjoint constraint specifies that if subtypes of specialization are disjoint then an entity can be a member of only one subtype
non-disjoint (overlap) rule
if subtypes of specialization are not disjoint then an entity may be a member of more than one subtype