Ch.

2: Database Environment

Dr. Nader Mahmoud

/22
Chapter Outline:

Objectives of Three-Level Architecture

ANSI-SPARC Three-Level Architecture

Data Independence

Database Languages

Data Models

Functions of a DBMS

1/22
1) Objectives of Three-Level Architecture:

1. All users should be able to access same data, but have a different customized view
of the data.

2. A user’s view is immune to changes made in other views.

3. Users should not need to know physical database storage details.

2/22
1) Objectives of Three-Level Architecture:

4. DBA should be able to change database storage structures without affecting the
users’ views.

5. Internal structure of database should be unaffected by changes to physical aspects

of storage.

6. DBA should be able to change conceptual structure of database without affecting all
users.

3/22
 1) ANSI-SPARC Three-Level Architecture:

• External Level

• Users’ view of the database (different

representation of the same data). E.g.
date formate, and age.

• Describes that part of database that is

relevant to a particular user (entities,
attributes, and relationships).

4/22
 1) ANSI-SPARC Three-Level Architecture:
• Conceptual Level

• Community view of the database.

• Describes what data is stored in

database and relationships among the
data.

• The conceptual level represents:

• All entities, attributes,
relationships;
• Constraints on the data;
• Security and integrity
information.
5/22
 1) ANSI-SPARC Three-Level Architecture:

• Internal Level

• Physical representation of the

database on the computer.

• Describes how the data is stored

in the database (data structures,
file organization, storing, and
hashing/indexing).

6/22
1) Differences between Three Levels of ANSI-SPARC Architecture:

7/22
 2) Data Independence:

• Means that upper levels are unaffected by changes to lower levels. logical and physical.

Logical Data Independence

• Refers to immunity of external schemas

to changes in conceptual schema (e.g.
addition/removal of entities and/or
relationships).

• Should not require changes to external

schema or rewrites of application
programs.

8/22
 2) Data Independence:

• Means that upper levels are unaffected by changes to lower levels. logical and physical.

Physical Data Independence

• Refers to immunity of conceptual schema

to changes in the internal schema (e.g.
using different file organizations, storage
structures/devices).

• Should not require change to conceptual

or external schemas.

9/22
3) Database Languages:

Data Definition Language (DDL)

• Allows the DBA or user to describe and name entities, attributes, and
relationships required for the application

• Plus any associated integrity and security constraints.

10/22
 3) Database Languages:

• Data Manipulation Language (DML)

• Provides basic data manipulation operations on data held in the database.

Procedural DML Non-Procedural DML

Allows user to tell system Allows user to state what data
exactly how to manipulate is needed rather than how it is
data. to be retrieved.

• Fourth Generation Languages (4GLs): Forms generator, report generator, graphics

generator, and application generator.
11/22
 4) Data Models:

• Collection of concepts for describing data, relationships between data, and constraints on
the data in an organization.

• To represent data in an understandable way.

a structural part

• Data Model consists of: a manipulative part

possibly a set of integrity rules

12/22
4) Data Models:

1. Object-Based Data Models

• Entity-Relationship
• Semantic
• Functional
• Object-Oriented.

2. Record-Based Data Models

• Relational Data Model
• Network Data Model
• Hierarchical Data Model.

3. Physical Data Models

13/22
4) Data Models:

1. Object-Based Data Models

• Entity-Relationship
• Semantic
• Functional
• Object-Oriented.

2. Record-Based Data Models

• Relational Data Model
• Network Data Model
• Hierarchical Data Model.

3. Physical Data Models

14/22
4) Data Models:

1. Object-Based Data Models

• Entity-Relationship
• Semantic
• Functional
• Object-Oriented.

2. Record-Based Data Models

• Relational Data Model
• Network Data Model
• Hierarchical Data Model.

3. Physical Data Models

15/22
4) Data Models:

1. Object-Based Data Models

• Entity-Relationship
• Semantic
• Functional
• Object-Oriented.

2. Record-Based Data Models

• Relational Data Model
• Network Data Model
• Hierarchical Data Model

3. Physical Data Models

16/22
4) Data Models:

1. Object-Based Data Models

• Entity-Relationship
• Semantic
• Functional
• Object-Oriented.

2. Record-Based Data Models

• Relational Data Model
• Network Data Model
• Hierarchical Data Model

3. Physical Data Models

17/22
4) Conceptual Modeling:

• Is the process of developing a model of information use that is independent of

implementation details.

• Conceptual schema is the core of a system supporting all user views.

• Should be complete and accurate representation of an organization’s data

requirements.

18/22
5) Functions of a DBMS:

1. Data Storage, Retrieval, and

Update.

2. A User-Accessible Catalog.

3. Transaction Support.

The Lost update problem

4. Concurrency Control Services.

5. Recovery Services.
19/22
5) Functions of a DBMS:

6. Authorization Services.

7. Support for Data Communication.

8. Integrity Services.

9. Services to Promote Data Independence.

10. Utility Services.

20/22
End of Chapter 2

22/22