Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4- 1 EER stands for Enhanced ER or Extended ER EER Model Concepts Includes all modeling concepts.

Slide 4- 1Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

EER stands for Enhanced ER or Extended ER EER Model Concepts

Includes all modeling concepts of basic ER Additional concepts:

subclasses/superclasses specialization/generalization categories (UNION types) attribute and relationship inheritance

These are fundamental to conceptual modeling The additional EER concepts are used to model applications

more completely and more accurately

Chapter 2: Enhanced Entity Relationship Modeling

Slide 4- 2Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Subclasses and Superclasses (1) EER diagrams extend ER diagrams to represent these additional

subgroupings, called subclasses or subtypes Also called IS-A relationships

Slide 4- 3Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Specialization (1)

Specialization is the process of defining a set of subclasses of a superclass

The set of subclasses is based upon some distinguishing characteristics of the entities in the superclass Example: {SECRETARY, ENGINEER, TECHNICIAN}

is a specialization of EMPLOYEE based upon job type. May have several specializations of the same

superclass Attributes of a subclass are called specific or local

attributes.

Slide 4- 4Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Representing Specialization in EER Diagrams

Slide 4- 5Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Specialization (2)

Slide 4- 6Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Generalization

Several classes with common features are generalized into a superclass;

Slide 4- 7Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Constraints on Specialization and Generalization (1)

If we can determine exactly those entities that will become members of each subclass by a condition, the subclasses are called predicate-defined (or condition-defined) subclasses

Slide 4- 8Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Constraints on Specialization and Generalization (2)

Two basic constraints can apply to a specialization/generalization:

Disjointness Constraint: Completeness Constraint:

Hence, we have four types of specialization/generalization: Disjoint, total Disjoint, partial Overlapping, total Overlapping, partial

Note: Generalization usually is total because the superclass is derived from the subclasses.

Slide 4- 9Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Example of disjoint partial Specialization

Slide 4- 10Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Example of overlapping total Specialization

Slide 4- 11Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Specialization/Generalization Hierarchies, Lattices & Shared Subclasses (1)

A subclass may itself have further subclasses specified on it forms a hierarchy or a lattice

Hierarchy has a constraint that every subclass has only one superclass (called single inheritance); this is basically a tree structure

In a lattice, a subclass can be subclass of more than one superclass (called multiple inheritance)

Slide 4- 12Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Shared Subclass “Engineering_Manager”

Slide 4- 13Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Specialization / Generalization Lattice Example (UNIVERSITY)

Slide 4- 14Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Categories (UNION TYPES) (1)

In some cases, we need to model a single superclass/subclass relationship with more than one superclass

Superclasses can represent different entity types Such a subclass is called a category or UNION TYPE

Slide 4- 15Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Unions vs Shared Sub Class

Slide 4- 16Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Formal Definitions of EER Model (1)

Specialization Z: Z = {S1, S2,…, Sn} is a set of subclasses with same superclass G; hence, G/Si is a superclass relationship for i = 1, …., n.

G is called a generalization of the subclasses {S1, S2,…, Sn} Z is total if we always have:

S1 ∪ S2 ∪ … ∪ Sn = G; Otherwise, Z is partial.

Z is disjoint if we always have: Si ∩ S2 empty-set for i ≠ j;

Otherwise, Z is overlapping. Category or UNION type T

A class that is a subset of the union of n defining superclasses D1, D2,…Dn, n>1:

T ⊆ (D1 ∪ D2 ∪ … ∪ Dn)

Slide 4- 17Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

UML Example for Displaying Specialization / Generalization

Slide 4- 18Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Ontologies

Use conceptual modeling and other tools to develop “a specification of a conceptualization” Specification refers to the language and vocabulary

(data model concepts) used Conceptualization refers to the description (schema)

of the concepts of a particular field of knowledge and the relationships among these concepts

Many medical, scientific, and engineering ontologies are being developed as a means of standardizing concepts and terminology