Enhanced Entity-Relationship (EER) Model Flashcards

1
Q

Additional semantic data modeling concepts incorporated into ER model to
reflect the data properties and constraints more precisely

A

Enhanced Entity-Relationship (EER) Model
also called Extended ER Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

A subset of an entity set with a meaningful (or an explicit need for) subgrouping

A

Subclass (or Subtype)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Entity set from which the subgroupings were formed

A

Superclass (or Supertype)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Also called superclass/subclass or supertype/subtype relationship

Also called an IS-A (or IS-AN) relationship

A

Class/Subclass Relationship

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Subclasses inherit all the
attributes and relationship types of their superclass(es)

A

Inheritance (or Type Inheritance)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Process of defining a set of
subclasses of an entity type

Maximizes the difference between the set of subclasses

Used in top-down conceptual
refinement process

A

Specialization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Process of defining a generalized entity type from given entity types

Suppresses (minimizes) the
differences between entity types by identifying their common features

Used in bottom-up conceptual
synthesis process

A

Generalization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Specialization vs Generalization

A

Specialization starts with a superclass, and defining a set of subclasses from it. Generalization on the other hand starts with specialized entity types and defining a generalized entity type (Superclass) from it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Why include Class/Subclass Relationships?

A
  1. Certain attributes may apply to some but not all entities of the superclass entity type
  2. Some relationship types may be participated in only by entities that are members of the
    subclass
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Subclass membership can be determined by placing a condition on the value
of some attribute of the superclass

Defining predicate is written next to the line connecting subclass to circle

A

Predicate-Defined Subclasses
(Condition-defined subclasses)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Subclass membership condition determined by the same attribute of the superclass

A

Attribute-Defined Subclasses

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Subclass membership is determined by the (would-be) database users

A

User-Defined Subclasses

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Constraints (on Specialization/Generalization)

A

Disjointness
Completeness (Totalness)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Uses the circle notation to indicate type: disjoint (d) or overlapping (o)

A

Disjointness

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Entity can be a member of at
most one of the subclasses of the specialization

A

Disjoint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Entity can be a member of multiple subclasses of the specialization

A

Overlapping

17
Q

Similar to the Participation constraint on relationship types but on the specialization context

A

Completeness

18
Q

Specifies that every entity in the
superclass must be a member of at least one subclass in the
specialization

A

Total Specialization

19
Q

Allows an entity not to belong to any of the subclasses

A

Partial Specialization

20
Q

TRUE OR FALSE:

Deleting an attribute from a superclass implies that it is automatically deleted
from all subclasses to which it belongs

21
Q

Every subclass participates in only one class/subclass relationship (Only single inheritance would exist)

A

Specialization Hierarchy

22
Q

A subclass can be a subclass in more than one class/subclass relationship (Multiple inheritance would occur)

A

Specialization Lattice

23
Q

Subclass that represents a collection of entities from different entity types

Has 2 or more superclasses that may represent collections of entities from
distinct entity types

A

Union Type (or Category)

24
Q

Union Type vs Shared Subclass

A

Shared subclass is the subset of the intersection of the entity sets, whereas a union type is the union of the entity sets

25
Holds the union of all entities in its superclasses
Total
26
Generalized Superclass vs Union Type
All subclass of a generalized superclass is an instance of it. Contrary, not all instance of entities forming a union type is part of it. (ie. Some cars & some trucks are registered vehicle but not necessarily all, where as all cars and trucks are vehicle)
27
Abstraction concept for building composite objects from their component objects, Combining objects that are related by a particular relationship instance into a higher-level aggregate object (which may be related to another object)
Aggregation
28
TRUE or FALSE Union types should generally be avoided unless the situation definitely warrants this type of construct
TRUE
29
TRUE or FALSE The choice of disjoint/overlapping and total/partial constraints on specialization/generalization is driven by the rules in the miniworld being modeled. If not specified, default would be disjoint and total.
FALSE. default is overlapping and partial
30