Data Modeling Using the

Entity-Relationship (ER) Model

 Entity Relationship Modeling

Objectives:
• To illustrate how relationships between entities are defined and refined.
• To know how relationships are incorporated into the database design
process.
• To describe how ERD components affect database design and
implementation.
What is Conceptual Database
Design?

 Process of describing the data, relationships

between the data, relationships between the
data, and the constraints on the data.
 After analysis - Gather all the essential data
required and understand how the data are related
 The focus is on the data, rather than on the
processes.
 The output of the conceptual database design is
a Conceptual Data Model ( + Data Dictionary)
Gathering Information for Conceptual
Data Modeling

 Two perspectives
 Top-down
 Data model is derived from an intimate
understanding of the business.
 Bottom-up
 Data model is derived by reviewing specifications
and business documents.
 Composite versus Simple (Atomic)
Attributes

 Composite attributes can be divided into smaller

subparts, which represent more basic attributes
with independent meanings.
 Address attribute of the EMPLOYEE entity can be subdivided into
Street_address, City, State, and Zip.

Database Systems
 Composite versus Simple (Atomic)
Attributes

 simple or atomic attributes

 Attributes that are not divisible.

Database Systems
 Single-Valued versus Multivalued
Attributes

 Single Value
 attributes have a single value for a particular entity
 Age is a single-valued attribute of a person
 Multivalued Attributes
 attribute can have a set of values for the same entity
 a Colors attribute for a car, or a College_degrees
attribute for a person.
Cars with one color have a single value,
 two-tone cars have two color values.
 person may have two or more degrees;
Database Systems
 Stored versus Derived Attributes

 the Age and Birth_date attributes of a person

 Age can be determined from the current
(today’s) date and the value of that person’s
Birth_date
 The Age attribute is hence called a derived
attribute and is said to be derivable from
the Birth_date attribute, which is called a
stored attribute

Database Systems
 Entity and its keys

 Regular entity

 Any entity that has a unique key

 Weak entity
 An entity type with no key

Database Systems
FIGURE 7.1
The ER conceptual schema diagram for the COMPANY database.

