Chapter 2 Cs338

Front 1

Suppression of details of data organization and storage

Back 1

Data abstraction

Front 2

Highlighting of the essential features for an improved understanding of data

Back 2

Data abstraction

Front 3

Collection of concepts that describe the structure of a database

Back 3

Data model

Front 4

Provides means to achieve data abstraction

Back 4

Data model

Front 5

Specify retrievals and updates on the database

Back 5

Basic operations

Front 6

Allows the database designer to specify a set of valid operations allowed on database objects

Back 6

Dynamic aspect or behavior of a database application

Front 7

Close to the way many users perceive data

Back 7

High-level or conceptual data models

Front 8

Describe the details of how data is stored on computer storage media

Back 8

Low-level or physical data models

Front 9

Easily understood by end users
Also similar to how data organized in computer storage

Back 9

Representational data models

Front 10

Represents a real-world object or concept

Back 10

Entity

Front 11

Represents some property of interest
Further describes an entity

Back 11

attribute

Front 12

Represents an association among the entities

Back 12

Relationship among two or more entities

Front 13

Used most frequently in traditional commercial DBMSs

Back 13

Relational data model

Front 14

New family of higher-level implementation data models
Closer to conceptual data models

Back 14

Object data model

Front 15

Describe how data is stored as files in the computer

Back 15

Physical data models

Front 16

Structure that makes the search for particular database records efficient

Back 16

Access path

Front 17

Example of an access path
Allows direct access to data using an index term or a keyword

Back 17

Index

Front 18

Description of a database

Back 18

Database schema

Front 19

Displays selected aspects of schema

Back 19

Schema diagram

Front 20

Each object in the schema

Back 20

Schema construct

Front 21

Data in database at a particular moment in time

Back 21

Database state or snapshot

Front 22

Specify database schema to the DBMS

Back 22

Define a new database

Front 23

Populated or loaded with the initial data

Back 23

Initial state

Front 24

Satisfies the structure and constraints specified in the schema

Back 24

Valid state

Front 25

Changes applied to schema as application requirements change

Back 25

Schema evolution

Front 26

Describes physical storage structure of the database

Back 26

Internal level

Front 27

Describes structure of the whole database for a community of users

Back 27

Conceptual level

Front 28

Describes part of the database that a particular user group is interested in

Back 28

External or view level

Front 29

types of data independence

Back 29

logical and physical

Front 30

Capacity to change the schema at one level of a database system
Without having to change the schema at the next higher level

Back 30

Data Independence

Front 31

Defines both schemas (language)

Back 31

Data definition language (DDL)

Front 32

Specifies the internal schema (language)

Back 32

Storage definition language (SDL)

Front 33

Specifies user views/mappings to conceptual schema (language)

Back 33

View definition language (VDL)

Front 34

Allows retrieval, insertion, deletion, modification (language)

Back 34

Data manipulation language (DML)

Front 35

Can be used on its own to specify complex database operations concisely
•Set-at-a-time or set-oriented (language)

Back 35

High-level or nonprocedural DML

Front 36

Must be embedded in a general-purpose programming language
•Record-at-a-time
(language)

Back 36

Low-level or procedural DML

Front 37

Load existing data files

Back 37

loading

Front 38

Creates a backup copy of the database

Back 38

backup