Entity Relationship (ER) Modeling

The Entity Relationship Model (ERM)

Database Systems, 9th Edition2

ER model forms the basis of an ER diagramERD represents conceptual database as

viewed by end userERDs depict database’s main components:

EntitiesAttributesRelationships

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

Entity name, a noun, written in capital letters

Keys


Each row in a table must be uniquely identifiable

Key is one or more attributes that determine other attributes

Key’s role is based on determinationIf you know the value of attribute A, you can

determine the value of attribute BFunctional dependence

Attribute B is functionally dependent on A if all rows in table that agree in value for A also agree in value for B

Keys (cont’d.)


Composite keyComposed of more than one attribute

Key attributeAny attribute that is part of a key

SuperkeyAny key that uniquely identifies each row

Candidate key A superkey without unnecessary attributes

Keys (cont’d.)


NullsNo data entryNot permitted in primary keyShould be avoided in other attributesCan represent:

An unknown attribute valueA known, but missing, attribute valueA “not applicable” condition

Keys (cont’d.)


Nulls (cont’d.)Can create problems when functions such as

COUNT, AVERAGE, and SUM are usedCan create logical problems when relational

tables are linked

Attributes


Characteristics of entitiesChen notation: attributes represented by

ovals connected to entity rectangle with a lineEach oval contains the name of attribute it

representsCrow’s Foot notation: attributes written in

attribute box below entity rectangle

Attributes (cont’d.)


Required attribute: must have a valueOptional attribute: may be left emptyDomain: set of possible values for an

attributeAttributes 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 subdividedSimple attribute cannot be subdividedSingle-value attribute can have only a

single valueMultivalued attributes can have many

values



M:N relationships and multivalued attributes should not be implementedCreate several new attributes for each of the

original multivalued attributes’ componentsCreate new entity composed of original

multivalued attributes’ componentsDerived attribute: value may be

calculated from other attributesNeed not be physically stored within

database

Relationships


Association between entitiesParticipants are entities that participate

in a relationshipRelationships between entities always

operate in both directionsRelationship can be classified as 1:MRelationship 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 dependenceEntity exists in database only when it is

associated with another related entity occurrence

Existence independenceEntity can exist apart from one or more

related entitiesSometimes such an entity is referred to as a

strong or regular entity

Relationship Strength


Weak (non-identifying) relationshipsExists if PK of related entity does not contain

PK component of parent entityStrong (identifying) relationships

Exists when PK of related entity contains PK component of parent entity

Weak Entities


Weak entity meets two conditionsExistence-dependentPrimary key partially or totally derived from

parent entity in relationshipDatabase designer determines whether an

entity is weak based on business rules

Relationship Participation


Optional participationOne entity occurrence does not require

corresponding entity occurrence in particular relationship

Mandatory participationOne entity occurrence requires

corresponding entity occurrence in particular relationship

Relationship Degree


Indicates number of entities or participants associated with a relationship

Unary relationshipAssociation is maintained within single entity

Binary relationship Two entities are associated

Ternary relationship Three entities are associated

Developing an ER Diagram


Database design is an iterative processCreate detailed narrative of organization’s

description of operationsIdentify business rules based on description of

operationsIdentify main entities and relationships from

business rulesDevelop initial ERDIdentify attributes and primary keys that

adequately describe entitiesRevise and review ERD

Entity Relationship (ER) Modeling

Documents

Transcript of Entity Relationship (ER) Modeling