chapter 8-14 Flashcards

1
Q

data modeling

A

a technique for organizing and documenting a systems data.

sometimes called database modeling

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

entity relationship diagram

A

a data model utilizing several notations to depict data in terms of the entities and relationships described by that data

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

entity

A

person, place, thing, etc that the business needs to capture and store data

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

attribute

A

a descriptive property or characteristic of an entity

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

compound attribute

A

an attribute that consists of other attributes

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

attribute value

A

the value of each attribute should be defined in:

data type, domain, default value

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

key

A

an attribute, or group of attributes, that assumes a unique value for each entity instance

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

concatenated key

A

group of attributes that uniquely identifies an instance

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

candidate key

A

an attribute that uniquely identifies an instance

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

primary key

A

a candidate key used to uniquely identify a single entity instance

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

cardinality

A

the minimum and maximum number of occurrences of one entity that may be related to a single occurrence of the other entity

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

degree

A

the number of entities that participate in the relationship

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

unary relationship

A

a relationship between different instances of the same entity

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

binary relationship

A

a relationship between two entities

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

ternary relationship

A

a relationship between three entities

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

associative entity

A

an entity that inherits its primary key from more than one other entity

17
Q

foreign key

A

primary key of an entity that is used in another entity to identify instances of a relationship

18
Q

what is a good data model?

A

a good data model is…

simple, non redundant, flexible and adaptable to future needs

19
Q

data analysis

A

a technique used to improve a data model for implementation as a database

20
Q

normalization

A

a data analysis technique that organizes data attributes such that they are grouped to form non redundant, stable, and adaptive entities

21
Q

1NF

A

entity whose attributes have only one value for a single instance of that entity

22
Q

2NF

A

entity whose non primary key attributes are dependent on the full primary key

no partial dependencies on a composite primary key

23
Q

partial dependency

A

when a non key attribute is determined by a part but not the whole of a composite primary key

24
Q

3NF

A

entity whose non primary key attributes are not dependent on any other non primary key attributes

no transitive dependency

25
Q

transitive dependency

A

when a non key attribute determines another non key attribute

26
Q

method for database design

A
  1. review the logical data model
  2. create a table for each entity
  3. create fields for each attribute
  4. designate foreign keys for relationships
  5. define data types, sizes, null settings, domains, and default value for each attribute
  6. evaluate database integrity
27
Q

key integrity

A

every table should have a primary key

28
Q

domain integrity

A

appropriate controls must be designed to ensure that no field takes on an inappropriate value

ex) valid date

29
Q

referential integrity

A

ensures that a foreign key value in one table has a matching primary key value in the related table