Data Management - Foundations - D426 (4/6)

0.0(0)
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/74

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

75 Terms

1
New cards

Discover entities, relationships, and attributes.(Discovery)

1A. Identify entities, relationships, and attributes in interviews. \n\n1B. Draw ER diagram. \n\n1C. List standard attribute types in glossary. \n\n1D. Document names, synonyms, and descriptions in glossary.

2
New cards

Relationship maximum(Cardinality)

Relationship _______ is the greatest number of instances of one entity that can relate to a single instance of another entity.

3
New cards

unique attribute(Cardinality)

Each value of a ______ attribute describes at most one entity instance.

4
New cards

Determine cardinality(Cardinality)

2A. Determine relationship maxima and minima. \n\n2B. Determine attribute maxima and minima. \n\n2C. Identify unique attributes. \n\n2D. Document cardinality in glossary and, optionally, on ER diagram.

5
New cards

identify(Strong entities)

Identifying attribute values correspond one-to-one to, or ________, entity instances.

6
New cards

strong entity(Strong entities)

A ______ entity has one or more identifying attributes.

7
New cards

Supertype/subtype entities (Supertype & subtype entities)

A ___type entity is a subset of another entity type, called the _____type entity.

8
New cards

partition attribute(Supertype & subtype entities)

Each partitioncorresponds to an optional _________ _________ of the supertype entity.

9
New cards

Create supertype and subtype entities(Supertype & subtype entities)

4A. Identify supertype and subtype entities. \n\n4B. Replace similar entities and optional attributes with supertype and subtype entities. \n\n4C. Identify partitions and partition attributes. \n\n4D. Document supertypes, subtypes, and partitions in glossary and ER diagram.

10
New cards

entity-relationship model (Entities, relationships, and attributes)

An ______-_____________ model is a high-level representation of data requirements, ignoring implementation details.

11
New cards

entity (Entities, relationships, and attributes)

An ______ is a person, place, product, concept, or activity.

12
New cards

relationship (Entities, relationships, and attributes)

A _____________ is a statement about two entities.

13
New cards

attribute (Entities, relationships, and attributes)

An _________ is a descriptive property of an entity.

14
New cards

reflexive relationship(Entities, relationships, and attributes)

A _________ relationship relates an entity to itself.

15
New cards

entity-relationship diagram/ER diagram(Entities, relationships, and attributes)

______-____________ diagram is a schematic picture of entities, relationships, and attributes.

16
New cards

glossary/data dictionary/repository(Entities, relationships, and attributes)

________ , documents additional detail in text format.

17
New cards

entity type(Entities, relationships, and attributes)

An ______ type is a set of things. Ex: All employees in a company.

18
New cards

relationship type(Entities, relationships, and attributes)

A____________ type is a set of related things. Ex: Employee-Manages-Department is a set of (employee, department) pairs, where the employee manages the department.

19
New cards

attribute type (Entities, relationships, and attributes)

An _________ type is a set of values. Ex: All employee salaries.

20
New cards

entity instance(Entities, relationships, and attributes)

An ______ instance is an individual thing. Ex: The employee Sam Snead.

21
New cards

relationship instance(Entities, relationships, and attributes)

A ____________ instance is a statement about entity instances. Ex: "Maria Rodriguez manages Sales.".

22
New cards

attribute instance(Entities, relationships, and attributes)

An _________ instance is an individual value. Ex: The salary $35,000.

23
New cards

Analysis(Entities, relationships, and attributes)

________ develops an entity-relationship model, capturing data requirements while ignoring implementation details.

24
New cards

Logical design(Entities, relationships, and attributes)

________ design converts the entity-relationship model into tables, columns, and keys for a particular database system.

25
New cards

Physical design(Entities, relationships, and attributes)

________ design adds indexes and specifies how tables are organized on storage media.

26
New cards

Analysis steps(Entities, relationships, and attributes)

1. Discover entities, relationships, and attributes \n\n2. Determine cardinality\n3. Distinguish strong and weak entities \n\n4. Create supertype and subtype entities

27
New cards

