CH1, CH2, CH3, CH4, CH6 FLASHCARDS

4.0(1)
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/226

flashcard set

Earn XP

Description and Tags

CIS 3060 Database Management Systems, MSU DENVER, Chapters 1, 2, 3, 4, 6

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

227 Terms

1
New cards

Knowledge

The body of information and facts about a specific subject. This term implies familiarity, awareness, and understanding of information as it applies to an environment. A key characteristic with this term is that the new can come from the old.

2
New cards

Information

The result of processing raw data to reveal its meaning. It consists of transformed data and facilitates decision making.

3
New cards

Data Management

A process that focuses on data collection, storage, and retrieval. Common functions include addition, deletion, modification, and listing.

4
New cards

Database Management System (DBMS)

The collection of programs that manages the database structure and controls access to the data stored in the database.

5
New cards

Database

A shared, integrated computer structure that houses a collection of related data. This contains two types of data: end-user data (raw facts) and metadata.

6
New cards

Metadata

Data about data; that is, data about data characteristics and relationships. See also data dictionary.

7
New cards

Data Inconsistency

A condition in which different versions of the same data yield different results.

8
New cards

Single-User Database

A database that supports only one user at a time.

9
New cards

ad hoc query

A “spur-of-the-moment” question.

10
New cards

Data Quality

A comprehensive approach to ensuring the accuracy, validity, and timeliness of data.

11
New cards

Query

A question or task asked by an end user of a database in the form of SQL code. A specific request for data manipulation issued by the end user or the application to the DBMS.

12
New cards

Desktop Database

A single-user database that runs on a personal computer.

13
New cards

Discipline- Specific Database

A database that contains data focused on a specific subject area.

14
New cards

Query Result Set

The collection of data rows returned by a query.

15
New cards

Multiuser Database

A database that supports multiple concurrent users.

16
New cards

Centralized Database

A database located at a single site.

17
New cards

Workgroup database

A multiuser database that usually supports fewer than 50 users or is used for a specific department in an organization.

18
New cards

enterprise database

The overall company data representation, which provides support for present and expected future needs.

19
New cards

Distributed Database

A logically related database that is stored in two or more physically independent sites.

20
New cards

Cloud Database

A database that is created and maintained using cloud services, such as Microsoft Azure or Amazon AWS.

21
New cards

Operational Database

A database designed primarily to support a company’s day-to-day operations. Also known as a transactional database, OLTP database, or production database.

22
New cards

Online Transaction Processing Database (OLTP)

A database designed primarily to support a company’s day-to-day operations. Also known as a transactional database, or production database.

23
New cards

Transactional Database

A database designed primarily to support a company’s day-to-day operations. Also known as a OLTP database, or production database.

24
New cards

General-purpose databases

A database that contains a wide variety of data used in multiple disciplines.

25
New cards

Production Database

A database designed primarily to support a company’s day-to-day operations. Also known as a transactional database, or OLTP database.

26
New cards

Unstructured Data

Data that exists in its original, raw state; that is, in the format in which it was collected. Usually, does not conform to a predefined data model.

27
New cards

Online Analytical Processing (OLAP)

A set of decision support system (DSS) tools that use multidimensional data analysis techniques. This creates an advanced data analysis environment that supports decision making, business modeling, and operations research.

28
New cards

Analytical Database

A database focused primarily on storing historical data and business metrics used for tactical or strategic decision making.

29
New cards

Data Warehouse

An integrated, subject-oriented, time-variant, nonvolatile collection of data that provides support for decision making.

30
New cards

Business Intelligence

A set of tools and processes used to capture, collect, integrate, store, and analyze data to support business decision making.

31
New cards

Structured Data

Data that has been formatted to facilitate storage, use, and information generation in a predefined data model.

32
New cards

NoSQL

A new generation of database management systems that is not based on the traditional relational database model.

33
New cards

Semistructured data

Data that has already been processed to some extent.

34
New cards

Extensible Markup Language (XML)

A meta-language used to represent and manipulate data elements. Unlike other markup languages, this language permits the manipulation of a document’s data elements. It facilitates the exchange of structured documents such as orders and invoices over the Internet.

35
New cards

XML database

A database system that stores and manages semi-structured XML data.

36
New cards

Social Media

