Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
158 Cards in this Set
- Front
- Back
|
Data Processing System
|
An automated system for processing the data for the records of an organization.
|
|
|
Application Program
|
A computer program that performs a specific task of practical value in a business situation.
|
|
|
Random Access Processing
|
A file access method that provides direct access to a specific record.
|
|
|
Key
|
Data fields that uniquely identify a record in a file.
|
|
|
Information System
|
An automated system which organizes data to produce information.
|
|
|
Management Information System
|
A system that provides information to management.
|
|
|
Data
|
Isolated facts.
|
|
|
Information
|
Organized or summarized data.
|
|
|
Database
|
A collection of interrelated data items that can be processed by one or more application systems.
|
|
|
Database System
|
A database, a database management system, and appropriate hardware and personnel.
|
|
|
Database Management System (DBMS)
|
Systems software that facilitates the management of a database.
|
|
|
Homonym
|
A term that has different meanings in different contexts.
|
|
|
Synonyms
|
Terms that mean the same thing.
|
|
|
Data Model
|
A conceptual method of structuring data.
|
|
|
Hierarchical Model
|
A data model that assumes all data relationships can be structured as hierarchies.
|
|
|
Pointer
|
A physical address which identifies where a record can be found on disk.
|
|
|
Child
|
An "owned" record in a hierarchical relationship.
|
|
|
Parent
|
An "owner" record in a hierarchical relationship.
|
|
|
Network
|
A data relationship in which a record can be owned by records from more than one file.
|
|
|
Client/Server Platform
|
A local area network consisting of client computers which receive services from a server computer.
|
|
|
Database Server
|
A program running on server hardware to provide database services to client machines.
|
|
|
Graphical User Interface (GUI)
|
Screens and functions that provide a graphical means for an end user to access a computer system.
|
|
|
Open Systems
|
The concept of connecting a variety of computer, hardware and software to work in concert to achieve user goals.
|
|
|
Interoperability
|
The state of multiple heterogeneous systems communicating and contributing to completion of a common task.
|
|
|
Metadata
|
Data in the data dictionary which describe the database. "Data about data."
|
|
|
Data view
|
A definition of a restricted portion of the database; also called a view.
|
|
|
Users
|
People who need information from the database to carry out their primary business responsibility.
|
|
|
Practitioners
|
People responsible for the database system and its associated application software.
|
|
|
Procedure
|
Written instructions describing the steps needed to accomplish a given task in a system.
|
|
|
|
|
|
|
Chapter 3 - Database Systems in the Organization
|
|
|
|
Data Integration
|
Combining data for common use.
|
|
|
Electronic Data Processing (EDP)
|
Computer automation of paperwork at the operational level of an organization.
|
|
|
Management Information System (MIS)
|
Automated system focused on information for middle management.
|
|
|
Decision Support System (DSS)
|
Automated system providing strategic information to senior management.
|
|
|
Centralized Database
|
Database physically confined to a single location.
|
|
|
Distributed Database System
|
A database system made of several systems at local sites, connected by communication lines.
|
|
|
Database Planning
|
Strategic effort to determine information needs for an extended period.
|
|
|
Database Development Life Cycle (DDLC)
|
A process for designing, implementing, and maintaining a database.
|
|
|
Database Administration (DBA)
|
Personnel with responsibility for controlling and protecting the database.
|
|
|
Conceptual Database Design
|
Identification of data elements, relationships, and constraints for a database.
|
|
|
Value Constraint
|
A rule defining the permissible values for a specific data item.
|
|
|
Physical Database Design
|
Determination of storage devices, access methods, and indexes for using a database.
|
|
|
Schema
|
A definition of the logical structure of the entire database.
|
|
|
Information Center
|
An area where users have facilities to do their own computing.
|
|
|
Retrieve Only Access
|
Database access with no update allowed.
|
|
|
Data Integrity
|
Accuracy and consistency of data values in the database.
|
|
|
Three-level Architecture
|
Standard database structure consisting of conceptual, external, and internal levels.
|
|
|
Conceptual Level
|
Database structural level defining logical schema of database.
|
|
|
External Level
|
Database structural level defining user views.
|
|
|
Internal Level
|
Database structural level defining physical view of database.
|
|
|
System Development Life Cycle
|
A process for system development.
|
|
|
Function-oriented Approach
|
Views a system from the perspective of the functions it should perform.
|
|
|
Data-oriented Approach
|
Focuses on the analysis of data used by the functions.
|
|
|
Preliminary Planning
|
Planning for a database that occurs during the strategic database planning process.
|
|
|
Feasibility Study
|
Portion of the DDLC that determines technological, operational, and economic feasibility of database.
|
|
|
Technological Feasibility
|
Determination of hardware and software availability for database system.
|
|
|
Operational Feasibility
|
Determination of availability of expertise and personnel needed for the database system.
|
|
|
Economic Feasibility
|
Cost-benefit study of proposed database system.
|
|
|
Requirements Definition
|
Determination of management and functional area information requirements.
|
|
|
Conceptual Design
|
Creation of conceptual-level schema for database.
|
|
|
Database Implementation
|
The steps required to change a conceptual design to a functioning database.
|
|
|
|
|
|
|
Chapter 4
|
Principles of Conceptual Database Design
|
|
|
model
|
representation of reality that only retains selected details
|
|
|
map
|
associate elements of reality with elements of the model
|
|
|
semantic
|
mapping the meanings.
|
|
|
lexical
|
can be printed
|
|
|
abstract
|
can't be printed "person"
|
|
|
surrogate key
|
represents the abstract object
|
|
|
relationship
|
links 2 object sets
|
|
|
cardinality (multiplicity)
|
the max number of instances in one object set that are related to a single instance in the other object set
|
|
|
functional
|
relationship with max cardinality of 1 one way.
|
|
|
key
|
value used to uniquely identify an object every time
|
|
|
Association Class
|
A relationship viewed as a class.
|
|
|
Higher-level Relationship
|
A relationship which involves three or more classes.
|
|
|
Binary Relationship
|
Relationships which involve two classes.
|
|
|
N-ary Relationship
|
A higher-level relationship (involving three or more classes).
|
|
|
Ternary Relationship
|
A higher-level relationship involving three classes.
|
|
|
Data Processing System
|
An automated system for processing the data for the records of an organization.
|
|
|
Application Program
|
A computer program that performs a specific task of practical value in a business situation.
|
|
|
Random Access Processing
|
A file access method that provides direct access to a specific record.
|
|
|
Key
|
Data fields that uniquely identify a record in a file.
|
|
|
Information System
|
An automated system which organizes data to produce information.
|
|
|
Management Information System
|
A system that provides information to management.
|
|
|
Data
|
Isolated facts.
|
|
|
Information
|
Organized or summarized data.
|
|
|
Database
|
A collection of interrelated data items that can be processed by one or more application systems.
|
|
|
Database System
|
A database, a database management system, and appropriate hardware and personnel.
|
|
|
Database Management System (DBMS)
|
Systems software that facilitates the management of a database.
|
|
|
Homonym
|
A term that has different meanings in different contexts.
|
|
|
Synonyms
|
Terms that mean the same thing.
|
|
|
Data Model
|
A conceptual method of structuring data.
|
|
|
Hierarchical Model
|
A data model that assumes all data relationships can be structured as hierarchies.
|
|
|
Pointer
|
A physical address which identifies where a record can be found on disk.
|
|
|
Child
|
An "owned" record in a hierarchical relationship.
|
|
|
Parent
|
An "owner" record in a hierarchical relationship.
|
|
|
Network
|
A data relationship in which a record can be owned by records from more than one file.
|
|
|
Client/Server Platform
|
A local area network consisting of client computers which receive services from a server computer.
|
|
|
Database Server
|
A program running on server hardware to provide database services to client machines.
|
|
|
Graphical User Interface (GUI)
|
Screens and functions that provide a graphical means for an end user to access a computer system.
|
|
|
Open Systems
|
The concept of connecting a variety of computer, hardware and software to work in concert to achieve user goals.
|
|
|
Interoperability
|
The state of multiple heterogeneous systems communicating and contributing to completion of a common task.
|
|
|
Metadata
|
Data in the data dictionary which describe the database. "Data about data."
|
|
|
Data view
|
A definition of a restricted portion of the database; also called a view.
|
|
|
Users
|
People who need information from the database to carry out their primary business responsibility.
|
|
|
Practitioners
|
People responsible for the database system and its associated application software.
|
|
|
Procedure
|
Written instructions describing the steps needed to accomplish a given task in a system.
|
|
|
|
|
|
|
Chapter 3 - Database Systems in the Organization
|
|
|
|
Data Integration
|
Combining data for common use.
|
|
|
Electronic Data Processing (EDP)
|
Computer automation of paperwork at the operational level of an organization.
|
|
|
Management Information System (MIS)
|
Automated system focused on information for middle management.
|
|
|
Decision Support System (DSS)
|
Automated system providing strategic information to senior management.
|
|
|
Centralized Database
|
Database physically confined to a single location.
|
|
|
Distributed Database System
|
A database system made of several systems at local sites, connected by communication lines.
|
|
|
Database Planning
|
Strategic effort to determine information needs for an extended period.
|
|
|
Database Development Life Cycle (DDLC)
|
A process for designing, implementing, and maintaining a database.
|
|
|
Database Administration (DBA)
|
Personnel with responsibility for controlling and protecting the database.
|
|
|
Conceptual Database Design
|
Identification of data elements, relationships, and constraints for a database.
|
|
|
Value Constraint
|
A rule defining the permissible values for a specific data item.
|
|
|
Physical Database Design
|
Determination of storage devices, access methods, and indexes for using a database.
|
|
|
Schema
|
A definition of the logical structure of the entire database.
|
|
|
Information Center
|
An area where users have facilities to do their own computing.
|
|
|
Retrieve Only Access
|
Database access with no update allowed.
|
|
|
Data Integrity
|
Accuracy and consistency of data values in the database.
|
|
|
Three-level Architecture
|
Standard database structure consisting of conceptual, external, and internal levels.
|
|
|
Conceptual Level
|
Database structural level defining logical schema of database.
|
|
|
External Level
|
Database structural level defining user views.
|
|
|
Internal Level
|
Database structural level defining physical view of database.
|
|
|
System Development Life Cycle
|
A process for system development.
|
|
|
Function-oriented Approach
|
Views a system from the perspective of the functions it should perform.
|
|
|
Data-oriented Approach
|
Focuses on the analysis of data used by the functions.
|
|
|
Preliminary Planning
|
Planning for a database that occurs during the strategic database planning process.
|
|
|
Feasibility Study
|
Portion of the DDLC that determines technological, operational, and economic feasibility of database.
|
|
|
Technological Feasibility
|
Determination of hardware and software availability for database system.
|
|
|
Operational Feasibility
|
Determination of availability of expertise and personnel needed for the database system.
|
|
|
Economic Feasibility
|
Cost-benefit study of proposed database system.
|
|
|
Requirements Definition
|
Determination of management and functional area information requirements.
|
|
|
Conceptual Design
|
Creation of conceptual-level schema for database.
|
|
|
Database Implementation
|
The steps required to change a conceptual design to a functioning database.
|
|
|
|
|
|
|
Chapter 4
|
Principles of Conceptual Database Design
|
|
|
model
|
representation of reality that only retains selected details
|
|
|
map
|
associate elements of reality with elements of the model
|
|
|
semantic
|
mapping the meanings.
|
|
|
lexical
|
can be printed
|
|
|
abstract
|
can't be printed "person"
|
|
|
surrogate key
|
represents the abstract object
|
|
|
relationship
|
links 2 object sets
|
|
|
cardinality (multiplicity)
|
the max number of instances in one object set that are related to a single instance in the other object set
|
|
|
functional
|
relationship with max cardinality of 1 one way.
|
|
|
key
|
value used to uniquely identify an object every time
|
|
|
Association Class
|
A relationship viewed as a class.
|
|
|
Higher-level Relationship
|
A relationship which involves three or more classes.
|
|
|
Binary Relationship
|
Relationships which involve two classes.
|
|
|
N-ary Relationship
|
A higher-level relationship (involving three or more classes).
|
|
|
Ternary Relationship
|
A higher-level relationship involving three classes.
|
