Chapter 9: Database Management Systems

Question 1

Flat-file Model

Answer 1

Environment in which individual data files are not related to other files

Question 2

Data attribute

Answer 2

Most elemental piece of potentially useful data in the databse

Question 3

Data redundancy

Answer 3

State of data elements being represented in all user files

Question 4

Data storage

Answer 4

Efficient information system that captures and stores data only once and makes this single source available to all users who need it

Question 5

Data updating

Answer 5

Periodic updating of data stored in the files of an organization

Question 6

Currency of information

Answer 6

Problem associated with the flat-file model because of it’s failure to update all the user files affected by a change in status; may result in decisions based on outdated information

Question 7

Task-data dependency

Answer 7

User’s inability to obtain additional information as his or her needs change

Question 8

Database Management System

Answer 8

Software system that controls access to the data resource (program development, backup and recovery, database usage reporting, database access)

Question 9

Hierarchical Model

Answer 9

Database model that represents data in a hierarchical structure and permits only a single parent record for each child record

Question 10

Network Model

Answer 10

Variation of the hierarchical model, allowed two parents for single child record

Question 11

Relational Model

Answer 11

Data model that is more flexible than traditional navigational models, allows users to create new and unique paths through the database to solve a wide range of business problems

Question 12

Navigational Model

Answer 12

Model that possesses explicit links or paths among data elements

Question 13

Structured Model

Answer 13

The data elements for predefined structured paths

Question 14

Users

Answer 14

Individuals who employ systems, receive information, and act on the information received

Question 15

Data definition language

Answer 15

Programming language used to define the physical database to the database management system

Question 16

Internal View

Answer 16

Physical arrangement of records in the database

Question 17

Schema (conceptual view)

Answer 17

Description of entire database represented logically and abstractly

Question 18

User view (subschema)

Answer 18

Set of data that particular user needs to achieve his or her assigned tasks, defines how particular user sees the portion of the database authorized to see

Question 19

Access Method

Answer 19

Technique used to locate records and navigate through the database

Question 20

Data manipulation language

Answer 20

language used to insert special database commands into application programs written in conventional languages, programming language used by particular DBMS to retrieve, process, and store data

Question 21

Structured Query Language

Answer 21

Data processing tool for end users and professional programmers to access data in the database directly without the need for conventional programs

Question 22

Database Administrator

Answer 22

Individual responsible for managing database resource (database planning, design, implementation, operation and maintenance, and change and growth)

Question 23

Data dictionary

Answer 23

Description of every data element in database

Question 24

Physical Database

Answer 24

Lowest level of the database containing magnetic spots on magnetic disks

Question 25

Entity

Answer 25

Anything about which the organization wishes to capture data

Question 26

Data model

Answer 26

Blueprint for ultimately creating the physical database

Question 27

Entity Relationship Diagram

Answer 27

Graphical representation used to depict data model

Question 28

Occurrence

Answer 28

number of instances or records that pertain to a specific entity

Question 29

Attributes

Answer 29

data elements that define an entity

Question 30

Association

Answer 30

Relationship amongst record types

Question 31

Cardinality

Answer 31

Degree of association between two entities, describes the number of possible occurrences in one table that are associated with a single occurrence in a related table

Question 32

Primary Key

Answer 32

Characteristics that uniquely identify each record in the tables

Question 33

Foreign Key

Answer 33

Key that permits the physical connection of logically related tables to achieve the associations described in the data model

Question 34

Anomalies

Answer 34

Negative operational symptoms caused by improperly normalized tables, can cause DBMS processing problems that restrict or even deny users’ access to information they need

Question 35

Update anomaly

Answer 35

Results from data redundancy in an unnormalized table, unintentional updating of data in table

Question 36

Insertion Anomaly

Answer 36

Unintentional insertion of data into the table

Question 37

Deletion Anomaly

Answer 37

Unintentional deletion of data from a table

Question 38

View Modeling

Answer 38

Determines the associations between entities and documents them with an ER diagram, six phases of database design