Web and mobile technologies that enable “anywhere, anytime, always on” human interactions.

37
New cards

Database Design

The process that yields the description of the database structure and determines the database components. The second phase of the database life cycle.

38
New cards

File

A collection of related records. For example, this might contain data about the students currently enrolled at Gigantic University.

39
New cards

data processing (DP) specialist

The person responsible for developing and managing a computerized file processing system.

40
New cards

Field

A character or group of characters (alphabetic or numeric) that has a specific meaning. Used to define and store data.

41
New cards

Record

A logically connected set of one or more fields that describes a person, place, or thing.

42
New cards

Structural Dependence

A data characteristic in which a change in the database schema affects data access, thus requiring changes in all access programs.

43
New cards

Structural Independence

A data characteristic in which changes in the database schema do not affect data access.

44
New cards

Data Type

Defines the kind of values that can be used or stored. Also, used in programming languages and database systems to determine the operations that can be applied to such data.

45
New cards

Data Independence

A condition in which data access is unaffected by changes in the physical data storage characteristics.

46
New cards

Data Dependence

A data condition in which data representation and manipulation are dependent on the physical data storage characteristics.

47
New cards

Logical Data Format

The way a person views data within the context of a problem domain.

48
New cards

Physical Data Format

The way a computer “sees” (stores) data.

49
New cards

Islands Of Information

In the old file system environment, pools of independent, often duplicated, and inconsistent data created and managed by different departments.

50
New cards

Data Redundancy

Exists when the same data is stored unnecessarily at different places.

51
New cards

Data Integrity

In a relational database, a condition in which the data in the database complies with all entity and referential integrity constraints.

52
New cards

Database System

An organization of components that defines and regulates the collection, storage, management, and use of data in a database environment.

53
New cards

Data Anomaly

A data abnormality in which inconsistent changes have been made to a database. For example, an employee moves, but the address change is not corrected in all files in the database.

54
New cards

Data Dictionary

A DBMS component that stores metadata—data about data. Thus, this contains the data definition as well as their characteristics and relationship. It may also include data that are external to the DBMS. Also known as an information resource dictionary.

55
New cards

Application Programming Interfaces

Software through which applications interact with each other transmitting data, messages, status, etc. Also specifically software through which programmers interact with middleware. An API allows the use of generic SQL code, thereby allowing client processes to be database server-independent.

56
New cards

Query Language

A nonprocedural language that is used by a DBMS to manipulate its data. An example of this type of language is SQL.

57
New cards

Performance Tuning

Activities that make a database perform more efficiently in terms of storage and access speed.

58
New cards

Structured Query Language (SQL)

A powerful and flexible relational database language composed of commands that enable users to create database and table structures, perform various types of data manipulation and data administration, and query the database to extract useful information.

59
New cards

application programming interface (API)

Software through which applications interact with each other transmitting data, messages, status, etc. Also specifically software through which programmers interact with middleware. These allow the use of generic SQL code, thereby allowing client processes to be database server-independent.

60
New cards

Discipline- Specific Database

A database that contains data focused on a specific subject area.

61
New cards

General-Purpose Database

A database that contains a wide variety of data used in multiple disciplines.

62
New cards

Entity

A person, place, thing, concept, or event for which data can be stored. See also attribute.

63
New cards

relationship

An association between entities.

64
New cards

Data Modeling

The process of creating a specific data model for a determined problem domain.

65
New cards

Data Model

A representation, usually graphic, of a complex “real-world” data structure. Used in the database design phase of the Database Life Cycle.

66
New cards

Attribute

A characteristic of an entity or object. These have a name and a data type.

67
New cards

One-to-many (1:M or 1..*) relationship

Associations among two or more entities that are used by data models. In this type of relationship, one entity instance is associated with many instances of the related entity.

68
New cards

Many-to-many (M:N or ..) relationship

Association among two or more entities in which one occurrence of an entity is associated with many occurrences of a related entity and one occurrence of the related entity is associated with many occurrences of the first entity.

69
New cards

Business Rule

A description of a policy, procedure, or principle within an organization. For example, a pilot cannot be on duty for more than 10 hours during a 24-hour period, or a professor may teach up to four classes during a semester.

70
New cards

One-to-one (1:1 or 1..1) relationship