Slide 7- 10
Entity-Relationship (ER) Modeling.

 ER Modeling is a `top-down approach to

database design.
 Entity Relationship (ER) Diagram
 A detailed, logical representation of the entities,
associations and data elements for an organization or
business
 Notation uses three main constructs
 Data entities Chen Model
 Relationships & Crow’s
 Attributes Foot Model
 Chen Notation

Association
between the
instances of one or
more entity types

EntityName Verb Phrase AttributeName

Person, place, object, event named property or

or concept about which data characteristic of an
is to be maintained entity

Represents a set or
collection of objects in
the real world that share
the same properties
Crow’s Foot Notation

Entity Attribute Relationship

EntityName
EntityName Verb phrase

List of
Attributes

Acceptable
Entities
 Examples of entities:
 Person: EMPLOYEE, STUDENT, PATIENT
 Place: STORE, WAREHOUSE
 Object: MACHINE, PRODUCT, CAR
 Event: SALE,REGISTRATION, RENEWAL
 Concept: ACCOUNT, COURSE
 Guidelines for naming and defining entity types:
 An entity type name is a singular noun
 An entity type should be descriptive and specific
 An entity name should be concise
 Event entity types should be named for the result of the event, not
the activity or process of the event.
Attributes

 Example of entity types and associated attributes:

STUDENT: Student_ID, Student_Name, Home_Address,
Phone_Number, Major

 Guidelines for naming attributes:

 An attribute name is a noun.
 An attribute name should be unique
 To make an attribute name unique and clear, each attribute name
should follow a standard format
 Similar attributes of different entity types should use similar but
distinguishing names.
Identifier Attributes
 Candidate key
 Attribute (or combination of attributes) that uniquely
identifies each instance of an entity type
 Some entities may have more than one candidate key
 Ex: A candidate key for EMPLOYEE is Employee_ID, a second is
the combination of Employee_Name and Address.
 If there is more than one candidate key, need to make a choice.

 Identifier
 A candidate key that has been selected as the unique
identifying characteristic for an entity type
Referential Attributes

 Make Reference to another instance in another table

Referential attribute: Ties the lecturer entity to

another entity that is department.

Name IdNum DeptID Email

Ali 105 LG [email protected]

Mary 106 IT [email protected]

John 107 ENG [email protected]
Lim 108 IT [email protected]
Instance of Lecturer.
Example

Name Gender

StaffID IC

Staff

Staff
PK StaffID
Name
Gender
IC
Relationships
 Associations between instances of one or more entity
types that is of interest
 Given a name that describes its function.
• relationship name is an active or a passive verb.

Relationship name:
writes

Author Book

An author writes one or more books

A book can be written by one or more authors.
Degree of Relationships

 Degree: number of entity types that participate in a relationship

 Three cases
 Unary: between two instances of one entity type
 Binary: between the instances of two entity types
 Ternary: among the instances of three entity types
Cardinality and Connectivity

 Relationships can be classified as either

 one – to – one
 one – to – many
Connectivity
 many – to –many

 Cardinality : minimum and maximum number of

instances of Entity B that can (or must be)
associated with each instance of entity A.
2.4 Cardinality and Connectivity

Professor teaches Class

teaches
Professor Class

A professor teaches class OR

A class is taught by professor

How Many??
2.4 Cardinality and Connectivity
Connectivity

1 M
Professor teaches Class

(1,4) (1,1)
Cardinality

Connectivity

teaches
Professor Class

(1,1) (1,4)
Cardinality
Connectivity
 Chen Model
 1 to represent one. 1
 M to represent many
M

 Crow’s Foot

One Mandatory one ,

means (1,1)
many

One or
many Optional? – we’ll see
after this
Binary Relationships
 1:M relationship
 Relational modeling ideal
 Should be the norm in any relational database design

The 1: M relationship between PAINTER and PAINTING

The Implemented 1:M relationship between PAINTER and PAINTING
Binary Relationships
 1:1 relationship
 Should be rare in any relational database design
 A single entity instance in one entity class is related to a single entity
instance in another entity class
 Could indicate that two entities actually belong in the same table
The 1:1 Relationship Between PROFESSOR and DEPARTME
Binary Relationships

 M:N relationships
 Must be avoided because they lead to data redundancies.
 Can be implemented by breaking it up to produce a set of 1:M
relationships
 Can avoid problems inherent to M:N relationship by creating a
composite entity or bridge entity
 This will be used to link the tables that were originally related
in a M:N relationship
 The composite entity structure includes-as foreign keys-at
least the primary keys of the tables that are to be linked.
 The M:N Relationship Between STUDENT and CLASS
Bowser Accounting 1 (ACCT-211)

Intro to Microcomputing
Smithson
(CIS-220)
Intro to Statistics (QM-
261)
This CANNOT be implemented as shown next…..
The tables have many redundancies!!

+ CLASS_CODE
CLASS_CODE

+ STU_NUM
Changing the M:N relationship to TWO 1:M relationships
 The database designer has 2 main options to
define a composite table’s primary key:
either
use the combination of those foreign
keys or create a new primary key.

Foreign keys reference the primary keys in the

other tables of which it has a relationship with

Converting the M:N relationship into TWO 1:M relationships

Mandatory vs. Optional Cardinalities
 Specifies whether an instance must exist or can be absent in the
relationship

Optional
Mandatory

M
1
Lecturer handles Class
(0,N) (1,1)

A Lecturer may handle zero or many classes.

A class is handled by one and only one Lecturer.

How to Evaluate a Data Model?

 A good data model has the following:

 Accuracy and completeness
 Non redundancy
 Enforcement of business rules
 Data Reusability
 Stability and Flexibility
 Communication Effectiveness
 Simplicity
A Common Mistake
Modeling the business processes or functions
instead of the data.

What data we want to keep??

We are interested in modeling the data,
NOT the processes or functions that use
or generate those data.
 Example:

M N
Member Searches Books

Is this part of the data requirement?

Are we interested to know the books searched by the
members?
If answer is NO, then DO NOT include that as a
relationship.
Use other appropriate diagramming techniques to capture
the business processes such as Data Flow Diagram.
Do not mix up the use of ER Modeling with DFD.