0% found this document useful (0 votes)
19 views

Chapter 2_Database system concepts and architectures (2)

Uploaded by

teseman2020
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views

Chapter 2_Database system concepts and architectures (2)

Uploaded by

teseman2020
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

CHAPTER TWO

Database System Concepts and Architectures

- Ermias N.

22, Mar 2023


Chapter Two

Data Abstraction and Data Models


• Database systems are made up of complex data structure.
• Data structure mean the data types, relationships, and constraints that
should hold on the data
• To ease user interaction with the database, the developer hide internal
irrelevant details from the users.
• The process of hiding this irrelevant details from the users is called
data abstraction.

• THINK how a car’s internal mechanisms are


abstracted away from the driver.
2
Chapter Two

Data Abstraction and Data Models


• A data model: A collection of concepts that can be used to describe
the structure of a database.
• Most data models also include a set of basic operations for
specifying retrievals and updates on the database.

3
Chapter Two

Categories of Data Models


• High-level or conceptual data models: provide concepts that are close to the
way many users perceive data.
• Conceptual data models use concepts such as entities, attributes, and relationships.
• An entity represents a real-world object or concept. Eg. employee.
• An attribute represents some property of interest that further describes an entity,
Eg. employee’s name or salary.
• A relationship among two or more entities represents an interaction among the
entities. Eg. works-on
• low-level or physical data models: provide concepts that describe the details of
how data is stored in the computer.
• Concepts provided by low-level data models needs computer specialist not end
users.
4
Chapter Two

Schemas, Instances, and Database


State
• The description of a database is called the database schema, which is
specified during database design and is not expected to change
frequently.
• The actual data in a database may change quite frequently. The data
in the database at a particular moment in time is called a database
state.
• Current set of occurrences in a given database state called instances.
• Every time we insert or delete a record, or change the value of a data
item in a record, we change one state of the database into another
state.
5
Chapter Two

Database System Architecture


• Centralized Database System Architecture:
• All processing performed remotely on the “high performance” computer system.

• Only display information sent to the terminals

• And, the terminals have not a processing capabilities.

• Client/Server Architecture for a Database System:


• As the price of hardware decline, terminals replaced by PCs and workstations
• So the client processes stated to run separately from the server processes, usually on a
different computer.

6
Chapter Two

Cont…
• Two-Tier Client/Server Architecture: In this architecture the client
processes provide an interface for the user, and gather and present
data usually on a screen.
• The server processes provide an interface with the data storage. The
logic that validates data, monitors security and permissions, and
performs other business rules.
• The exact division of the logic varies from system to system.
• Client/server applications that are designed to run the user and
business tiers of the application on the client side and the data tier on
the server side are known as fat client applications.
7
Chapter Two

Cont…
• Applications that are designed to run the user tier on the client side and
the business and data tiers on the server side are known as thin client
applications.
• Three-Tier Client/Server Architecture: An application that has three
modularly separated tiers that can be run on three machines.
• User/Client tier (GUI or Web Interface): User tier presents the user interface
for the application, displays data and collects user input.

• Application tier (Application Server or Web Server): It receives requests


for data from the user tier, evaluates them against the business rules and passes
them on to the data tier

• Data tier (Data Server): Data tier comprises the data storage and a layer that
passes data from the data storage to
8
the business tier and vice versa.
Chapter Two

Cont…

9
Chapter Two

The Three-Schema Architecture


• The goal of the three-schema architecture is to separate the user
applications and the physical database.
• The internal level has an internal schema: which describes the physical
storage structure of the database. describes the complete details of data
storage and access paths for the database.

• The conceptual level has a conceptual schema: describes the structure of


the whole database for a community of users. Hides the details of physical
storage structures and concentrates on describing entities, data types,
relationships

• The external or view level includes external schema: Includes user views.
Hides the rest of the database from user groups.

1
0
Chapter Two

Cont…

1
1
Chapter Two

Data Independence
• Data independence: Can be defined as the capacity to change the
schema at one level of a database system without having to change the
schema at the next higher level.
• There are two types of data independence.
• Logical data independence: The capacity to change the conceptual
schema without having to change external schemas or application
programs
• We may change the conceptual schema to expand the database or to
reduce the database, but it doesn’t affect the external schema.
• Changes to constraints can be applied also to the conceptual schema
without affecting the external schemas.
1
2
Chapter Two

Data Independence
• Physical data independence: The capacity to change the internal
schema without having to change the conceptual (or external)
schemas.
• If the same data as before remains in the database, we should not
have to change the conceptual schema

1
3
Chapter Two

Database Development Life Cycle


• There are several steps in designing a database system, the major steps in database design
are :-
• Planning: Identifying information gap in an organization and propose a database solution to
solve the problem.
• Analysis: Concentrates more on fact finding about the problem
• Feasibility analysis, requirement determination and structuring, and selection of best
design method are also performed at this phase.
• Design:
• Conceptual Design: concise description of the data, data type, relationship between data and constraints on the data.
• Logical Design: a higher level conceptual abstraction with selected specific data model to implement the data structure with
no physical consideration.

• Physical Design: physical implementation of the upper level design of the database with respect to internal storage and file
structure

1
4
Chapter Two

Cont…
• Implementation: The testing and deployment of the designed database for use.
• Operation and Support: Administering and maintaining the operation of the database

1
5
Chapter Two

DBMS Languages and Interfaces


• Data Definition Language (DDL): The language by which database schema is
defined.
• Storage structure and access matters used by the database system are specified by
DDL.
• Data manipulation language (DML): The language by which users manipulate or
access data stored in database.
• Retrieval
• Insertion
• Deletion
• Modification
• Data control language (DCL): Provides internal security for a database.
1
6
Chapter Two

DBMS Interfaces
Types of interfaces provided by the DBMS include:
• Menu-Based Interfaces
• These interfaces present the user with lists of options that lead the user through the formulation of a
request.

• Need not to memorize the specific commands and syntax


• Query is composed step-by-step by picking options from a menu that is displayed by the system .

• Forms-Based Interfaces:
• Displays a form to each user.
• User can fill out form to insert new data
• or they can fill out only certain entries, to retrieve matching data for the remaining entries.
• Graphical User Interfaces: Displays a schema to the user in diagram form.
1
7
Chapter Two

Database System Environment


• Database management system consists of the following
components:
• Hardware
• Software
• Data
• Procedure
• People

1
8
Chapter Two

Classification of DBMSs
Reading Assignment…

1
9

You might also like