ER Model

The real-world problem is depicted in visual form in this model to make it easier for stakeholders to
comprehend. The ER diagram also makes it very simple for developers to comprehend the system.
What is the Entity-Relationship Model in DBMS?
A high-level data model diagram is the entity-relationship model or ER Model. We depict the real-
world problem in visual form in this model to make it easier for stakeholders to comprehend. The
developers can also quickly grasp the system by simply looking at the ER Diagram.

Features of an Entity-Relationship Model

1. Graphical Representation for Better Understanding – It is really straightforward and
easy to comprehend, so developers can use it to interact with stakeholders.

2. Database Design – This approach is extensively used in database design and aids database
designers in the creation of databases.

3. ER Diagram – The ER diagram is a visual representation of the model.

Components of an ER Diagram
The ER diagram is a visual representation of an ER Model. The three components of an ER
diagram are as follows:

1. Entities
An entity is a real-life concept. It could be a person, a location, or even an idea. A school
management system, for example, has entities such as teachers, students, courses, buildings,
departments, and so on.

2. Attributes
An attribute is a real-world property that exists in an entity. For example, the entity teacher
has properties such as teacher salary, id, age, and so on.

3. Relationship
The relationship between two traits describes how they are linked. A teacher, for example,
works for a department.
Pros of Entity-Relationship Model
1. Simple – The ER Model is simple to construct conceptually. We can easily construct the
ER Diagram for the model if we know the relationship between the entities and the attributes.

2. Effective communication tool – Database designers frequently employ this model to

communicate their thoughts.

3. Easy conversion to any model – This model translates neatly to the relational model, and
it is simple to transform the ER model into a table. This model can be transformed into a
network model, a hierarchical model, and so forth.

Cons of Entity-Relationship Model

1. No industry standard for notation – When it comes to creating an ER model, there is no
industry standard. As a result, one developer may utilise notations that are unfamiliar to other
developers.

2. Hidden information – In the ER model, certain information may be lost or hidden.

Because it is a high-level view, there is a potential that some information specifics will be
buried.

Symbols Used in ER Model

ER Model is used to model the logical view of the system from a data perspective
which consists of these symbols:
 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.
Entity:
An entity may be any object, class, person or place. In the ER diagram, an entity can be
represented as rectangles.Consider an organization as an example- manager, product,
employee, department etc. can be taken as an entity.

Weak Entity

An entity that depends on another entity called a weak entity. The weak entity doesn't contain
any key attribute of its own. The weak entity is represented by a double rectangle.

Attribute
The attribute is used to describe the property of an entity. Eclipse is used to represent an
attribute.

For example, id, age, contact number, name, etc. can be attributes of a student.
a. Key Attribute

The key attribute is used to represent the main characteristics of an entity. It represents a
primary key. The key attribute is represented by an ellipse with the text underlined.

b. Composite Attribute

An attribute that composed of many other attributes is known as a composite attribute. The
composite attribute is represented by an ellipse, and those ellipses are connected with an
ellipse.
c. Multivalued Attribute

An attribute can have more than one value. These attributes are known as a multivalued
attribute. The double oval is used to represent multivalued attribute.

For example, a student can have more than one phone number.

d. Derived Attribute

An attribute that can be derived from other attribute is known as a derived attribute. It can be
represented by a dashed ellipse.

For example, A person's age changes over time and can be derived from another attribute
like Date of birth.
Relationship
A relationship is used to describe the relation between entities. Diamond or rhombus is used
to represent the relationship.

Types of relationship are as follows:

a. One-to-One Relationship

When only one instance of an entity is associated with the relationship, then it is known as
one to one relationship.

For example, A female can marry to one male, and a male can marry to one female.

b. One-to-many relationship
When only one instance of the entity on the left, and more than one instance of an entity on
the right associates with the relationship then this is known as a one-to-many relationship.

For example, Scientist can invent many inventions, but the invention is done by the only
specific scientist.

c. Many-to-one relationship

When more than one instance of the entity on the left, and only one instance of an entity on
the right associates with the relationship then it is known as a many-to-one relationship.

For example, Student enrolls for only one course, but a course can have many students.

d. Many-to-many relationship

When more than one instance of the entity on the left, and more than one instance of an entity
on the right associates with the relationship then it is known as a many-to-many relationship.

For example, Employee can assign by many projects and project can have many employees.

Example of ER Diagram