Académique Documents
Professionnel Documents
Culture Documents
With Entity
Relationship
Diagram
PART 2
Data Modeling with
Entity Relationship Diagrams
Relationship Strength
Weak Entities
Relationship Participation
Relationship Degree
Recursive Relationship
Develop ER Diagram
Data
Modeling ERD
with
ERD Relationship Strength
Strong entity sets have a primary key; weak entity sets have no primary key.
Weak entities rely on strong entities for their existence in the data model.
E.g. the next-of-kin of an employee are irrelevant if the employee leaves.
In ER diagrams:
weak entities are denoted by
double-boxes
strong/weak entity relationships
are denoted by double- name phone
diamonds
discriminators are denoted by
dotted underline
Data
Modeling ERD
with !
ERD
Weak Entities
Data
Modeling ERD
with !
ERD
Weak Entities
Data
Modeling
with !
ERD
ERD 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
Data
Modeling
with !
ERD
ERD Relationship Participation
Data
Modeling
with !
ERD
ERD Relationship Participation
Data
Modeling
with !
ERD
ERD Relationship Degree
2013 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition.
May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.
DISCUSSION
Exercise 1
Each company operates four departments, and each department
belongs to one company.
Each department in employs one or more employees, and each
employee works for one department.
Each of the employees may or may not have one or more
dependents, and each dependent belongs to one employee.
Each employee may or may not have an employment history.