Database Systems: Design, Implementation, and Management: Entity Relationship (ER) Modeling

Database Systems:
Design, Implementation, and

Management
Tenth Edition
Chapter 4
Entity Relationship (ER) Modeling
Objectives
• In this chapter, students will learn:

– The main characteristics of entity relationship
components
– How relationships between entities are defined,
refined, and incorporated into the database
design process
– How ERD components affect database design
and implementation
– That real-world database design often requires
the reconciliation of conflicting goals
Database Systems, 10th Edition 2
The Entity Relationship Model (ERM)
• ER model forms the basis of an ER diagram

• ERD represents conceptual database as
viewed by end user
• ERDs depict database’s main components:
– Entities
– Attributes
– Relationships

Entities
• Refers to entity set and not to single entity

occurrence
• Corresponds to table and not to row in
relational environment
• In Chen and Crow’s Foot models, entity is
represented by rectangle with entity’s name
• The entity name, a noun, is written in capital
letters

Attributes
• Characteristics of entities
• Chen notation: attributes represented by ovals
connected to entity rectangle with a line
– Each oval contains the name of attribute it
represents
• Crow’s Foot notation: attributes written in
attribute box below entity rectangle

Attributes (cont’d.)
• Required attribute: must have a value

• Optional attribute: may be left empty
• Domain: set of possible values for an attribute
– Attributes may share a domain
• Identifiers: one or more attributes that uniquely
identify each entity instance
• Composite identifier: primary key composed of
more than one attribute

• Composite attribute can be subdivided

• Simple attribute cannot be subdivided
• Single-value attribute can have only a single
value
• Multivalued attributes can have many values

• M:N relationships and multivalued attributes

should not be implemented
– Create several new attributes for each of the
original multivalued attributes’ components
– Create new entity composed of original
multivalued attributes’ components
• Derived attribute: value may be calculated from
other attributes
– Need not be physically stored within database

Relationships
• Association between entities

• Participants are entities that participate in a
relationship
• Relationships between entities always operate
in both directions
• Relationship can be classified as 1:M
• Relationship classification is difficult to establish
if only one side of the relationship is known

Connectivity and Cardinality
• Connectivity
– Describes the relationship classification
• Cardinality
– Expresses minimum and maximum number of
entity occurrences associated with one
occurrence of related entity
• Established by very concise statements known
as business rules

Existence Dependence
• Existence dependence
– Entity exists in database only when it is
associated with another related entity
occurrence
• Existence independence
– Entity can exist apart from one or more related
entities
– Sometimes such an entity is referred to as a
strong or regular entity

Relationship Strength
• Weak (non-identifying) relationships

– Exists if PK of related entity does not contain PK
component of parent entity
• Strong (identifying) relationships
– Exists when PK of related entity contains PK
component of parent entity

Weak Entities
• Weak entity meets two conditions

– Existence-dependent
– Primary key partially or totally derived from
parent entity in relationship
• Database designer determines whether an
entity is weak based on business rules

Relationship Participation
• Optional participation
– One entity occurrence does not require
corresponding entity occurrence in particular
relationship
• Mandatory participation
– One entity occurrence requires corresponding
entity occurrence in particular relationship

Relationship Degree
• Indicates number of entities or participants

associated with a relationship
• Unary relationship
– Association is maintained within single entity
• Binary relationship
– Two entities are associated
• Ternary relationship
– Three entities are associated

Recursive Relationships
• Relationship can exist between occurrences of

the same entity set
– Naturally found within unary relationship

Associative (Composite) Entities
• Also known as bridge entities

• Used to implement M:N relationships
• Composed of primary keys of each of the
entities to be connected
• May also contain additional attributes that play
no role in connective process

Developing an ER Diagram
• Database design is an iterative process
– Create detailed narrative of organization’s description
of operations
– Identify business rules based on description of
operations
– Identify main entities and relationships from business
rules
– Develop initial ERD
– Identify attributes and primary keys that adequately
describe entities
– Revise and review ERD

Database Design Challenges:
Conflicting Goals
• Database designers must make design
compromises
– Conflicting goals: design standards, processing
speed, information requirements
• Important to meet logical requirements and
design conventions
• Design is of little value unless it delivers all
specified query and reporting requirements
• Some design and implementation problems do
not yield “clean” solutions
Summary
• Entity relationship (ER) model

– Uses ERD to represent conceptual database as
viewed by end user
– ERM’s main components:
• Entities
• Relationships
• Attributes
– Includes connectivity and cardinality notations

Summary (cont’d.)
• Connectivities and cardinalities are based on

business rules
• M:N relationship is valid at conceptual level
– Must be mapped to a set of 1:M relationships
• ERDs may be based on many different ERMs
• UML class diagrams are used to represent the
static data structures in a data model
• Database designers are often forced to make
design compromises

Database Systems: Design, Implementation, and Management: Entity Relationship (ER) Modeling

Uploaded by

Copyright:

Available Formats

Database Systems: Design, Implementation, and Management: Entity Relationship (ER) Modeling

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Database Systems: Design, Implementation, and Management: Entity Relationship (ER) Modeling

Uploaded by

Copyright:

Available Formats

Database Systems:

Design, Implementation, and

• In this chapter, students will learn:

• ER model forms the basis of an ER diagram

Database Systems, 10th Edition 3

• Refers to entity set and not to single entity

Database Systems, 10th Edition 4

Database Systems, 10th Edition 5

• Required attribute: must have a value

Database Systems, 10th Edition 7

• Composite attribute can be subdivided

Database Systems, 10th Edition 9

• M:N relationships and multivalued attributes

Database Systems, 10th Edition 11

• Association between entities

Database Systems, 10th Edition 13

Database Systems, 10th Edition 14

Database Systems, 10th Edition 16

• Weak (non-identifying) relationships

Database Systems, 10th Edition 17

• Weak entity meets two conditions

Database Systems, 10th Edition 20

Database Systems, 10th Edition 23

• Indicates number of entities or participants

Database Systems, 10th Edition 26

• Relationship can exist between occurrences of

Database Systems, 10th Edition 29

• Also known as bridge entities

Database Systems, 10th Edition 32

Database Systems, 10th Edition 35

• Entity relationship (ER) model

Database Systems, 10th Edition 49

• Connectivities and cardinalities are based on

You might also like