Data Base Management System

Class :BSSE
Credit Hours ( 3)
 Introduction
Database model Importance &
business rule
DBMS Models
Network Model
Hierarchical model

3 10/19/24
 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

4
 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

5
 The Importance of Data Models (continued)

End-users have different views and

needs for data

Data model organizes data for various

users

6
 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

7
 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

8
 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
9
 Discovering Business Rules

Sources of Business Rules:

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

 Operations manuals

Direct interviews with end users

10
 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

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

Verbs translate into relationships

among entities

Relationships are bi-directional

12
 The Evolution of Data Models
(continued)

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

13
 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”

14
The Hierarchical Model (continued)

15
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

16
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

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

 Lacks structural independence

 Implementation limitations

 Lack of standards

18
 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)

19
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

20
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
21
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
22
The Network Model (continued)

23
 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

24
 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

25
 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.

26
 Thank You

27 10/19/24