Skip to content
Home » Entity Relationship Model

Entity Relationship Model

Below is a complete, exam-oriented, and advanced-level explanation of the Entity–Relationship (ER) Model — perfect for 5-mark, 10-mark, and 15-mark answers.

ENTITY–RELATIONSHIP (ER) MODEL

The Entity–Relationship Model (ER Model) is a high-level conceptual data model used to design the logical structure of a database.
It was proposed by Peter Chen in 1976.

ER Modeling is used during the database design phase to represent real-world entities, their attributes, and their relationships in a graphical form called an ER Diagram (ERD).

PURPOSE OF ER MODEL

✔ Represents real-world data in a structured form
✔ Helps designers understand system requirements
✔ Forms the basis for creating relational schema
✔ Ensures clarity before implementation
✔ Avoids redundancy by identifying relationships correctly

COMPONENTS OF ER MODEL

The ER Model consists of the following components:

1. ENTITY

An Entity is a real-world object/person/place/concept about which we store data.

Examples:

  • Student
  • Teacher
  • Customer
  • Product
  • Department

Entities are represented by rectangles in ER diagrams.

Types of Entities

(a) Strong Entity

  • Has its own primary key
  • Does not depend on any other entity
    Example: Student(StudentID, Name, Age)

(b) Weak Entity

  • Cannot be uniquely identified by its own attributes
  • Depends on a strong entity
  • Identified by a partial key + strong entity’s key
    Example: Dependent(Name, Age) → depends on Employee

Represented using double rectangles.

2. ATTRIBUTES

Attributes are properties or characteristics of an entity.

Example (Student Entity):

  • RollNo
  • Name
  • Age
  • Email

Represented by ellipses.

Types of Attributes

  1. Simple Attribute – cannot be divided (Age, Salary).
  2. Composite Attribute – can be divided (Address → City, State).
  3. Single-valued Attribute – has one value (DOB).
  4. Multi-valued Attribute – has multiple values (Phone Numbers).
  5. Derived Attribute – derived from other attributes (Age from DOB).
  6. Key Attribute – uniquely identifies each entity (StudentID).

Multi-valued attributes → double ellipse
Derived attributes → dotted ellipse

3. RELATIONSHIPS

A Relationship is an association between two or more entities.

Example:

  • Student enrolls in Course
  • Employee works in Department
  • Customer buys Product

Represented by diamonds.

4. DEGREE OF RELATIONSHIP

Degree = Number of entities participating.

  1. Unary (1 entity) – Employee manages Employee
  2. Binary (2 entities) – Most common
  3. Ternary (3 entities) – Supplier supplies product to project

5. CARDINALITY (MAPPING CONSTRAINTS)

Defines the number of occurrences of one entity related to another.

Types:

  1. One-to-One (1:1)
    Example: Each passport issued to one citizen.
  2. One-to-Many (1:M)
    Example: One department has many employees.
  3. Many-to-One (M:1)
    Example: Many students belong to one department.
  4. Many-to-Many (M:N)
    Example: Students enroll in many courses; each course has many students.

Cardinality helps DB designers create correct foreign keys.

6. PARTICIPATION CONSTRAINTS

Specifies if participation in a relationship is mandatory or optional.

Types:

  • Total Participation – entity must participate
    (Employee must belong to a department)
  • Partial Participation – participation is optional
    (Customer may or may not place an order)

Represented with double lines for total participation.

7. GENERALIZATION, SPECIALIZATION, AND INHERITANCE

ER Model also supports hierarchical relationships.

(a) Generalization

Combines multiple entity types into a higher-level entity.
Example:

  • Car, Bus, Truck → Vehicle

(b) Specialization

Breaks a high-level entity into lower-level sub-entities.
Example:

  • Employee → Full-Time / Part-Time

(c) Inheritance

Attributes of a superclass are inherited by subclasses.

Useful for complex database designs.

8. WEAK ENTITY SETS

A weak entity:

  • Has no primary key
  • Identified through a strong entity
  • Uses a partial key
  • Relationship with the strong entity is identifying relationship

Represented with double diamond for the relationship.

ER DIAGRAM SYMBOLS (Quick Visual)

Entity:          [ Student ]
Attribute:        (Name)
Key Attribute:    (RollNo underlined)
Weak Entity:      [[ Dependent ]]
Relationship:      <> Enrolls <>
Multi-valued:     ((Phone))
Derived:          (Age dotted)

ADVANTAGES OF ER MODEL

✔ Easy to understand (graphical)
✔ Accurately models real-world relationships
✔ Helps identify entities and attributes clearly
✔ Reduces redundancy
✔ Provides a clear blueprint for relational database creation

LIMITATIONS OF ER MODEL

✘ Not suitable for very complex, real-time applications
✘ Doesn’t handle unstructured data well
✘ Poor representation of dynamic behavior
✘ Not ideal for large-scale distributed (NoSQL) systems

SUMMARY (Perfect for 5 Marks)

The ER Model is a high-level conceptual model used to design databases.
It represents data using entities, attributes, and relationships.
It supports:

  • Strong & weak entities
  • Simple, composite, multi-valued, derived attributes
  • Relationships with cardinality (1:1, 1:M, M:N)
  • Participation constraints
  • Generalization and specialization

ER models form the foundation for creating relational schema.