1

BM62E4 – DATA MANAGEMENT

Pertemuan 4

Konsep Pemodelan Data

Candiwan

Prodi MBTI – Fakultas Ekonomi & Bisnis

 2

OUTLINE
1. Konsep Data Model

2. Elemen-elemen Pada Data Model

3. Penentuan Business Rules

4. Evaluasi Data Model

5. Karakteristik Relational Model

6. Contoh Relational Data Model

7. Data Dictionary
 1. Definition 3

Data Modelling: process of creating data model for

determined problem domain
Problem Domain (Mini-World) : a clearly defined area
within the real-world environment, with well-defined
scope and boundaries, that will be systematically
addressed
Data Model : relatively simple presentation, usually
graphical, of more complex real-world data structures.

Data Model as a Communication Tool

Sumber Referensi: Cengage Learning

 4
2. Basic Building Blocks

Entity • Represents a particular type of object in the real world

• May be physical object (ex: person, product) and may also be abstractions (ex: events, schedule)

Attribute • A characteristic of an entity

• The equivalent of fields in file systems

Relationship • Describes an association among entities, in both directions

• Three types: One-to-many (1:M), many-to-many (M:N), one-to-one (1:1)

Constraints • A restriction placed on the data to make sure data integrity

Sumber Referensi: Cengage Learning

 5
3. Business Rule

Business rules establish entities, attributes,

relationships, and constraints
Business Rule is a brief, precise, and unambiguous
description of a policy, procedure, or principle within a
specific organization.
Examples:
A customer may generate many invoices, an invoice is generated by only one
customer
A training session cannot be scheduled for fewer than 10 employees or for more
than 30 employees
 6
3. Business Rules

• Noun  Entity
Translating into • Verb (passive/active)  Relationships
Data Model • Relationship between instances of Entity
 Type of relationship

• Entity names : descriptive of the objects

Naming and familiar to users
Conventions • Attribute names : descriptive of the data
represented by attribute
 7
4. Evolution of Data Models

• Hierarchical Model •Network Model

• Records arranged in tree-like structure • Allow given record to point back to any
other record in the database (M:N
• Contains levels or segments that relationships)
equivalent with file system’s record type • Rely on physical relationship in the form of
• Parent-child relationship (1:M) storage addresses
• First DBMS was IDS by GE in 1964 • Specification released by CODASYL in
1971
Sumber Referensi: Kenneth C. Laudon & Jane P. Laudon Essentials of Management Information Systems, Prentice Hall 2005 (LL)
 4. Evolution of Data Models (cont.) 8

• Relational Model
• A Relation as a table with
Rows and columns
• Easy to understand by
matching values in common
data fields (attributes)
• Introduced in 1970 by E.F.
Codd of IBM
• Implemented through RDBMS
which is powerful and flexible
query language (SQL)
• Does not rely on physical
relationships (performed by
RDBMS behind the scenes)
• Variance: Multidimensional
Model (Data elements are
viewed as being in cubes)

Sumber Referensi: Kenneth C. Laudon & Jane P. Laudon Essentials of Management Information Systems, Prentice Hall 2005 (LL)
 9
4. Evolution of Data Models (cont.)

Entity Relationship Model

Introduced by Peter Chen in
1976
Complement the relational
data model concepts
Normally represented in entity
relationship diagram (ERD),
use graphical
representations
Components:
Entity (and attributes)
Relationships (and relationship
types)
Sumber Referensi: Coronel, Morris, & Rob., Database Principles: Fundamentals of Design, Implementation and Management, CENGAGE Learning 2013
 4. Evolution of Data Models (cont.) 10

Object Oriented (OO)

Model
• Used in object-oriented database
management systems (OODBMS)
• Supports complex data types more
efficiently than relational databases
• Examples: graphic images, video clips,
web pages
• An object consists of data values
describing the attributes of an entity and
their relationship
• OODM Development allowed object to
contain all operations that can be
performed on it

Sumber Referensi: Coronel, Morris, & Rob., Database Principles: Fundamentals of Design, Implementation and Management, CENGAGE Learning 2013
 11
4. Evolution of Data Models (cont.)

Emerging Data Model:

Big Data and NoSQL
• Relational approach does
not always match the needs
of organizations with Big
Data challenges (i.e., store
and process unstructured
data)
• NoSQL databases are not
based on the relational
model
• No standard NoSQL data
model
• Document database
• Graph stores
• Column stores
• Key-value stores
Sumber Referensi: Coronel, Morris, & Rob., Database Principles: Fundamentals of Design, Implementation and Management, CENGAGE Learning 2013
 12
4. Degrees of Data Abstraction

Defined by
American National
Standard Institute
(ANSI/SPARC) in
the early 1970s
A database
designer start with
an abstract view
of overall data
environment and
adds details as
the design comes
closer to
implementation

Sumber Referensi: Coronel, Morris, & Rob., Database Principles: Fundamentals of Design, Implementation and Management, CENGAGE Learning 2013
 13

5. Relational Model Characteristics

 14

5. Relational Model Characteristics

 6. Example of a Database Schema & Database State 15

Sumber Referensi: Elmasri, Ramuz, and Shamkant B. Navathe, Fundamentals of Database Systems, Addison Wesley 2011
 16

7 . Data Dictionary

16
 17
7. Data Dictionary and System Catalog

• Data Dictionary provides a detailed description of all

tables in the database created by the user and designer
• Contains metadata – data about data

• System Catalog: a detailed system data dictionary,

including data about:
• Table’s name, table’s creation and creation date, number of column in each
table, data type for each column, index filenames, index creators, authorized
users, and access privileges

• Often used interchangeably

 7. A Sample Data Dictionary 18

Sumber Referensi: Coronel, Morris, & Rob., Database Principles: Fundamentals of Design, Implementation and Management, CENGAGE Learning 2013
 19

Europe

THANKS YOU
USA OFFICE
1243 Barker Cypress
San Francisco, California
1243 Barker Cypress
San Francisco, California

South America
1243 Barker Cypress
San Francisco, California