Download presentation
Presentation is loading. Please wait.
Published byRoland Anthony Modified over 9 years ago
2
Basic ER modeling was adequate for simpler databases, but in the 1980’s more demanding databases required more extensive modeling requirements. Some such applications: CAD - Computer Aided Design CAM – Computer Aided Manufacturing CASE – Computer Assisted Software Engineering OIS – Office Information Systems GIS – Geographical Information Systems
3
EER adds 3 main additional semantic concepts for visual modeling of databases using UML(Unified Modeling Language). 1. Specialization/Generalization 1. Superclass 2. Subclass 3. Inheritance 2. Aggregation 3. Composition
4
Very similar to Object Oriented programming superclass, subclass and inheritance. Superclass: An entity type that includes one ore more subgroupings of its occurrences, which require to be represented in a data model. Subclass: A distinct subgrouping of occurrences of an entity type, which require to be represented in a data model. Superclass/Subclass relation is a 1:1 relation Superclass may contain overlapping subclasses Helps avoid multiple copies of the same data and null entries
5
Subclasses inherit Superclasses attributes Subclass is its own entity Subclass may have its own subclasses Shared Subclass: Entity with more than 1 Superclass : (Multiple Inheritance) An entity and its Sublasses are called: Type Hierarchy Specialization Hierarchy Generalization Hierarchy Is-A Hierarchy
6
Specialization: The process of maximizing the differences between members of an entity by identifying their distinguishing characteristics. Specialization is a Top-Down approach Generalization: The process of minimizing the differences between entities by identifying their common characteristics. Generalization is a Bottom-Up approach
7
Use an open triangle on the Superclass side to denote a SuperClass/Subclass relation.
9
Participation Constraint: Determines whether every member of a superclass must participate as a member of a subclass. Mandatory Optional Disjoint Constraint: Describes the relationship between members of the subclasses and indicates whether it is possible for a member of a superclass to be a member of one or more subclasses. Disjoint: Or Nondisjoint: And
10
4 Possibilities {Mandatory, And} {Mandatory, Or} {Optional, And} {Optional, Or}
11
Aggregation: Represents a “has-a” or “is-part- of” relationship between two entities. Entirely conceptual, only distinguishing the “whole” from the “part” Does not change the diagrammatic meaning or traversal of the relationship Does not link the lifetimes of the “whole” and “part”
12
Use an Open diamond on the “whole” side
13
Composition: A specific form of aggregation that represents an association between entities, where there is a strong ownership and coincidental lifetime between the “whole” and “part”. In a Composite relationship the “whole” is responsible for the disposition of the relationship. The “whole” is responsible for the creation and destruction of its parts. An object may be part of only one composite at a time.
14
Use a filled diamond on the “whole” side
15
By: Bryan Hunwardsen
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.