Entity

Relational
model
 Agenda
Concepts of
01 ER model 03 diagram

02 ER diagram 04 Conclusion
 Entity Relationship
The entity relationship (ER) data model has
existed for over 35 years. It is well suited to data
modelling for use with databases because it is fairly
abstract and is easy to discuss and explain. ER
models are represented by ER diagrams.

ER modelling is based on two

concepts:
● Entities, defined as tables that hold specific
information (data)
● Relationships, defined as the associations or
interactions between entities
 ER Model
• Entity Relationship Model is a high-
level conceptual data model
diagram.
• ER model helps to systematically
analyze data requirements to
produce a well-designed database.
• The ER Model represents real-world
entities and the relationships
between them.
Entity Relationship
Diagram
ERD is a diagram that
displays the relationship of
entity sets stored in a
database.
ER diagrams help to
explain the logical structure of
databases.
ER diagrams are created
based on three basic
concepts: entities,
attributes and
 WHAT IS ENTITY?
● A real-world thing either living or non-
living that is easily recognizable and
nonrecognizable.
● It may be a physical thing or simply a
fact about the enterprise or an event
that happens in the real world.
● The characteristics of entities are must
have an attribute, and a unique key.
Every entity is made up of some
‘attributes’ which represent that entity.
Examples of entities:

Person: Employee, Student,

Patient
Place: Store, Building
Object: Machine, product,
and Car
Event: Sale, Registration,
Renewal
Entity Set: An Entity is an object of
Entity Type and a set of all entities is
called an entity set.
 Weak VS Strong
entity
● Weak entity is an entity that cannot be
uniquely identified by its attributes alone.
For example, the bank account of a particular
bank has no existence if the bank doesn't exist
anymore.
●Strong entity is an entity that is not
dependent on any other entity. It has a primary
key, or a table includes a primary key. For
example the "Customer" is the entity type with
attributes such as ID, Name, Gender, and
Phone Number.
 Relationship
● Relationship is nothing but an association
among two or more entities. E.g., Tom works
in the Chemistry department.
 Cardinality
● The number of times an entity of an entity set
participates in a relationship set is known as
cardinality. Cardinality can be of different
types:
1. One-to-One: When each entity in each
entity set can take part only once in the
relationship, the cardinality is one-to-one. Let
us assume that a male can marry one female
and a female can marry one male. So the
relationship will be one-to-one.
2. One-to-Many: In one-to-many mapping
as well where each entity can be related to
more than one relationship. Let us assume that
one surgeon deparment can accomodate many
doctors. So the Cardinality will be 1 to M. It
means one deparment has many Doctors.
3. Many-to-One: When entities in one entity
set can take part only once in the relationship set and
entities in other entity sets can take part more than once
in the relationship set, Let us assume that a student can
take only one course but one course can be taken by
many students.
4. Many-to-Many: When entities in
all entity sets can take part more than once in
the relationship. Let us assume that a student
can take more than one course and one course
can be taken by many students.
Attributes
It is a single-valued property
of either an entity-type or a
relationship-type.
For example, a lecture might
have attributes: time, date,
duration, place, etc.
An attribute in ER Diagram
examples, is represented by
an Ellipse
Attributes
Symbols Used in ER Model
Rectangles: Rectangles represent Entities in
the ER Model.
Ellipses: Ellipses represent Attributes in the
ER Model.
Diamond: Diamonds represent Relationships
among Entities.
Lines: Lines represent attributes to entities
and entity sets with other relationship
types.
Double Ellipse: Double Ellipses represent
Multi-Valued Attributes.
Double Rectangle: Double Rectangle
represents a Weak Entity.
Symbols Used in ER Model
 Introduction_

The “our idea” part of a pitch deck

should include an explanation of your
product/service, how it works, and
what the customer value is. You
should also explain the market
opportunity for your product/service
 Summary
The ER model is a high-level data model diagram
ER diagrams are a visual tool which is helpful to represent the ER
model
Entity relationship diagram DBMS displays the relationships of entity
set stored in a database
ER Model in DBMS is based on three basic concepts: Entities,
Attributes & Relationships
An entity can be place, person, object, event or a concept, which
stores data in the database (DBMS)
Relationship is nothing but an association among two or more entities
A weak entity is a type of entity which doesn’t have its key attribute
It is a single-valued property of either an entity-type or a relationship-
type
It helps you to defines the numerical attributes of the relationship
between two entities or entity sets
ER- Diagram DBMS is a visual representation of data that describe