Chapter 13 Flashcards

1
Q

Cornerstone of data design

A

Store data once

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

Data storage

A
  • Data must be available when the user wants to use it
  • Data must be accurate and consistent
  • Efficient storage of data as well as efficient updating and retrieval
  • Necessary that information retrieval is purposeful
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Data storage approaches

A
  1. Store data in individual files
    - Each unique to particular application
  2. Store data in database
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Define database

A

A formally defined and centrally controlled store of data intended for use in many different applications

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

Effectiveness objectives of the database

A
  • Ensure that data can be shared among users for a variety of applications
  • Maintaining data that is accurate and consistent
  • Data required for current and future applications will be readily available
  • Allow the database to evolve as the needs of the user grows
  • Allow users to construct their personal view of the data without concern for the way that data is physically stored
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Data vs Metadata

A

Data
- collected about people, objects, or events in reality and eventually stored in a file or database

Metadata
- information that describes data

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

Entities

A
  • Any person, object or event about which someone chooses to collect data
  • Can be a person, place or thing
  • May be an event or unit of time
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Entity consists of rows called

A

Records
A record consists of properties of the entity (–> attributes)

Specific record is an instance of the entity

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

Relationships

A

Used to link data entries

  • one to one
  • one to many
  • one to many (mandatory on many side)
  • one to many (optional on many side)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Key properties

A
  • Uniquely identify records
  • Are dataless
  • Never null
  • Never change
  • Can be used in combination
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

File types

A
  1. Master file
  2. Table file
  3. Transaction file
  4. Report file
    o Used when necessary to print report and no printer is available
    o Useful as users can take files to other computer systems and output to
    specialty devices
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Master file

A
  • Contain records for a group of entities

- Contain all information about a data entity

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

Table file

A
  • Contain data used to calculate more data or performance measures
  • Usually read-only by program
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Report file

A
  • Used when necessary to print report and no printer is available
  • Useful as users can take files to other computer systems and output to specialty devices
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Relational Databases

A
  • Databases are intended to be shared by many users

- In relational data structures, data is stored in many tables

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

3 structures for storing database files

A
  1. Relational database structures
  2. Hierarchical database structures
  3. Network database structures
17
Q

Optionalities

A
  • Used to refine Entity- Relationship diagram
  • Enforce specific business rules pertaining to the data
  • Once optionalities are added, the diagram is called an Extended Entity-
    Relationship Diagram (EERD)