Scribd
Upload
1 views2 pages

EER_Help_File

The Extended Entity Relationship (EER) Model builds on the ER model by incorporating advanced concepts like specialization, generalization, inheritance, aggregation, and categories, which are essential for modeling complex database applications. It distinguishes between supertype and subtype relationships, allowing for better abstraction and reduced redundancy. The EER model is applicable in various fields such as hospital management, banking, and university management, providing improved scalability and accurate real-world modeling.

Uploaded by

krishikamittal15
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1 views2 pages

EER_Help_File

The Extended Entity Relationship (EER) Model builds on the ER model by incorporating advanced concepts like specialization, generalization, inheritance, aggregation, and categories, which are essential for modeling complex database applications. It distinguishes between supertype and subtype relationships, allowing for better abstraction and reduced redundancy. The EER model is applicable in various fields such as hospital management, banking, and university management, providing improved scalability and accurate real-world modeling.

Uploaded by

krishikamittal15
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Extended Entity Relationship (EER) Model

The Extended Entity Relationship (EER) Model extends the ER model with advanced concepts
such as specialization, generalization, inheritance, aggregation and categories. It is used to model
complex database applications.

Difference Between ER and EER


ER Model: entities, attributes and relationships. EER Model: includes supertype/subtype,
inheritance, specialization, generalization and advanced constraints.

Supertype and Subtype


A supertype contains common attributes. Example: Person(Person_ID, Name, Address, Phone).
Subtypes: Student(Roll_No, Semester) and Employee(Employee_ID, Salary). Student and
Employee inherit Name, Address and Phone.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.

Specialization
Top-down approach. Example: Employee -> Faculty, Staff, Technician. Each subtype inherits
Employee_ID, Name and Salary and adds its own attributes.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.

Generalization
Bottom-up approach. Example: Student and Teacher are generalized into Person because they
share Name, Address and Phone.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.

Inheritance
Subtypes automatically inherit attributes and relationships of the parent entity. Example: Faculty
inherits Employee_ID, Name, Salary and adds Subject and Qualification.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.

Aggregation
Aggregation treats a relationship as a higher-level entity. Example: Manager manages the
Works_On relationship between Employee and Project.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.

Categories (Union Type)


A category is a subtype whose instances come from multiple supertypes. Example: Owner may be
a Person or a Company.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.
Constraints
Total specialization: every Employee is Faculty or Staff. Partial specialization: some Employees
remain only Employee. Disjoint: entity belongs to one subtype only. Overlapping: a Person may be
both Student and Employee.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.

Complete Example
University Management System: Person -> Student, Employee; Employee -> Faculty, Admin Staff;
Student -> Research Scholar. Faculty teaches Course and supervises Project.
Example Diagram (text):
Person -> {Student, Employee}; Employee -> {Faculty, Staff}; Student -> {Research Scholar}.

Applications
Hospital Management, Banking, University Management, E-commerce, Library Management, ERP
and HR Systems.

Advantages
Better abstraction, reduced redundancy, inheritance support, easier maintenance, improved
scalability and accurate real-world modeling.

Summary
The EER model enhances ER modeling through supertype-subtype hierarchies, specialization,
generalization, inheritance, aggregation and constraints, making it suitable for complex database
design.

You might also like