Вы находитесь на странице: 1из 26

Data Model

Chapter 2
The Importance of Data
Model
An abstraction of a more complex real
Model
Model world object / event

Data
Data Model
Model Simple / graphical representation of
complex real data structures
Chap. 2: Data Model

Main functions of model

to help us to understand the complexities of the


real world environment.
as a communication tools to facilitates the
interaction among designer, programmer & user.
The Importance of Data
Model
Data Model Represent What ??

Data structures
Their characteristic
Chap. 2: Data Model

Relations
Constraints
Transformation
Data Model Basic Building Blocks

Entity Attribute Relationship Constraints

Is anything / or Is a Describe an Is a restriction


any real world characteristic of association placed on the
Chap. 2: Data Model

object that can an entity among entities data


store data
Eg: Eg:
Eg: 1:1, 1:M, • Book Price must less
M:N than rm1000
Book, Doctor, Eg:
• Student CGPA must
Student, Book_Title, between 0.00 and 4.00
Doc_Id,
Student_Name • Each Doctor must have
at least 2 specialization
Types of Relationship
 1:1 (one-to-one)

 1:M (one-to-many)

LECTURER has ROOM


 M:N (many-to-many)
Chap. 2: Data Model

PERSON has CAR

NURSE served WARD


Business Rules
 Is a brief, precise & UNambiguous
description of a policy / procedure /
within a specific organization
environment.
 Is derived from a detailed description
Chap. 2: Data Model

of an organization’s operation
 To define entity, attributes,
relationship, constraint
 Must be written / documented properly.
Business Rules
WHERE TO GET THE BUSINESS RULES??
 Company manager
 Department manager
 Policy makers
Chap. 2: Data Model

 Written document
 company
procedures
 Standard & policy
 operation manual
 End user
Business Rules
Why BR need to be identified & documented properly???

 Help to standardize the company’s view of data


 As a comm. tools between user & designers
 Allow the designer to understand the nature,
Chap. 2: Data Model

role, and scope of data


 To understand the business process
 To develop appropriate relationship participation
rules & constraints and to create an accurate
data model
Discovering Business Rules

 Generally, nouns translate into entities

 Verbs translate into relationships among


entities
Chap. 2: Data Model

 Relationships are bi-directional


The Evolution of Data Model
Chap. 2: Data Model
Chap. 2: Data Model
Hierarchical Model
Chap. 2: Data Model
Network Model
Chap. 2: Data Model
Relational Model
Entity-Relationship Model
Chap. 2: Data Model
Object-Oriented Model
Chap. 2: Data Model
Summary of Data Model
Chap. 2: Data Model
Degrees of Data Abstraction
 Way of classifying data models
 External; Conceptual; Internal
Chap. 2: Data Model
External Model
 End users’ view of the data environment
 based on the internal model
 a specific representation of an external view 
External Schema
 DBMS dependent,
dependent and hardware independent
Chap. 2: Data Model

 Advantages :
 make application program development simpler
 easier to identify specific data required
 providing feedback about the conceptual model’s
adequacy
 ensure security constraints in the dtbs design
Chap. 2: Data Model
External Model
Conceptual Model
 global view of dtbs
 specific representation of an conceptual model  Conceptual
Schema
 integrate all external view in a single view
 representation of data as viewed by high level managers
 the basis for identification & description of the main data objects,
Chap. 2: Data Model

avoiding details
 most widely use conceptual model is the ERM-represent by ERD
 easily understood –macro view of data environment
 Independent of both software and hardware

 Does not depend on the DBMS software used to implement the model
 Does not depend on the hardware used in the implementation of the
model
 Changes in either hardware or DBMS software have no effect on the
database design at the conceptual level
Internal Model
 representation of the dtbs as seen by the DBMS
 requires the designer to match the conceptual
model’s characteristics and constraints to those
of the selected implementation model
 Maps the conceptual model to the DBMS (eg:
Chap. 2: Data Model

Access)
 Internal schema depicts a specific
representation of an internal model
 it is software dependent, hardware
independent
Chap. 2: Data Model
Internal Model
Physical Model
 operates at the lowest level of abstraction
 describing the way data are saved on
storage
 requires the definition of both physical
storage device and the access methods to
Chap. 2: Data Model

reach the data within the storage device


 it is both software & hardware
dependent
Summary
 A data model is a (relatively) simple
abstraction of a complex real-world
data environment
 Basic data modeling components
are:
Chap. 2: Data Model

 Entities
 Attributes
 Relationships
 Constraints
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
Chap. 2: Data Model

between record types

 Relational model
 Current database implementation standard
 ER model is a popular graphical tool for data
modeling that complements the relational
model
Summary
 Object is basic modeling structure of
object oriented data model

 The relational model has adopted many


object-oriented extensions to become the
Chap. 2: Data Model

extended relational data model (ERDM)

 Data modeling requirements are a


function of different data views (global vs.
local) and level of data abstraction

Вам также может понравиться