Académique Documents
Professionnel Documents
Culture Documents
Model
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 2
What is ER Model? And Why?
Interface between
conceptual schema and
external schemas
Conceptual
Database Approach: Schema
Internal
Schema
Database
physically stored
in files on disks
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 3
What is ER Model? And Why?
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 4
Example COMPANY Database
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 5
Example COMPANY Database
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 6
Example COMPANY Database
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 8
ER Model Concepts
Types of Attributes
– Simple
Each entity has a single atomic value for the attribute. For
example, SSN or Sex
– Composite
The attribute may be composed of several components. For
example, Address (Apt#, House#, Street, City, State, ZipCode,
Country) or Name (FirstName, MiddleName, LastName).
Composition may form a hierarchy where some components are
themselves composite
– Multi-valued
An entity may have multiple values for that attribute. For example,
Color of a CAR or PreviousDegrees of a STUDENT. Denoted as
{Color} or {PreviousDegrees}
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 9
ER Model Concepts
Types of Attributes
– In general, composite and multi-valued attributes may be
nested arbitrarily to any number of levels although this is
rare
E.g., PreviousDegrees of a STUDENT is a composite multi-
valued attribute denoted by
{ PreviousDegrees (College, Year, Degree, Field) }
– Derived Attribute
Attribute that represents a value that is derivable from value of
a related attribute, or set of attributes, not necessarily in the
same entity type
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 10
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 11
ER Model Concepts
car1
((ABC 123, TEXAS), TK629, Ford Mustang, convertible, 1999, (red, black))
car2
((ABC 123, NEW YORK), WP9872, Nissan 300ZX, 2-door, 2002, (blue))
car3
((VSY 720, TEXAS), TD729, Buick LeSabre, 4-door, 2003, (white, blue))
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 12
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 13
Example COMPANY Database
Example relationship instances
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 16
Summary of the Notation for ER Diagrams
Example COMPANY Database
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 19
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 20
Example COMPANY Database
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 22
One-to-many (1:N) or Many-to-one (N:1)
RELATIONSHIP
EMPLOYEE WORKS_FOR DEPARTMENT
r1
e1 ● ● d1
r2
e2 ●
e3 ● r3 ● d2
e4 ● r4
● d3
e5 ●
r5
e6 ●
r6
e7 ●
r7
Many-to-many (M:N) RELATIONSHIP
e3 ● r3 ● p2
e4 ● r4
● p3
e5 ●
r5
e6 ●
r6
e7 ●
r8 r7
ER Model Concepts
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 25
Example COMPANY Database
ER Model Concepts
PERSON MARRY
M
1
PART COMPRISE
N
N
EMPLOYEE SUPERVISE
1
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 27
ER Model Concepts
Recursive relationships:
– Both participations are same entity type in
different roles
– For example, SUPERVISION relationships
between EMPLOYEE (in role of supervisor or
boss) and (another) EMPLOYEE (in role of
subordinate or worker)
– In following figure, first role participation labeled
with 1 and second role participation labeled with 2
– In ER diagram, need to display role names to
distinguish participations
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 28
A Recursive Relationship SUPERVISION
EMPLOYEE SUPERVISION
2
e1 ● r1
1
e2 ● 2
1
2 r2
e3 ●
1
e4 ● 2 r3
1
e5 ● 1
2 r4
e6 ● 1
2 r5
e7 ●
r6
Example COMPANY Database
ER Diagram
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 31
ER Diagram
Example Univ Database
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 32
ER Diagram
Example Univ Database
N 1
N
M 1
MODULE TEACH LECTURER
M
ENROL STUDENT
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 33
ER Diagram
Example Univ Database
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 34
ER Diagram
Example Univ Database
Relationships:
– HEAD_OF:
1:1 between LECTURER and DEPARTMENT
Membership: Mandatory for DEPARTMENT
– IS_IN:
1:N between DEPARTMENT and LECTURER
Membership: Mandatory for both
– OFFER:
1:N between DEPARTMENT and MODULE
Membership: Mandatory for MODULE
– ENROL:
M:N between STUDENT and MODULE
Membership: Mandatory for both
Attribute: DATE (date of enrolment)
– TEACH:
1:M between LECTURER and MODULE
Membership: Mandatory for both
Homework: Do complete the ER Diagram !!
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 35
ER Diagram
(min, max) notation for relationship structural constraints
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 36
ER Diagram
(min, max) notation for relationship structural constraints
(0,1) (1,1)
(1,1) (4,N)
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 37
ER diagrams for the COMPANY schema, with structural
constraints specified using (min, max) notation
Problems with ER Models
Problems may arise when designing a conceptual
data model called connection traps
Often due to a misinterpretation of the meaning of
certain relationships
Two main types of connection traps are called fan
traps and chasm traps
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 39
Problems with ER Models
Fan Trap
– Where a model represents a relationship between entity types, but
pathway between certain entity occurrences is ambiguous
– Usually: two or more 1:N relationships fan out from the same
entity
Chasm Trap
– Where a model suggests the existence of a relationship between
entity types, but pathway does not exist between certain entity
occurrences
– Usually: optional participation
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 40
An Example of a Fan Trap
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 46
Alternative Diagrammatic Notations
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 48
Q&A
Dr. Dang Tran Khanh (dtkhanh@hcmut.edu.vn), M.eng. Tran Minh Quang (quangtran@cse.hcmut.edu.vn) 49