AIS 9 Flashcards

1
Q

A specific data file was created for each application ​

A

File-oriented processing

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

Create a single data repository to support numerous applications.​

A

Data-oriented processing

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

creates excessive storage costs of paper documents and/or magnetic form​

A

Data Storage

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

any changes or additions must be performed multiple times​

A

Data Updating

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

potential problem of failing to update all affected files​

A

Currency of Information

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

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

A

Task-Data Dependency

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

Data is stored only once, eliminating data redundancy and reducing storage costs.​

A

No data redundancy

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

Because data is in only one place, it requires only a single update, reducing the time and cost of keeping the database current.​

A

Single update

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

A change to the database made by any user yields current data values for all other users.​

A

Current values

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

As users’ information needs expand, the new needs can be more easily satisfied than under the flat-file approach. ​

A

Task-data independence

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

stands between the user and the database per se.​

A

The database management system (DBMS)

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

user created applications​

A

Program Development

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

copies database​

A

Backup and Recovery

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

captures statistics on database usage (who, when, etc.)​

A

Database Usage Reporting

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

authorizes access to sections of the database​

A

Database Access

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

makes the presence of the DBMS transparent to the user​

A

User Programs

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

allows authorized users to access data without programming​

A

Direct Query

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

is a programming language used to define the database per se. ​

It identifies the names and the relationship of all data elements, records, and files that constitute the database.​

A

DDL

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

physical arrangement of records (1 view)​

A

Internal view

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

representation of database (1 view)​

A

Conceptual view (schema)

21
Q

the portion of the database each user views (many views) ​

A

User view (subschema)

22
Q

is the proprietary programming language that a particular DBMS uses to retrieve, process, and store data to / from the database.​

A

Data Manipulation Language (DML)​

23
Q

The query capability permits end users and professional programmers to access data in the database without the need for conventional programs.​

A

Query Language

24
Q

is a fourth-generation language that has emerged as the standard query language.​

A

IBM’s structured query language (SQL)

25
Adopted by ANSI as the standard language for all relational databases​
IBM’s structured query language (SQL)
26
Refers to the particular method used to organize records in a database​ A.k.a. “logical data structures”​
Database Conceptual Models​
27
portrays data in the form of two dimensional ‘tables’.​
The Relational Model​
28
is based on the relational algebra functions of restrict, project, and join.​
Relational model
29
the labeled line connecting two entities or tables in a data model Describes the nature of the between them ​ Represented with a verb, such as ships, requests, or receives​
Association
30
the degree of association between two entities​ The number of possible occurrences in one table that are associated with a single occurrence in a related table​ Used to determine primary keys and foreign keys​
Cardinality
31
A new item cannot be added to the table until at least one entity uses a particular attribute item.​
Insertion Anomaly
32
If an attribute item used by only one entity is deleted, all information about that attribute item is lost.​
Deletion Anomaly
33
A modification on an attribute must be made in each of the rows in which the attribute appears.​
Update Anomaly
34
Anomalies can be corrected by creating additional
relational tables
35
users can form ad hoc relationships​
Very flexible
36
A process which systematically splits unnormalized complex tables into smaller tables
The Normalization Process​
37
can generate conflicting and obsolete database values.​
Update anomalies
38
can result in unrecorded transactions and incomplete audit trails.​
Insertion anomalies
39
can cause the loss of accounting records and the destruction of audit trails.​
Deletion anomalies
40
should understand the data normalization process and be able to determine whether a database is properly normalized.​
Accountants
41
is organized around several information processing units (IPUs) distributed throughout the organization. ​
Distributed Data Processing (DDP)​
42
The data is retained in a central location. ​ Remote IPUs send requests for data.​ Central site services the needs of the remote IPUs.​ The actual processing of the data is performed at the remote IPU.​
Centralized Databases in DDP Environment​
43
Occurs in DDP with a centralized database​ During transaction processing, data will temporarily be inconsistent as records are read and updated. ​
Data Currency​
44
procedures are necessary to keep IPUs from reading inconsistent data and from writing over a transaction being written by another IPU.​
Database lockout
45
Splits the central database into segments that are distributed to their primary users​
Distributed Databases: Partitioning​
46
Occurs when multiple sites lock each other out of data that they are currently using ​ One site needs data locked by another site.​
The Deadlock Phenomenon​
47
The duplication of the entire database for multiple IPUs​ Effective for situations with a high degree of data sharing, but no primary user​ Supports read-only queries​ Data traffic between sites is reduced considerably.​
Distributed Databases: Replication​
48
is the presence of complete and accurate data at all IPU sites.
Database concurrency
49
is used to serialize transactions.​ Prevents and resolves conflicts created by updating data at various IPUs​
Time stamping