EER modeling Flashcards

(34 cards)

1
Q

taking a ________ to modeling data and relationships in a business process is important because of

A

standardized approach, the complexity involved

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

enhanced ER diagram

A

ER diagram that shows subtypes and supertypes of entities and identifies relationships between them

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

supertype

A

entity type that includes distinct subtypes that needs to be represented in data model

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

subtype

A

subgrouping of entities in an entity type that is meaningful to org and shares common attributes/relationships distinct from other subgroups

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

how to show subtype and supertype on EER diagram

A
  • subtypes are like branches under supertype (connected by circle under subtype)
  • supertype contains all attributes shared by all subtypes
  • subtypes only contain additional attributes that are unique to them
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

example of sub and supertypes

A

supertype: employee, all entity instances have employee ID, name, address, and date hired

subtypes: hourly (hourly rate attribute), salaried (annual salary and stock option attributes), consultant (contract number and billing rate attributes)

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

first steps to EER diagram

A
  • identify a set of entities that share a set of common attributes
  • attempt to identify supertype with maximum number of common attributes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

relationships at the supertype level indicate that

A

all subtypes will participate in the relationship

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

if a relationship is shown at the subtype level

A

only instances part of that subtype participate in relationship

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

2 processes for identifying supertypes and subtypes

A

generalization and specialization

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

generalization

A

process of minimizing the differences between entities by identifying their common features and aggregating them into a supertype, with subtypes for leftover attributes

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

generalization is a

A

bottom-up approach (creates smaller number of entity types from a larger number)

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

potential downside of generalization

A

being too general and having too few entity types, leaving out important details

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

specialization

A

identify relevant differences between entities and splitting them into necessary subtypes

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

specialization is a

A

bottom-down approach

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

potential byproduct of generalization

A

realizing an entity had no particular distinguishing characteristics and has no need to be a subtype

17
Q

subtype discriminator

A

attribute of supertype whose values determine target subtype

18
Q

example of subtype discriminator

A

attribute Employee_type can be H, S, or C, each representing 3 subtypes of employee supertype

19
Q

why use subtype discriminator

A

speed up data retrieval if there are large number of subtypes

20
Q

constraints are

A

intuitive, help us manifest business rules and incorporate them into EER design

21
Q

participation constraint

A

dictate whether every member of superclass must participate as a member of a subclass

22
Q

disjoint constraints

A

define whether it is possible for an instance of a superclass to be a member of one or more subclasses simultaneously

23
Q

disjoint rule

A

disjoint constraint specifies that if subtypes of specialization are disjoint then an entity can be a member of only one subtype

24
Q

non-disjoint (overlap) rule

A

if subtypes of specialization are not disjoint then an entity may be a member of more than one subtype

25
represent disjoint rule
circle with d inside connected to rectangle, multiple subtypes connected to circle with curve on line
26
represent overlap rule
circle with o inside connected to rectangle, multiple subtypes connected to circle with curve on line
27
participation constraints addresses the question
does an instance of a supertype have to be a member of at least one of the subtypes or not?
28
total specialization
every instance of supertype has to belong to a subtype
29
partial specialization
every entity in supertype does not need to be in any subtype
30
representation of total specialization
double line from entity to circle with letter inside
31
total and disjoint constraint combination
- double line, d in circle - supertype entity must also be exactly one of the subtypes
32
total and overlapping constraint combination
- double line, o in circle - supertype entity must be at least one of the subtypes
33
partial and disjoint constraint combination
- single line, d in circle - if supertype entity is part of subtype, it must be a part of exactly one of them
34
partial and overlapping constraint combination
- single line, o in circle - supertype entity can be a part of some, all, or none of the subtypes