Enhanced Entity-Relationship (EER) Model Flashcards
Additional semantic data modeling concepts incorporated into ER model to
reflect the data properties and constraints more precisely
Enhanced Entity-Relationship (EER) Model
also called Extended ER Model
A subset of an entity set with a meaningful (or an explicit need for) subgrouping
Subclass (or Subtype)
Entity set from which the subgroupings were formed
Superclass (or Supertype)
Also called superclass/subclass or supertype/subtype relationship
Also called an IS-A (or IS-AN) relationship
Class/Subclass Relationship
Subclasses inherit all the
attributes and relationship types of their superclass(es)
Inheritance (or Type Inheritance)
Process of defining a set of
subclasses of an entity type
Maximizes the difference between the set of subclasses
Used in top-down conceptual
refinement process
Specialization
Process of defining a generalized entity type from given entity types
Suppresses (minimizes) the
differences between entity types by identifying their common features
Used in bottom-up conceptual
synthesis process
Generalization
Specialization vs Generalization
Specialization starts with a superclass, and defining a set of subclasses from it. Generalization on the other hand starts with specialized entity types and defining a generalized entity type (Superclass) from it.
Why include Class/Subclass Relationships?
- Certain attributes may apply to some but not all entities of the superclass entity type
- Some relationship types may be participated in only by entities that are members of the
subclass
Subclass membership can be determined by placing a condition on the value
of some attribute of the superclass
Defining predicate is written next to the line connecting subclass to circle
Predicate-Defined Subclasses
(Condition-defined subclasses)
Subclass membership condition determined by the same attribute of the superclass
Attribute-Defined Subclasses
Subclass membership is determined by the (would-be) database users
User-Defined Subclasses
Constraints (on Specialization/Generalization)
Disjointness
Completeness (Totalness)
Uses the circle notation to indicate type: disjoint (d) or overlapping (o)
Disjointness
Entity can be a member of at
most one of the subclasses of the specialization
Disjoint
Entity can be a member of multiple subclasses of the specialization
Overlapping
Similar to the Participation constraint on relationship types but on the specialization context
Completeness
Specifies that every entity in the
superclass must be a member of at least one subclass in the
specialization
Total Specialization
Allows an entity not to belong to any of the subclasses
Partial Specialization
TRUE OR FALSE:
Deleting an attribute from a superclass implies that it is automatically deleted
from all subclasses to which it belongs
TRUE
Every subclass participates in only one class/subclass relationship (Only single inheritance would exist)
Specialization Hierarchy
A subclass can be a subclass in more than one class/subclass relationship (Multiple inheritance would occur)
Specialization Lattice
Subclass that represents a collection of entities from different entity types
Has 2 or more superclasses that may represent collections of entities from
distinct entity types
Union Type (or Category)
Union Type vs Shared Subclass
Shared subclass is the subset of the intersection of the entity sets, whereas a union type is the union of the entity sets