Logical design steps(Entities, relationships, and attributes)

5. Implement entities \n\n6. Implement relationships \n\n7. Implement attributes \n\n8. Apply normal form

28
New cards

cardinality (Cardinality)

In entity-relationship modeling, ___________ refers to maxima and minima of relationships and attributes.

29
New cards

singular / plural(Cardinality)

A related entity is ________ when the maximum is one and ______ when the maximum is many.

30
New cards

Relationship minimum(Cardinality)

Relationship _______ is the least number of instances of one entity that can relate to a single instance of another entity.

31
New cards

optional / required(Cardinality)

A related entity is ________ when the minimum is zero and ________ when the minimum is one.

32
New cards

Attribute maximum(Cardinality)

Attribute _______ is the greatest number of attribute values that can describe each entity instance. Attribute _______ is usually specified as one (singular) or many (plural).

33
New cards

Attribute minimum(Cardinality)

Attribute _______ is the least number of attribute values that can describe each entity instance. Attribute _______ is usually specified as zero (optional) or one (required).

34
New cards

identifying attribute(Strong entities)

An ___________ attribute is unique, singular, and required.

35
New cards

weak entity / identifying relationship / identifying entity (Weak entities)

A____ entity does not have an identifying attribute. Instead, a ____ entity usually has a relationship, called an identifying relationship, to another entity, called an identifying entity. Cardinality of the identifying entity is 1(1).

36
New cards

Distinguish strong and weak entities. (Strong and weak entities)

3A. Identify strong and weak entities. \n\n3B. Determine the identifying relationship(s) for each weak entity. \n\n3C. Document weak entities and identifying relationships in glossary and ER diagram.

37
New cards

IsA relationship(Supertype & subtype entities)

A supertype entity identifies its subtype entities. The identifying relationship is called an ___ relationship.

38
New cards

Similar entities(Supertype & subtype entities)

_______ entities are entities that have many common attributes and relationships.

39
New cards

partition(Supertype & subtype entities)

A _________ of a supertype entity is a group of mutually exclusive subtype entities.

40
New cards

crow's foot notation(Alternative modeling conventions)

Variations in cardinality conventions are common. One popular convention, called ____'s ____ notation, depicts cardinality as a circle (zero), a short line (one), or three short lines (many). The three short lines look like a bird's foot, hence the name "____'s ____ notation".

41
New cards

subject area(Alternative modeling conventions)

Decompose a complex model into a group of related entities, called a _______ ____.

42
New cards

independent/dependent(Alternative modeling conventions)

Refer to strong entities as ___________ and weak entities as _________.

43
New cards

Unified Modeling Language/UML(Alternative modeling conventions)

_______ ________ ________ is commonly used for software development. Software data structures are similar to database structures, so UML includes ER conventions.

44
New cards

IDEF1X(Alternative modeling conventions)

______ became popular, in part, due to early adoption by the United States Department of Defense.

45
New cards

Chen notation(Alternative modeling conventions)

____ ________ appeared in an early ER modeling paper by Peter Chen. ____ ________ is not standardized but often appears in literature and tools.

46
New cards

Stable (Selecting primary keys)

Primary key values should not change. When a primary key value changes, statements that specify the old value must also change. Furthermore, the new primary key value must cascade to matching foreign keys.

47
New cards

Simple(Selecting primary keys)

Primary key values should be easy to type and store. Small values are easy to specify in an SQL WHERE clause and speed up query processing. Ex: A 2-byte integer is easier to type and faster to process than a 15-byte character string.

48
New cards

Meaningless(Selecting primary keys)

Primary keys should not contain descriptive information. Descriptive information occasionally changes, so primary keys containing descriptive information are unstable.

49
New cards

strong table (Implementing entities)

A strong entity becomes a _____ table. The primary key must be unique and non-NULL, and should be stable, simple, and meaningless. Single-column primary keys are best, but if no such column exists, a composite primary key may have the required properties.

50
New cards

artificial key(Implementing entities)

An__________ key is a single-column primary key created by the database designer when no suitable single-column or composite primary key exists.

