๐Ÿ’พ
Welcome to DataGenesis !
  • ๐Ÿš€ Welcome to the Database Management System Playground! ๐Ÿ“Š๐Ÿ’พ
  • Basics of DBMS
    • Database Management System
    • DBMS V/S File System
    • DBMS Architectures
    • Tier 3 Architecture / Three Schema Architecture
  • E-R Data Model
    • Basics of E-R Model
    • Attributes in E-R Model
    • Null Values
    • Strong & Weak Entities
    • Relationship Constraints
    • Recursive Relationships
    • E-R Diagrams
    • Extended E-R Model
  • Relational Model
    • Relational Model
    • Facts About Relational Model
    • Types of Keys in Relational Model
    • Integrity Constraints
    • Anomalies in Relational Model
  • Transform - ER Model to Relational Model
    • Mapping from ER Model to Relational Model
  • SQL - Structured Query Language
    • SQL
    • CRUD Operations
    • Data Types
    • Type of Commands in SQL
    • Working With Commands
    • Data Retrieval Commands
  • Normalisation
    • Functional Dependencies
    • Armstrong's Axioms
    • Multivalued Dependency
    • 1 Normal Form
    • 2 Normal Form
    • 3 Normal Form
    • Boyce-Codd Normal Form (BCNF)
    • 4 Normal Form
    • 5 Normal Form
    • Lossless Decomposition, Lossless Join ,and Dependency Preserving Decomposition, Denormalization
  • Concurrency Control
    • Transactions & Concurrency
    • Scheduling of Transactions
    • Problems & Strategies in Concurrency Control
    • Transaction & ACID Properties
    • How to implement ACID Properties
    • Atomicity Techniques
    • Durability Techniques
    • Implementing Locking in DBMS
    • Concurrency Control Protocols
      • Two Phase Locking
      • Timestamp Ordering
      • Multi Version Concurrency Control Techniques
    • Starvation in DBMS
    • Deadlock in DBMS
    • Log Based Recovery
  • NoSQL & Types of Databases
    • SQL V/S NoSQL
    • Types of Databases
  • DB Optimization
    • File Organization
      • Hash File Organizations
      • B+ Tree File Organization: A Guide to Efficient Data Indexing
      • Cluster File Organization
    • Indexing in DBMS
      • Primary Indexing
      • Clustered Indexing
      • Secondary Indexing
      • Multilevel Indexing
  • Distributed Databases
    • Database Clustering
    • Partitioning and Sharding
    • CAP Theorm
Powered by GitBook
On this page
  • Specialization ( TOP DOWN )
  • Generalization ( BOTTOM UP )
  • Attribute Inheritance
  • Participation Inheritance
  • Aggregation

Was this helpful?

  1. E-R Data Model

Extended E-R Model

PreviousE-R DiagramsNextRelational Model

Last updated 1 year ago

Was this helpful?

In the Entity-Relationship (ER) model of database design, Generalization, Specialization, and Aggregation are three important concepts used to model relationships and hierarchies among entities. Let's explore each of these concepts:

Specialization ( TOP DOWN )

  1. In ER model, we may require to subgroup an entity set into other entity sets that are distinct in some way with other entity sets.

  2. Specialisation is splitting up the entity set into further sub entity sets on the basis of their functionalities, specialities and features.

  3. It is a Top-Down approach.

  4. e.g., Person entity set can be divided into customer, student, employee. Person is superclass and other specialised entity sets are subclasses.

  5. We have โ€œis-aโ€ relationship between superclass and subclass.

  6. Depicted by triangle component.

Why Specialisation ?

  1. Certain attributes may only be applicable to a few entities of the parent entity set.

  2. DB designer can show the distinctive features of the sub entities.

  3. To group such entities we apply Specialisation, to overall refine the DB blueprint.

Generalization ( BOTTOM UP )

  1. It is just a reverse of Specialisation.

  2. 2. DB Designer, may encounter certain properties of two entities are overlapping. Designer may consider to make a new generalised entity set. That generalised entity set will be a super class.

  3. 3. โ€œis-aโ€ relationship is present between subclass and super class.

  4. 4. e.g., Car, Jeep and Bus all have some common attributes, to avoid data repetition for the common attributes. DB designer may consider to Generalise to a new entity set โ€œVehicleโ€.

  5. 5. It is a Bottom-up approach. 6. Why Generalisation?

  6. Makes DB more refined and simpler.

  7. Common attributes are not repeated

Attribute Inheritance

  1. Both Specialisation and Generalisation, has attribute inheritance.

  2. The attributes of higher level entity sets are inherited by lower level entity sets.

  3. E.g., Customer & Employee inherit the attributes of Person.

Participation Inheritance

If a parent entity set participates in a relationship then its child entity sets will also participate in that relationship

Aggregation

In aggregation, the relation between two entities is treated as a single entity. In aggregation, relationship with its corresponding entities is aggregated into a higher level entity.

For example: Center entity offers the Course entity act as a single entity in the relationship which is in a relationship with another entity visitor. In the real world, if a visitor visits a coaching center then he will never enquiry about the Course only or just about the Center instead he will ask the enquiry about both.

In summary, Generalization, Specialization, and Aggregation are essential concepts in the ER model for modeling relationships, hierarchies, and complex structures in a database schema. They help in creating more organized, efficient, and semantically rich database designs that accurately represent real-world scenarios.