Investigating

Entity-Relationship
Model’s Weakness
Group 2
Nguyễn Duy Bảo
Nguyễn Phước Hồng Quang Bảo
Trần Quốc Bảo
Nguyễn Trọng Chuẩn
Table of contents
01 02
Notation Relationship
Problems Representation

03 04
Common An Alternative
Mistakes Model
 01
Notation Problems
Notation inconsistencies and unintuitiveness make it difficult for
engineers to read and exchange diagrams.
“…agree
“Being
“I Unfortunately,
athere
diagram,
is nothey
there
suchcanaisstandard
no
show standardfor ERnotation: different
interconnectedness
modeling.
database design
In fact,practitioners
some
moreorganizations
clearly
preferthandifferent
ahave
text their
notations…”
description.
own standard,In depending
that way they on their
are easier
needstoand read
and understand.
knowledge
“…The notations
of their
However,
shown
teams.inOn there
[figure]
theisother
noshow
“intuitive”
hand,
onlywesome of the
notation.
have
diagrammatic
a myriad
People symbols
ofmust
coding learn
that
standards,
have
to read been
these
likeused or suggested for
diagrams and
CamelCase
displaying database
and
that’s
otheraconceptual
disadvantage.
good practices.schemes.
Also,
I believe
Other
there notations, as
are amany
it's
well as
matter
various
different
of how
combinations
important
notationsof isand
the
to some
have
[preceding],
aare not have also
easy to
modeling
been used.
understand.”
standard
It wouldinbeorder
useful to to
enhance
establishvalue
a standard
to that
software products
everyone would adhere deliveries,
to, in even
ordermoreto prevent
because
of the agile ways of developing.”
misunderstandings and reduce confusion…”Rich Cohen
Enterprise Architect and Data Modeler

Fernando Aparecido Nogueira

São Paulo State University
Attribute Symbols
Relationship Symbols
Displaying Attributes
Displaying Cardinality Ratios
Various (min, max) Notations
ER model and diagram is nothing more than a tool
for planning, visualization and communication.
Projecting abstract database design concepts to an
observable medium will always cause certain
information to be missing.

Database designers should keep consistency in mind

when sketching diagrams, make additional notes
where plain drawings can’t convey information, and
don’t be afraid to ask for clarification when facing a
strange diagram.
 02
Relationship Representation
Sometimes, problems known as connection traps occurs due to the
misinterpretation of the meaning of certain relationships.
There are two common types of connection traps in
Fan Trap:
database systems: Fan trap and Chasm trap. Both
An ER
Fan andmodel
Chasm that traps
represents
occura relationship between entity
when it becomes
occurrences is ambiguous.
impossible to retrieve all the necessary information
needed from the entire diagram.
Where does Bảo work?
Hà Nội or Hồ Chí Minh?
 Reconstruction.
Bảo works at Hà Nội and in the Marketing department.
Chasm Trap:
A pathway does not exist in all the related entities.
Which branch offers locker Loc_2?
 03
Common Mistakes
Pitfalls to avoid when creating an ER diagram.
Incorrect relationships between entities:
Occurs when defining the relationship between entities as it is very easy
to confuse a 1:N relationship with an M:N relationship.
Using entity instance instead of entity:
An entity that could be an attribute of a larger category, but isn’t.
Confusing an attribute with an entity:
Arises when an entity consists of too many attributes that don't uniquely
define it.
Complex attributes:
A complex attribute in an entity that should be its own entity, but isn’t.
 About ER Model and Data Manipulation
Data manipulation is the process of changing or altering data in order to
make it more readable and organized… 

Although ER model can be used to describe most kinds of data, it does not
capture these data manipulation operations that may be performed on entities
and relationships, including:

• Mathematical operations on numbers - multiplication, division, a log

transform, and so on.
• Merging two lists to create a longer list.
• Transforming an entity in some way.
• Splitting a single entity into its component parts.
• Forming a new entity out of other entities.
 04
An Alternative Model
A suggestion for cases when ER model can’t fulfill all
requirements.
 EER (Enhanced Entity Relationship) Model
A high-level data model that incorporates some extensions to
the original.
Sub Class and Super Class:
Allows the concept of Inheritance.
Specialization and Generalization:
Divides/combines entities to lower/higher levels.
Category:
Relationship of a class with more than one super class.
Aggregation:
Two or more entities are treated as one.
Kahoot
Time!
Thanks!
Does anyone have any questions?
 Reference
● Ramez Elmasri & Shamkant Navathe. (2015). Fundamentals of Database Systems.
● Enhanced Entity Relationship Model (EER Model) (tutorialride.com)
● What are the motivations for not having an ER model standard yet? (researchgate.net)
● Rich Cohen's answer to What are the benefits or disadvantages of ER diagrams? – Quora
● Problems with ER Model – javatpoint
● Common ER Diagram Mistakes | Vertabelo Database Modeler
● PowerPoint template from Slidesgo