51
New cards

subtype table (Implementing entities)

A subtype entity becomes a _______ table .

52
New cards

weak table(Implementing entities)

A weak entity becomes a ____ table.

53
New cards

Implement entities(Implementing entities)

5A. Implement strong entities as tables. \n\n5B. Create an artificial key when no suitable primary key exists. \n\n5C. Implement subtype entities as tables. \n\n5D. Implement weak entities as tables. \n\n5E. Specify cascade and restrict actions for identifying relationships.

54
New cards

Implementing relationships (Implementing relationships)

6A. Implement many-one relationships as foreign key on 'many' side. \n\n6B. Implement one-one relationships as foreign key in table with fewer rows. \n\n6C. Implement many-many relationships as new weak tables. \n\n6D. Specify cascade and restrict rules on foreign keys that implement dependency relationships.

55
New cards

Implement attributes (Implement attributes)

7A. Implement plural attributes as new weak tables. \n\n7B. Specify cascade and restrict rules on new foreign keys in weak tables. \n\n7C. Specify column data types corresponding to attribute types. \n\n7D. Enforce relationship and attribute cardinality with UNIQUE and NOT NULL keywords.

56
New cards

depends on(Functional dependence)

Column A depends on column B means each B value is related to at most one A value.

57
New cards

functional dependence(Functional dependence)

Dependence of one column on another is called __________ dependence.

58
New cards

Multivalued dependence / join dependence (Functional dependence)

__________ dependence and ____ dependence entail dependencies between three or more columns.

59
New cards

Redundancy (Normal forms)

__________ is the repetition of related values in a table.

60
New cards

Normal forms (Normal forms)

______ forms are rules for designing tables with less redundancy.

61
New cards

first normal form (Normal forms)

Every cell of a table contains exactly one value. A table is in _____ normal form when, in addition, the table has a primary key. \n\n\n\nIn a _____ normal form table, every non-key column depends on the primary key \n\nA _____ normal form table has no duplicate rows

62
New cards

second normal form (Normal forms)

A table is in ______ normal form when all non-key columns depend on the whole primary key.

63
New cards

third normal form (Normal forms)

Informally, a table is in _____ normal form when all non-key columns depend on the key, the whole key, and nothing but the key. A formal definition appears elsewhere in this material.

64
New cards

candidate key (Boyce-Codd normal form)

A_________ key is a simple or composite column that is unique and minimal.

65
New cards

Minimal (Boyce-Codd normal form)

_______ means all columns are necessary for uniqueness.

66
New cards

non-key (Boyce-Codd normal form)

A ___-___ column is a column that is not contained in a candidate key.

67
New cards

third normal form (Boyce-Codd normal form)

A table is in _____ normal form if, whenever a non-key column A depends on column B, then B is unique. Columns A and B may be simple or composite.

68
New cards

Boyce-Codd normal form (Boyce-Codd normal form)

A table is in _____-____ normal form if, whenever column A depends on column B, then B is unique. Columns A and B may be simple or composite.

69
New cards

trivial (Boyce-Codd normal form)

When the columns of A are a subset of the columns of B, A always depends on B.These dependencies are called _______.

70
New cards

non-trivial (Boyce-Codd normal form)

A table is in Boyce-Codd normal form if, for all ___-_______ dependencies B → A, B is unique.

71
New cards

Normalization (Applying normal form)

_____________ eliminates redundancy by decomposing a table into two or more tables in higher normal form.

72
New cards

depends on(Applying normal form)

Column A _______ on column B when each B value is related to at most one A value. A and B may be simple or composite columns.

73
New cards

Boyce-Codd normal form (Applying normal form)

In a _____-____ normal form table, if column A depends on column B, then B must be unique.

74
New cards

Denormalization(Applying normal form)

_______________ means intentionally introducing redundancy by merging tables.

75
New cards

Applying normal form(Applying normal form)

8A. Identify dependencies on non-unique columns. \n\n8B. Eliminate redundancy by decomposing tables.\n8C. Consider denormalizing tables in reporting databases.