ARSITEKTUR BASISDATA

MATA KULIAH SISTEM BASIS DATA

TAHUN AJARAN 2021/2022

Novi Prisma Yunita, M.Kom

Fakultas Ilmu Komputer

 The Three-Level ANSI-SPARC Architecture

This model provide a basis for understanding some of the functionality of a Database Management System
(DBMS). Three distinct levels at which data items can be described. The level form a three-level architecture
comprising an internal, a conceptual, and and external level.

The objective : to separate each user view of the database

Why separation is desirable :

• Each user should be able to access the same data but have different costumized view of data. The change
if any should not affect the other user view

• User should not have to deal directly with physical database storage details, suc as indexing. User’s
interaction with the database should be independent of storage consideration

• The DBA should be able to change the db storage structure without affecting the user view

• etc
Pic : The ANSI-SPARC three-level architecture
 Internal Level

• Describes how data is stored in the database physically

• It covers the data structures and file organizations used to store data on storage devices
• For instance :

“data customer, internal level sees customer data as it has attribute named “address” that
stored at storage media with the size of 20 byte”
 Conceptual 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. Its complete view of
the data requirements of the organization that is independent of any storage considerations.

• This level represents : all entities, their attributes, and their relationships; the constraints on the
data; semantic information about the data; security and integrity information;

• The user ignores the complexity on the physical level

• Data describe as box, line, arrow

• Database designer designs in the form of diagrams and model

 External Level

• describes only some part from the entire database

• database user don’t need the entire database contents

• end-user app converts physical data into logical to user (data stored as yes or no, displayed as
the other)

• user are limited with the hardware and software ability that used by database app
 Database Language

• Data Definition Language (DDL) : used to specify the database scchema

• Data Manipulation Language (DML) : used both to read and update the database

• Both called data sublanguage because they don’t include construct for all computing
needs, such as conditional and iterative statements, which are provided by the high level
programming language

• Many DBMSs have a facility for embedding the sublanguage in a high-level programming
language such as COBOL, Java, C#, C++, Pascal, Fortran, Visual Basic
 Data Definition Language (DDL)

• A language that allows the DBA or user to describe and name the entities, attributes, and
relationships required for the application, together with any associated integrity and
security constraints

• Used to define a schema or modify the existing one

• The result of the compilation of DDL statement is a set of table stored in special files
collectively called the system catalog. It integrated the metadata (data that describes the
objects in the database and make it easier for those object to be accessed or
manipulated)
 Data Manipulation Language (DML)

• A language that provides a set of operations to support the basic data manipulation
operations on the data held in the database

• Include : insertion of new data into the database (db); modification of data stored in db;
retrieval of data contained in db; deletion of data from the db;
 Data Model

• Object-based data model

• Record-based data model

 Object-based Data Models

• Object-based data models use concepts such as entities, attributes, and relationships

• Entity is a distinct object ( a person, place, thing, concept, event)

• Attribute is a property that describes some aspect ot the object that we wish to record

• Relationship is an association between entities

• Object-based data model: entity-relationship (ER); semantic; functional; object-oriented;

 Record-based Data Models

• Three type of record-based data models: relational data model, network data model,
hierarchical data model
 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
 Relational Data Model

branchNo Street City postCode

B005 22 Deer Rd London SW 1 4EH
B007 16 Argyll St Aberdeen AB2 3SU
B003 163 Main St Glasgow G11 9QX
B004 32 Manse Rd Bristol BS99 1NZ
B002 56 Clover Dr London NW10 6EU

staffNo fName lName Position Sex DOB Salary branchNo

SL21 John White Manager M 1-Oct-45 30000 B005

SG37 Ann Beech Assistant F 10-Nov-60 12000 B003

SG14 David Ford Supervisor M 24-Mar-58 18000 B003

 Hierarchical Data Model

• Restricted type of network model

• Data : collection of records; relationships : sets;

• This model allows a node to have only one parent

• Represented as tree graph, records as nodes; sets as egdes;

Hierarchical Data Model
Hierarchical Data Model
 Network Data Model

• Data : collection of records; relationships : sets;

• Allows node to have multiple parents, unlike hierachical model

• Respresented as tree graph, records as nodes; sets as edges;

Network Data Model
PERTANYAAN ?