Entity Relationship Modeling
Entity Relationship Modeling
Information Management
Entity Relationship Modeling
Learning Objectives
After completing this chapter, you will be able to:
Required
Domain
Attribute
Composite Multivalued
Attribute Attributes
Derived Attribute
Attribute whose value is calculated from other attributes
Derived using an algorithm
Multivalued Attributes
and Cardinality
Connectivity
describes the relationship classification
Include 1:1, 1:M, and M:N
Cardinality
expresses the minimum and maximum number of entity
occurrences associated with one occurrence of related
entity
In the ERD, cardinality is indicated by placing the
appropriate numbers beside the entities, using the
format (x, y)
Existence Dependence
Existence dependence Existence independence
Weak
Entities
EMP_NUM EMP_NUM
A Weak Entity in an ERD
EMP_LNAME DEP_NUM
EMP_FNAME DEP_FNAME
EMP_INITIAL DEP_DOB
EMP_DOB
EMP_HIREDATE
Entities
A Weak Entity in a Strong
Relationship
Ternary Relationship
three entities are associated
Recursive Relationship
relationship exists within a single
entity type
Relationship can exist between occurrences
Recursive
of the same entity set
Relationships
Naturally, such a condition is found within a unary
relationship
Common in manufacturing industries
Note: ENROLL is the composite entity that implements the M:N relationship “STUDENT enrolls in CLASS.”
Database
Design
Challenges: Database designers must often make design
Conflicting compromises that are triggered by conflicting
Goals goals
Conflicting
Goals
VARIOUS
IMPLEMENTATIONS OF THE
1:1 RECURSIVE
RELATIONSHIP
SECOND IMPLEMENTATION
VARIOUS
IMPLEMENTATIONS OF THE
1:1 RECURSIVE
RELATIONSHIP