Scribd
Upload
73 views

User 1 User 2 User N External Level

The document summarizes the three-level ANSI SPARC architecture for database systems. It includes an external level that defines each user's view, a conceptual level that defines the overall database structure, and an internal level that defines the physical storage. The document also discusses data models, conceptual modeling, functions of a DBMS, DBMS components, and software components for database management.

Uploaded by

Aileen P. de Leon
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
73 views

User 1 User 2 User N External Level

The document summarizes the three-level ANSI SPARC architecture for database systems. It includes an external level that defines each user's view, a conceptual level that defines the overall database structure, and an internal level that defines the physical storage. The document also discusses data models, conceptual modeling, functions of a DBMS, DBMS components, and software components for database management.

Uploaded by

Aileen P. de Leon
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

DBMS Lecture #2

THREE-LEVEL ANSI SPARC ARCHITECTURE

o American National Standards Institute – Standards Planning and Requirements


Committee
o An early proposal for a standard terminology and general architecture for
database systems was produced in 1971 by the DBTG(Data Base Task Group)
appointed by the Conference on Data Systems and Languages(CODASYL).
o The DBTG recognized the need for a two-level approach with a system view
called the schema and user views called subschemas.
o Recognized the need for the three-level approach with a system catalog.

The three-level architecture comprising an external, a conceptual and an internal


level.
User 1 User 2 User n

External View 1 View 2 ……. View n


Level

Conceptual
Conceptual
Level
Schema

Internal Level Internal


Schema

Physical Data
Organization Database

EXTERNAL LEVEL – the user’s view of the database. This level describes that part
of the database that is relevant to each other.

- consists of a number of different external views of the database. Each user


has a view of the “real world” represented in a form that is familiar for that user.

- includes entities, attributes and relationships.


CONCEPTUAL LEVEL – community view of the database. This level describes what
data is stored in the database and the relationships among the data.

- contains the logical structure of the entire database as seen by the DBA.
- Represents: entities, attributes and relationships
Constraints on the data
Semantic information about the data
Security and integrity information

INTERNAL LEVEL – physical representation of the database on the computer. This


level describes how the data is stored in the database.

- concerned with: storage space allocation for data


Record descriptions for storage
Record replacement
Data compression and data encryption techniques

• Physical Level – maybe managed by the operating system under the direction of
the DBMS.

TWO TYPES OF DML:

PROCEDURAL DML – language that allows the user to tell the system what data is
needed and exactly how to retrieve the data.

* User/Programmer specifies what data is needed and how to obtain it. This means
that the user must express all the data access operations that are to be used by calling
appropriate procedures to obtain the information required.

NON-PROCEDURAL DML – language that allows the user to state what data is needed
rather than how it is to be retrieved.

* It allows the required data to be specified in a single retrieval or update statement.


The user specifies what data is required without specifying how it is to be obtained.

FOURTH-GENERATION LANGUAGES

- shorthand programming language.


- Non-procedural
- User defines what is to be done, not how.
- It is expected to rely largely on how much higher-level components known as
fourth-generation tools. The user does not define the steps that a program
needs to perform a task, but instead defines parameters for the tools that use
them to generate an application program. It is claimed that 4GLs can improve
productivity by a factor of ten, at the cost of limiting the types of problem that
can be tackled.
It encompasses:

- presentation languages, such as query languages and report generators.


- Speciality languages, such as spreadsheets and database languages.
- Application generators that define, insert, update and retrieve data from the
database to build applications.
- Very high-level languages that are used to generate application code.

TYPES OF 4GL:
1. FORM GENERATORS – is an interactive facility for rapidly creating data input and
display layouts for screen forms.

2. REPORT GENERATORS – facility for creating reports from data stored in the
database. It allows the user to ask questions of the database and retrieve information
from it for a report.

3. GRAPHICS GENERATORS – facility to retrieve data from the database and display
the data as a graph showing trends and relationships in the data.

4. APPLICATION GENERATORS – facility for producing a program that interfaces with


the database.

DATA MODELS AND CONCEPTUAL MODELING

DATA MODEL – an integrated collection of concepts for describing and manipulating


data, relationships between data, and constraints on the data in an organization.

- represents the organization itself. It provides the basic concepts and notations
that will allow database designers and end-users definitely and accurately to
communicate their understanding of the organizational data.

MODEL – is a representation of “real world” objects and events, and their associations.
- an concept that concentrates on the essential, inherent aspects of an
organization and ignores the accidental properties.

THREE COMPONENTS:
1. STRUCTURAL PART – consisting of a set of rules according to which databases can
be constructed.

2. MANIPULATIVE PART – defining the types of operation that are allowed on the
data(this includes the operations that are used for updating or retrieving data from the
database and for changing the structure of the database).

3. SET OF INTEGRITY RULES – ensures that the data is accurate.


THREE CATEGORIES OF DATA MODEL
1. OBJECT-BASED DATA MODEL – use concepts such as entities, attributes, and
relationships.
ENTITY – is a distinct object in the organization that is to be represented in the
database.
ATTRIBUTE – is a property that describes some aspect of the object that we
wish to record.
RELATIONSHIP – is an association between entities.

COMMON TYPES OF OBJECT-BASED DATA MODEL:

o Entity-Relationship
o Semantic
o Functional
o Object-oriented

2. RECORD-BASED DATA MODELS – database consists of a number of fixed-format


records possibly of differing types.

THREE PRINCIPAL TYPES OF RECORD-BASED LOGICAL DATA MODEL

a. RELATIONAL DATA MODEL - based on the concept of mathematical relations. Data


and relationships are represented as tables, each of which has a number of columns
with a unique name.

b. NETWORK DATA MODEL - data is represented as collections of records, and


relationships are represented by sets. Relationship are explicitly modelled by the sets,
which become pointers in the implementation. The records are organized as
generalized graph structures with records appearing as nodes and sets as edges in the
graph.

c. HIERARCHICAL DATA MODEL – data is represented as collections of records and


relationships are represented by sets. However, the hierarchical model allows a node to
have only one parent. It can be represented as a tree graph, with records appearing as
nodes, also called segments, and sets as edges.

3. PHYSICAL DATA MODELS – describe how data is stored in the computer,


representing such as record structures, record orderings and access paths.

4. CONCEPTUAL MODELING – known as the “heart” of the database. It supports all


the external views and is, in turn, supported by the internal schema. However, the
internal schema is merely the physical implementation of the conceptual schema. The
conceptual schema should be a complete and accurate representation of the data
requirements of the enterprise.
- is the process of constructing a model of the information use in an enterprise
that is independent of implementation details, such as the target DBMS, application
programs, programming languages, or any other physical considerations.

FUNCTIONS OF A DBMS:
a. Data storage, retrieval, and update
b. User-accessible catalog
c. Transaction support
d. Concurrency control services
e. Recovery services
f. Authorization services
g. Support for data communication
h. Integrity services
i. Services to promote data independence
j. Utility services

COMPONENTS OF A DBMS:

a. Query processor
b. Database manager
c. File manager
d. DML pre-processor
e. DDL compiler
f. Catalog manager

MAJOR SOFTWARE COMPONENTS FOR THE DATABASE MANAGER:

a. Authorization control
b. Command processor
c. Integrity checker
d. Query optimizer
e. Transaction manager
f. Scheduler
g. Recovery manager
h. Buffer manager

You might also like