M1 Flashcards

1
Q

organized collection of logically related data

A

Database:

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

stored representations of meaningful objects and

event

A

Data:

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

data processed to increase knowledge in the

person using the data

A

Information:

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

data that describes the properties and context

of user data

A

Metadata:

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

All programs maintain metadata for each file they use.

A

Program-Data Dependence.

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

Different systems/programs have separate copies of the same data.

A

Duplication of data.

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

No centralized control of data

A

Limited Data Sharing

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

Programmers must design their own file formats

A

Lengthy Development Times

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

80% of information systems budget

A

Excessive Program Maintenanc

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

Solution to the disadvantages of file processing

A

database

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

A software system that is used to create, maintain, and provide controlled access to user databases

A

Database System Management

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

Graphical system capturing nature and relationship of data

A

Data models

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

high-level entities and relationships for the organization

A

Enterprise Data Model–

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

more detailed view, matching data structure in database or data warehouse

A

Project Data Model–

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

Noun form describing a person, place, object, event, or concept. Composed of attributes

A

entities

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

Between entities. Usually one-to-many (1:M) or many-to-many (M:N

A

Relationships

17
Q

Database technology involving tables (relations) representing entities and primary/foreign keys representing relationship

A

Relational Databases

18
Q

computer-aided software engineering

A

CASE Tools

19
Q

centralized storehouse of metadata

A

Repository–

20
Q

software for managing the database

A

Database Management System (DBMS) –

21
Q

storehouse of the data

A

Database–

22
Q

software using the data

A

Application Programs–

23
Q

text and graphical displays to users

A

User Interface–

24
Q

personnel responsible for maintaining the database

A

Data/Database Administrators–

25
Q

personnel responsible for designing databases and software

A

System Developers–

26
Q

people who use the applications and databases

A

End Users–

27
Q

software using the data

A

Application Programs–

28
Q

text and graphical displays to users

A

User Interface–

29
Q

personnel responsible for maintaining the database

A

Data/Database Administrators–

30
Q

personnel responsible for designing databases and software

A

System Developers–

31
Q

people who use the applications and databases

A

End Users–

32
Q

Detailed, well-planned development process. Time-consuming, but comprehensive. Long development cycle.

A

System Development Life Cycle SLDC

33
Q

Cursory attempt at conceptual data modeling. Define database during the development of the initial prototype. Repeat implementation and maintenance activities with new prototype versions.

A

Rapid application development (RAD) // Prototyping

34
Q

Purpose–preliminary understanding

Deliverable–request for study

Database activity– enterprise modeling and early conceptual data modeling

A

Planning

35
Q

Purpose–thorough requirements analysis and structuring

Deliverable–functional system specifications

Database activity–thorough and integrated conceptual data modeling

A

Analysis

36
Q

Purpose–information requirements elicitation and structure

Deliverable–detailed design specifications

Database activity– logical database design (transactions, forms, displays, views, data integrity and security)

A

Logical Design

37
Q

Purpose–develop technology and organizational specifications

Deliverable–program/data structures, technology purchases, organization redesign

Database activity– physical database design (define database to DBMS, physical data organization, database processing programs)

A

Physical Design

38
Q

Purpose–programming, testing, training, installation, documenting

Deliverable–operational programs, documentation, training materials

Database activity– database implementation, including coded programs, documentation, installation and conversion

A

Implementation