Module 2: Database Architecture, Models and Diagram Flashcards

1
Q

A Good Data Name Is:

A
  • related to business, not technical, characteristics
  • meaningful and self-documenting
  • unique
  • readable
  • composed of words from an approved list
  • repeatable
  • written in standard syntax
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

word or phrase with specific meaning

A

Term

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

association between two or more terms

A

Fact

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

Guidelines for Good Data Definition

A
  • A concise description of essential data meaning
  • Gathered in conjunction with systems requirements
  • Accompanied by diagrams
  • Achieved by consensus, and iteratively
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

person, place, object, event, concept (often corresponds to a row in a table)

A

Entity Instance

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

collection of entities (often corresponds to a table)

A

Entity Type

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

link between entities (corresponds to primary key-foreign key equivalences in related tables)

A

Relationship Instance

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

category of relationship… link between entity types

A

Relationship Type

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

properties or characteristics of an entity or relationship type (often corresponds to a field in a table)

A

Attributes

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

a special entity that is also a relationship

A

Associative

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

specify number of entity types involved

A

Relationship Degrees

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

specify how many of each entity type is allowed

A

Relationship Cardinalities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  • are statements that define or constrain some aspect of the business
  • are derived from policies, procedures, events, functions
A

Business Rules

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

Business rules assert _____.

A

business structure

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

Business rules are automated through _____.

A

DBMS software

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

A Good Business Rule

A
  • declarative
  • precise
  • atomic
  • consistent
  • expressible
  • distinct
  • business-oriented
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

what, not how

A

Declarative

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

clear, agreed-upon meaning

A

Precise

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

one statement

A

Atomic

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

internally and externally

A

Consistent

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

structured, natural language

A

Expressible

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

non-redundant

A

Distinct

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

understood by business people

A

Business-oriented

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

a person, a place, an object, an event, or a concept in the user environment about which the organization wishes to maintain data

A

Entity

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

a collection of entities that share common properties or characteristics

A

Entity Type

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

a single occurence of an entity type

A

Entity Instance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q
  • exists independently of other types of entities

- has its own unique identifier

A

Strong Entity

28
Q

Strong entity has its own unique identifier underline with _____.

A

single line

29
Q
  • dependent on a strong entity (identifying owner)… cannot exist on its own
  • does not have a unique identifier (only a partial identifier)
A

Weak Entity

30
Q

Weak entity box and partial identifier have _____.

A

double lines

31
Q

Identifier is also primary called _____/

A

Primary Key

32
Q

links strong entities to weak entities

A

Identifying Relationship

33
Q

property or characteristic of an entity or relationship type

A

Attribute

34
Q

Classification of Attrubutes

A
  • Required vs Optional Attributes
  • Simple vs Composite Attribute
  • Single-Valued vs Multivalued Attribute
  • Stored vs Derived Attributes
  • Identifier Attributes
35
Q

must have a value for every entity (or relationship) instance with which it is associated

A

Required

36
Q

may not have a value for every entity (or relationship) instance with which it is associated

A

Optional

37
Q

an attribute that has meaningful component parts (attributes)

A

Composite Attribute

38
Q

may take on more than one value for a given entity (or relationship) instance

A

Multivalued

39
Q

values can be calculated from related attribute values (not physically stored in the database)

A

Derived

40
Q

is saved into the database

A

Multivalued Attributes

41
Q

is not saved into the database because its values may change over time

A

Derived Attributes

42
Q

an attribute (or combination of attributes) that uniquely identifies individual instances of an entity type

A

Identifier (Key)

43
Q

an attribute that could be a key… satisfies the requirements for being an identifier

A

Candidate Identifier

44
Q

one attribute only

A

Simple Identifier

45
Q

two or more identifier attributes

A

Composite Identifier

46
Q

Standard Format for Naming Attributes

A

[Entity type name {]Qualifier]}] Class

47
Q

is modeled as lines between entity types

A

Relationship Type

48
Q

two entities can have more than one type of relationship between them

A

Multiple Relationships

49
Q

combination of relationship and entity

A

Associative Entity

50
Q

the instance is between specific entity instances

A

Relationship Instance

51
Q

is the number of entity types that participate in it

A

Degree of a Relationship

52
Q

one entity related to another of the same entity type

A

Unary

53
Q

entities of two different types related to each other

A

Binary

54
Q

entities of three different types related to each other

A

Ternary

55
Q

each entity in the relationship will have exactly one related entity

A

One-to-One

56
Q

an entity on one side of the relationship can have many related entities, but an entity on the other side will have a maximum of one related entity

A

One-to-Many

57
Q

entities on both sides of the relationship can have many related entities on the other side

A

Many-to-Many

58
Q

can have attributes of its own

A

A Relationship

59
Q

the number of instances of one entity that can or must be associated with each instance of another entity

A

Cardinality Constraints

60
Q

Minimum cardinality if zero

A

Optional

61
Q

Minimum cardinality if one or more

A

Mandatory

62
Q

Maximum cardinality

A

the maximum number

63
Q
  • an entity that has attributes

- a relationship that link entities together

A

Associative Entities

64
Q

is like a relationship with an attribute, but it is also considered to be an entity in its own right

A

Associative Entity

65
Q

a time value that is associated with a data value, often indicating when some event occurred that affected the data value

A

Time Stamp