BY : Ajaz Khan Baig

1
 Database Management
Systems

Lecture -4
2
 Introduction

Functions of DBMS
DBMS Environments
Database Application
Development Process
Preliminary Study of System

3
 Functions of DBMS

Data Processing
A User Accessible Catalog
Transaction Support
Concurrency Control Services

4
 Functions of DBMS

 Recovery Services
 Authorization Services
 Support for Data Communication
 Integrity Services

5
 DBMS Environments
Single User
Multi-user
 Teleprocessing
 File Servers
 Client-Server

6
 Teleprocessing

All processing at
a central computer

Dumb Terminals

7
 File Servers

File Server
Database

File returned Data request

LAN

Workstation
Workstation
8
 Client-Server

Server
Database (with DBMS)

Selected data returned Data request

LAN

Client Client
9
 Database Application Development Process

Involves
Database Design
Application Programs
Implementation

10
 Database Design

A DB Design is a model of a particular

real-world system
It provides a picture of reality

Should be simple and self-explanatory

11
 Database Development Process

Similar to software
Preliminary Study
development process

Requirement
Analysis
DB Design

Physical Design

Implementation

Maintenance

12
 Design Stages
Analyze User Environment

Develop Conceptual Model

Map Conceptual Model to Logical

Choose DBMS

Develop Physical Design

Implement System

Test System

Operational Maintenance

13
 Analyze Existing System
Objective: To understand the working
of existing system
Analyze users’ requirements
Tool Used:
 Data Flow Diagrams

14
 Database Model
A database can be modeled as:
 a collection of entities,
 relationship among entities.

Database systems are often modeled

using an Entity Relationship (ER)
diagram as the "blueprint" from which
the actual data is stored — the output
of the design phase.
 Data Flow Diagrams (DFDs)
Represent the flow of data between
different processes within a system
Simple & intuitive, not focusing on details

To describe, what users do, rather than

what computers do
Limitations
 Focus only on flows of information
 Decision points/basis not included

16
 Entity Relationship Diagram (ERD)

ER model allows us to sketch database designs

ERD is a graphical tool for modeling data.

ERD is widely used in database design
ERD is a graphical representation of the logical
structure of a database
ERD is a model that identifies the concepts or
entities that exist in a system and the
relationships between those entities
 Purposes of ERD
An ERD serves several purposes
The database analyst/designer gains a better
understanding of the information to be
contained in the database through the process
of constructing the ERD.
The ERD serves as a documentation tool.
Finally, the ERD is used to communicate the
logical structure of the database to users. In
particular, the ERD effectively communicates
the logic of the database to users.
 Objectives
Why data models are important
About the basic data-modeling building
blocks
What business rules are and how they
influence database design
How the major data models evolved
How data models can be classified by level of
abstraction

20
 The Importance of Data Models
Data models
 Relatively simple representations, usually
graphical, of complex real-world data
structures
 Facilitate interaction among the designer,

the applications programmer, and the end

user

21
 The Importance of Data Models (continued)

End-users have different views and

needs for data

Data model organizes data for various

users

22
 Data Model Basic Building Blocks

Entity - anything about which data are to be

collected and stored
Attribute - a characteristic of an entity
Relationship - describes an association among
entities
 One-to-many (1:M) relationship

 Many-to-many (M:N or M:M) relationship

 One-to-one (1:1) relationship

Constraint - a restriction placed on the data

23
 Business Rules
Brief, precise, and unambiguous
descriptions of a policies, procedures, or
principles within a specific organization

Apply to any organization that stores and

uses data to generate information

Description of operations that help to create

and enforce actions within that
organization’s environment

24
 Business Rules (continued)
Must be extracted in writing
Must be kept up to date
Sometimes are external to the
organization
Must be easy to understand and
widely disseminated
Describe characteristics of the data as
viewed by the company
25
 Discovering Business Rules

Sources of Business Rules:

Company managers
Policy makers
Department managers
Written documentation
 Procedures
 Standards

 Operations manuals

Direct interviews with end users

26
 Translating Business Rules into Data Model
Components

Standardize company’s view of data

Constitute a communications tool between users
and designers
Allow designer to understand the nature, role,
and scope of data
Allow designer to understand business processes
Allow designer to develop appropriate
relationship participation rules and constraints
Promote creation of an accurate data model

27
 Discovering Business Rules
(continued)
Generally, nouns translate into
entities

Verbs translate into relationships

among entities

Relationships are bi-directional

28
 The Evolution of Data Models
(continued)

Hierarchical
Network
Relational
Entity relationship
Object oriented (OO)

29
 The Hierarchical Model
Developed in the 1960s to manage
large amounts of data for complex
manufacturing projects

Basic logical structure is represented

by an upside-down “tree”

30
The Hierarchical Model (continued)

31
The Hierarchical Model (continued)
The hierarchical structure contains
levels, or segments
Depicts a set of one-to-many (1:M)
relationships between a parent and its
children segments
 Each parent can have many children
 each child has only one parent

32
The Hierarchical Model (continued)
Advantages
 Many of the hierarchical data model’s features
formed the foundation for current data models

 Generated a large installed (mainframe) base,

created a pool of programmers who developed
numerous tried-and-true business applications

33
The Hierarchical Model (continued)
Disadvantages
 Complex to implement
 Difficult to manage

 Lacks structural independence

 Implementation limitations

 Lack of standards

34
 The Network Model
Created to
 Represent complex data relationships
more effectively
 Improve database performance

 Impose a database standard

Conference on Data Systems

Languages (CODASYL)
Database Task Group (DBTG)

35
The Network Model (continued)

Schema
 Conceptual organization of entire database as
viewed by the database administrator
Subschema
 Defines database portion “seen” by the
application programs that actually produce the
desired information from data contained within
the database
Data Management Language (DML)
 Defines the environment in which data can be
managed

36
The Network Model (continued)
Schema Data Definition Language
(DDL)
 Enables database administrator to

define schema components

Subschema DDL
 Allows application programs to
define database components that will
be used
DML
 Works with the data in the database
37
The Network Model (continued)

Resembles hierarchical model

Collection of records in 1:M relationships
Set
 Relationship

 Composed of at least two record types

 Owner

 Equivalent to the hierarchical model’s

parent
 Member

 Equivalent to the hierarchical model’s

child
38
The Network Model (continued)

39
 The Network Model (continued)
Disadvantages
 Too cumbersome
 The lack of ad hoc query capability

put heavy pressure on programmers.

 Any structural change in the database

could produce havoc in all application

programs that drew data from the
database.
 Many database old-timers can recall

the interminable information delays

40
 KEY POINTS & SUMMARY
A data model is a (relatively) simple
abstraction of a complex real-world
data environment
Basic data modeling components are:
 Entities
 Attributes

 Relationships

 Constraints

41
 Summary

Hierarchical model

 Depicts a set of one-to-many (1:M) relationships

between a parent and its children segments

Network data model

 Uses sets to represent 1:M relationships between record

types.

42
 Thank You

43 10/19/24
 KEY POINTS
Data base architecture:
 External View
 The way users think about data
 Each user has a view of the database limited to the
appropriate portion of the user’s perspective of
reality.
 Conceptual view

 A complete description of the information content of the

database
 Physical view
 DBMS chooses type of data structures
 lays out data on storage devices with operating system access
methods
44
 Summary
Functions of DBMS and DBMS
Environments

Discussed Modeling tools(DFD)