Entity-Relationship (ER Modeling) Flashcards

1
Q

Database Design Process

A

Requirements Collection & Analysis
Functional & Data Requirements
Conceptual Design
Conceptual Schema
Logical Design
Physical Design

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

Database designers interview prospective database users to understand and document the data requirements

A

Requirements Collection &
Analysis

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

Output of the previous step but we will focus on Data Requirements part of the process

A

Functional & Data Requirements

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

Enables database designers to concentrate on specifying the properties of the data without being too concerned with storage and implementation details

A

Conceptual Design

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

Output of Conceptual Design

Concise description of the data requirements and includes detailed descriptions of the entity types, relationships, and constraints

A

Conceptual Schema

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

Conceptual data model transformed into representational (implementation) data model

A

Logical Design

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

Internal storage structures, file organizations, indexes, access paths, and other physical design parameters are specified

A

Physical Design

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

Popular high-level conceptual data model

Describes data as entities, relationships, and attributes

A

Entity-Relationship (ER) Model

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

Thing or object in the real world with an independent existence

A

Entity

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

May be physical existence (e.g. car, employee, student)

May be conceptual existence (e.g. job, course)

Has Attributes

A

Entity

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

A particular property that describes an entity

A

Attribute

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

Entity vs Entity Type vs Entity Set

A

Entity - Thing or object in real world

Entity Type - Defines a collection or set of entities that have the same attributes. Describes the schema for a set of entities that share the same structure

Entity Set - Collection of all entities of a particular entity type in the database at any point in time Also called entity collection

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

Has 1 or more key attributes (Represented as a regular entity using a rectangle)

A

Strong Entity Type

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

Has no key attributes, normally has a partial key and is represented using double rectangles

A

Weak Entity Type

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

Types of Attributes

A

Atomic vs Composite
Single-Valued vs Multivalued
Derived vs Stored
Complex
Key
Partial Key
Relationship Attributes

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

Can be divided into smaller subparts which represent more basic attributes with independent meanings

ex: Name broken down to Fname, Lname, MI

A

Composite Attributes

17
Q

Not divisible

A

Atomic or Simple Attributes

ex: Age

18
Q

Has single value for a particular
entity

A

Single-valued

19
Q

Can have a set of values for the same entity

May have lower and upper bounds to constrain the number of values allowed for each individual entity

Represented by double ovals

A

Multivalued Attribute

20
Q

Value determined using other attributes or properties (e.g. count)

Represented by dashed oval

A

Derived Attribute

21
Q

Opposite of derived attribute

A

stored attribute

22
Q

Nesting of composite and/or multivalued attributes

A

Complex Attributes

23
Q

Attribute whose values are distinct for each individual entity in the entity set

Attribute name underlined with a solid line

A

Key Attribute (No primary key concept yet in ER modeling)

24
Q

TRUE OR FALSE:

Several attributes can (together) form a key; Use composite attribute and designate it as key

25
Attribute that can uniquely identify weak entities that are related to the same owner entity Attribute name underlined with a broken line
Partial Key (discriminator)
26
Defines a set of associations (relationship set) among entities from the involved entity types
Relationship Type
27
In ER diagrams, ___________________ are displayed as diamond-shaped boxes
relationship types
28
Number of participating entity types
Relationship Degree (2 = binary, 3 = ternary)
29
Relationship Constraints
Cardinality Ratio (1:1, 1:N, M:N) Participation (Total and Partial)
30
Specifies the maximum number of relationship instances that an entity can participate in. Can be 1:1 (one-to-one), 1:N (one-to-many), N:1 (many-to-one), and M:N (many-to-many)
Cardinality Ratio
31
Specifies whether the existence of an entity depends on its being related to another entity via the relationship type Specifies the minimum number of relationship instances that each entity can participate in
Participation (minimum cardinality constraint)
32
Attributes recorded when the relationship is initiated between participating entities
Relationship Attributes
33
Migration Rules for Relationship Attributes
M:N - attach to relation 1:N - migrate to N side 1:1 - check for participation if Total: Total - either side if Partial: Partial - attach to relation if Partial:Total - migrate to Total Side
34
TRUE OR FALSE: Relationship types involving a weak entity type will also be weak (represented by single diamond)
FALSE. Represented by Double Diamonds
35
TRUE or FALSE Participation constraint of the weak entity type will always be Total
TRUE
36
Min-max Notation
Attaches the min and max number of participation in a relationship. min valued 1 = total participation min at 0 = partial participation (can be confusing as positioning of **cardinality** is flipped compared to ER Model)
37
TRUE or FALSE An attribute that exists in several entity types may be elevated or promoted to an independent entity type
True
38
TRUE or FALSE An entity type with a single attribute and related to only one other entity may be reduced or demoted to an attribute
True
39