History and Concepts of Database Management Systems

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/42

flashcard set

Earn XP

Description and Tags

A complete set of vocabulary flashcards covering the history, core concepts, database types, ACID properties, and file system anomalies from the DBMS lecture.

Last updated 1:35 AM on 8/25/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

43 Terms

1
New cards

Integrated Data Store (IDS)

First general-purpose DBMS created by Charles William Bachman III at General Electric; introduced the Network Data Model and was standardized by CODASYL.

2
New cards

Information Management System (IMS)

A database management system developed by IBM that used the Hierarchical Data Model.

3
New cards

Relational Data Model

A database model proposed by Edgar F. Codd that became the foundation of modern database systems.

4
New cards

CODASYL

Conference on Data Systems Languages; standardized the Integrated Data Store (IDS).

5
New cards

Data

Raw facts that have not yet been processed.

6
New cards

Information

Processed data that has meaning.

7
New cards

Knowledge

The understanding and application of information.

8
New cards

Data Management

A discipline that focuses on the proper generation, storage, and retrieval of data.

9
New cards

Database

A shared, integrated computer structure that stores a collection of end-user data and metadata.

10
New cards

End-user data

Raw facts of interest to the end-user, representing the actual content created or gathered by the user.

11
New cards

Metadata

Data about data, through which end-user data are integrated and managed; describes contextual details of content.

12
New cards

Database Management System (DBMS)

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

13
New cards

Single user database

A database that supports one user at a time, usually running on a personal device; also called a Desktop Database.

14
New cards

Multi user database

A database that supports multiple users at the same time (fewer than 50 users).

15
New cards

Centralized database

A database that supports data located at a single site.

16
New cards

Decentralised database

A database where every node makes its own decision, such as Bitcoin.

17
New cards

Distributed database

A database that supports data distributed across different locations but works as one system.

18
New cards

Operational Database

A database used for day-to-day business operations; also known as a Transactional Database or Production Database.

19
New cards

Data Warehouse

A database used for storing data for analysis, generating information, and decision-making.

20
New cards

Unstructured data

Data in their raw state.

21
New cards

Structured data

A fully structured data resulting from formatting unstructured data.

22
New cards

Semistructured data

Structured data that isn't fully structured yet.

23
New cards

Database design

The process of creating the structure of a database so that it can properly store and manage data according to user requirements.

24
New cards

Manual File System

Traditional paper-based storage system using filing cabinets, paper records, and folder systems.

25
New cards

Computerized File System

A computer-based storage and retrieval system.

26
New cards

Field

A character or group of characters that has a specific meaning.

27
New cards

Record

A collection of related fields that describe a person, thing, or place.

28
New cards

File

A collection of related records.

29
New cards

Atomicity

An ACID property requiring 'All or Nothing', meaning every operation in a transaction must succeed or revert to zero.

30
New cards

Consistency

An ACID property requiring that database rules remain valid before and after a transaction, reverting to a previous state if invalid data causes a failure.

31
New cards

Isolation

An ACID property ensuring that multiple transactions do not interfere with each other.

32
New cards

Durability

An ACID property ensuring that completed transactions remain saved even after system crashes.

33
New cards

Structural Dependence

Occurs when access to data depends on the file's structure, requiring programs to be modified if the file structure changes.

34
New cards

Structural Independence

Exists when changes can be made to the file structure without affecting application programs.

35
New cards

Data Dependence

Occurs when application programs must be changed whenever data storage characteristics change.

36
New cards

Data Independence

Occurs when data storage characteristics can change without affecting application programs.

37
New cards

Logical Data Format

Describes data structure and meaning in a way that is easy for people and programs to understand.

38
New cards

Physical Data Format

Describes how data is actually stored, saved, and read by a specific computer or software system.

39
New cards

Data Redundancy

Occurs when the same data is unnecessarily stored in multiple locations.

40
New cards

Data Integrity

The condition in which all of the data in the database are consistent with the real-world events and conditions.

41
New cards

Insertion Anomaly

A data anomaly that occurs when data cannot be inserted because other required information is missing.

42
New cards

Update Anomaly

A data anomaly that occurs when the same data appears in multiple places and all copies must be updated.

43
New cards

Deletion Anomaly

A data anomaly that occurs when deleting one record accidentally removes important information.