Associations among two or more entities that are used by data models. In this relationship, one entity instance is associated with only one instance of the related entity.

71
New cards

Constraint

A restriction placed on data, usually expressed in the form of rules. For example, “A student’s GPA must be between 0.00 and 4.00.”

72
New cards

Network Model

An early data model that represented data as a collection of record types in 1:M relationships.

73
New cards

Segment

In the hierarchical data model, the equivalent of a file system’s record type.

74
New cards

Hierarchical Model

An early database model whose basic concepts and characteristics formed the basis for subsequent database development. This model is based on an upside-down tree structure in which each record is called a segment. The top record is the root segment. Each segment has a 1:M relationship to the segment directly below it.

75
New cards

Data Manipulation Language (DML)

The set of commands that allows an end user to manipulate the data in the database, such as SELECT, INSERT, UPDATE, DELETE, COMMIT, and ROLLBACK.

76
New cards

Data Definition Language (DDL)

The language that allows a database administrator to define the database structure, schema, and subschema.

77
New cards

Subschema

The portion of the database that interacts with application programs.

78
New cards

Schema

A logical grouping of database objects, such as tables, indexes, views, and queries, that are related to each other. Usually, this belongs to a single user or application.

79
New cards

Relation

A logical construct perceived to be a two-dimensional structure composed of intersecting rows (entities) and columns (attributes) that represents an entity set in the relational model.

80
New cards

Tuple

In the relational model, a table row.

81
New cards

Relational Model

Developed by E. F. Codd of IBM in 1970, the relational model is based on mathematical set theory and represents data as independent relations. Each relation (table) is conceptually represented as a two-dimensional structure of intersecting rows and columns. The relations are related to each other through the sharing of common entity characteristics (values in columns).

82
New cards

Relational Database Management System (RDBMS)

A collection of programs that manages a relational database. This software translates a user’s logical requests (queries) into commands that physically locate and retrieve the requested data.

83
New cards

Entity Relationship Diagram (ERD)

A diagram that depicts an entity relationship model’s entities, attributes, and relations.

84
New cards

Relational Diagram

A graphical representation of a relational database’s entities, the attributes within those entities, and the relationships among the entities.

85
New cards

Entity Relationship Model (ER or ERM)

A data model that describes relationships (1:1, 1:M, and M:N) among entities at the conceptual level with the help of these diagrams.

86
New cards

Entity Instance

A row in a relational table.

87
New cards

Entity Set

A collection of like entities.

88
New cards

Connectivity

The classification of the relationship based on the maximum number of instances of one entity that can be related to an instance of the other entity. Classifications include 1:1, 1:M, and M:N.

89
New cards

Entity Occurrence

A row in a relational table.

90
New cards

Chen Notation

A data model that describes relationships (1:1, 1:M, and M:N) among entities at the conceptual level with the help of ER diagrams.

91
New cards

Crow’s Foot Notation

A representation of the entity relationship diagram that uses a three-pronged symbol to represent the “many” sides of the relationship.

92
New cards

Class Diagram Notation

The set of symbols used in the creation of class diagrams.

93
New cards

Object

An abstract representation of a real-world entity that has a unique identity, embedded properties, and the ability to interact with other objects and itself.

94
New cards

Object-Oriented Database Management System (OODBMS)

Data management software used to manage data in an object-oriented database model.

95
New cards

Semantic Data Model

The first of a series of data models that models both data and their relationships in a single structure known as an object.

96
New cards

object-oriented data model (OODM)

A data model whose basic modeling structure is an object.

97
New cards

Class

A collection of similar objects with shared structure (attributes) and behavior (methods). These encapsulate an object’s data representation and a method’s implementation.

98
New cards

Class Hierarchy

The organization of classes in a hierarchical tree in which each parent class is a superclass and each child class is a subclass. See also inheritance.

99
New cards

Inheritance

In the EERD, the property that enables an entity subtype to inherit the attributes and relationships of the entity supertype. In the object-oriented data model, the ability of an object to inherit the data structure and methods of the classes above it in the class hierarchy. See also class hierarchy.

100
New cards

Method

In the object-oriented data model, a named set of instructions to perform an action. These represent real-world actions. A programmed function within an object used to manipulate the data in that same object.