Questions
3-5 questions per university paper
Difficulty
Medium
Importance
Core high-yield topic for all DBMS exams
Overview
Entity-Relationship (ER) Modelling is a high-level conceptual data model that describes data as entities, attributes, and relationships. It is the cornerstone of database design, serving as the bridge between business requirements and the physical database schema. Mastery of this topic is essential for creating robust, normalized database structures in any software development lifecycle.
Entities and Relationships
An entity is a real-world object distinguishable from other objects, while a relationship represents the association between entities. Entities are categorized into strong (independent existence) and weak (dependent on identifying entity).
- Strong Entity represented by a single rectangle
- Weak Entity represented by a double rectangle
- Relationship represented by a diamond shape
- Attributes represented by ovals
- Key Attribute indicated by underlining
- Multivalued attribute represented by a double oval
Cardinality and Participation
Cardinality constraints define the number of entity instances that can be associated with another entity instance through a relationship. Participation constraints define whether the existence of an entity depends on its being related to another entity via the relationship type.
- One-to-One (1:1) mapping
- One-to-Many (1:N) mapping
- Many-to-One (N:1) mapping
- Many-to-Many (M:N) mapping
- Total Participation: double line connection
- Partial Participation: single line connection
ER to Relational Mapping
This process involves converting the conceptual ER diagram into a set of tables (relations) for implementation in a RDBMS. Every entity becomes a table, and relationships are translated based on their cardinality.
- Strong entity: becomes a standalone table
- Weak entity: table includes foreign key from identifying entity
- 1:N relationship: place PK of 1-side into N-side table
- M:N relationship: create a separate junction table
- Multivalued attribute: create a separate table
- Composite attribute: flatten into multiple simple columns
Formula Sheet
Cardinality Ratio (e.g., 1:N, M:N)
Degree of Relationship (Unary, Binary, Ternary)
Exam Tip
Always ensure you explicitly state the Primary Key and Foreign Key constraints when mapping ER diagrams to tables, as this is where most marks are lost.
Common Mistakes
- Confusing weak entity participation with mandatory participation in a relationship
- Failing to create a separate table for M:N relationships during mapping
- Using the wrong cardinality notation (e.g., using Chen notation mixed with Crow's Foot)
More Revision Notes
Ready to test yourself?
Play topic-wise ER Modelling questions in Aspirant Arcade — gamified MCQ practice.
Download Free