PROCESS MODELING (DFD)

ISA 110 – ANALISA DAN DESAIN 1

 DEFINITION
q  A data flow diagram (DFD) maps out the flow of information for any
process or system.
q  It uses defined symbols like rectangles, circles and arrows, plus short
text labels, to show data inputs, outputs, storage points and the routes
between each destination. Data flowcharts can range from simple,
even hand-drawn process overviews, to in-depth, multi-level DFDs that
dig progressively deeper into how the data is handled.
q  They can be used to analyze an existing system or model a new one.
Like all the best diagrams and charts, a DFD can often visually “say”
things that would be hard to explain in words, and they work for both
technical and nontechnical audiences, from developer to CEO.
•  Data Flow Diagram digunakan untuk menggambarkan bagaimana
data ditransformasikan pada perangkat lunak, serta fungsi-fungsi
yang mentranformasikan data
•  Data Flow Diagram ini pertama kali diperkenalkan oleh Martin dan
Extrim yang memperkenalkan suatu algoritma program dengan
menggunakan simbol lingkaran dan panah untuk mewakili arus data
(Data Flow). Data Flow Diagram sendiri digunakan untuk melakukan
penulisan analisa sistem secara struktural.
SIMBOL PADA DFD
 1. KOMPONEN ENTITAS LUAR (EXTERNAL ENTITY)

•  an outside system that sends or receives data, communicating with the

system being diagrammed.
•  They are the sources and destinations of information entering or leaving the
system.
•  They might be an outside organization or person, a computer system or a
business system.
•  They are also known as terminators, sources and sinks or actors.
•  They are typically drawn on the edges of the diagram.

Ø A rectangle represents an external entity

Ø They either supply data or receive data
Ø They do not process data
KOMPONEN ENTITAS LUAR (EXTERNAL ENTITY)
•  Note that:
Ø External entities also are called terminators because they are data
origins or final destinations.
Ø An external entity must be connected to a process through a data-
flow.
 2. KOMPONEN ALIRAN DATA

•  the route that data takes between the external entities, processes and
data stores. It portrays the interface between the other components
and is shown with arrows, typically labeled with a short data name, like
“Billing details.”
•  Example:
Ø  Customer_info (LastName, FirstName, SS#, Tel #, etc.)
Ø  Order_info (OrderId, Item#, OrderDate, CustomerID, etc.).
 2. ALIRAN DATA (DATA FLOW)

•  Notation
Ø  Straight lines with incoming arrows are input data flow
Ø  Straight lines with outgoing arrows are output data flows
•  Note that:
Ø  Because every process changes data from one form into another, at least one
data-flow must enter and one data-flow must exit each process symbol.
 3. PROCESS

•  any process that changes the data, producing an output.

•  It might perform computations, or sort data based on logic, or direct
the data flow based on business rules.
•  A short label is used to describe the process, such as “Submit
payment.”
•  Every process has a name that identifies the function it performs.
•  The name consists of a verb, followed by a singular noun.
•  Example:
Ø Apply Payment
Ø Calculate Commission
Ø Verify Order
 PEDOMAN PEMBERIAN NAMA PROSES

•  Nama proses terdiri dari kata kerja dan kata benda yang
mencerminkan fungsi proses. Misal : hitung gaji, Cetak Nilai.
•  Jangan menggunakan kata “Proses” sebagai bagian dari nama suatu
proses.
•  Tidak boleh ada beberapa proses dengan nama yang sama.
•  Proses harus diberi nomor.
•  Penomoran proses pada tingkat pertama (Diagram Nol) adalah 1.0,
2.0, 3.0, dst.
•  Penomoran proses pada tingkat kedua (rinci proses 1.0) : 1.1, 1.2, 1.3,
dst
•  Context diagram tidak perlu diberi nomor.
 4. DATA STORE
•  Files or repositories that hold information for later use, such as a
database table or a membership form.
•  Each data store receives a simple label, such as “Orders.”

•  Notation
Ø Data can be written into the data store, which is depicted by an outgoing arrow
Ø Data can be read from a data store, which is depicted by an incoming arrow.
•  Examples are: inventory, Accounts receivables, Orders, and Daily Payments.
 4. DATA STORE

•  Note that:
Ø  A data store must be connected to a process with a data-flow.
Ø  Each data store must have at least one input data-flow and at least one output
data-flow (even if the output data-flow is a control or confirmation message).
•  Dipakai untuk memodelkan kumpulan data, misalnya paket data,
tape magnetis, disk, dan model DBMS.
ATURAN PENTING DALAM DFD
 ATURAN 1

1) Antar entitas luar tidak diijinkan terjadi relasi/hubungan

 ATURAN 1

1) Antar entitas luar tidak diijinkan terjadi relasi/hubungan

 ATURAN 2

•  Tidak boleh ada aliran data antara entitas luar dengan data store
 ATURAN 3
•  Entitas luar boleh digambar beberapa kali dengan tanda khusus,
seperti diberi nomor
 ATURAN 4
•  Tidak boleh ada arus data dari datastore ke datastore tanpa melalui
proses
 ATURAN 5
•  Tidak boleh ada aliran data masukan tanpa keluaran atau sebaliknya
 ATURAN 6-12

6)  Satu aliran data boleh mengalirkan beberapa struktur data.

7)  Bentuk anak panah aliran data boleh bervariasi.
8)  Semua obyek harus mempunyai nama.
9)  Aliran data selalu diawali dan diakhiri dengan proses
10) Semua aliran data harus mempunyai tanda arah.
11) Perhatikan penyimpanan dan pembacaan data dari datastore satu
ke datastore lainnya, mengingat akan berdampak pada relasi data/
tabel yang akan dibuat di sistem.
12) Upayakan membuat proses untuk menciptakan datastore awal
(data master) yang akan digunakan untuk proses-proses transaksi.
TINGKATAN/LEVEL DALAM DFD
DFD LEVEL 0
•  DFD Level 0 is also called a
Context Diagram. It’s a
basic overview of the whole
system or process being
analyzed or modeled.
•  It’s designed to be an at-a-
glance view, showing the
system as a single high-level
process, with its relationship
to external entities.
•  It should be easily
understood by a wide
audience, including
stakeholders, business
analysts, data analysts and
developers. 
Ø The context diagram must fit in one page.
Ø The process name in the context diagram should be the name of the
information system.
Ø For example, Grading System, Order Processing System, Registration System.
Ø The context level diagram gets the number 0 (level zero).
 UNIQUE NAME FOR LEVEL

Ø Use unique names within each set of symbols.

Ø For example, there can be only one entity CUSTOMER in all levels of
the data-flow diagrams; or here can be only one process named
CALCULATE OVERTIME among all levels of data-flow diagrams.
 • One way to achieve this is
to restrict the number of
processes in a data-flow
NO CROSS LINE IN diagram.
DFD
 Ø On lower-level data-flow
diagrams with multiple
processes, one should not
RIGHT COMPLEXITY FOR
HUMAN MIND - 7 + / - 2 have more than nine process
SYMBOLS
symbols.
Ø Another way to avoid
crossing lines is to duplicate
an external entity or data
store. Use a special notation
such as an asterisk, to denote
the duplicate symbol.
 Ø Use a unique reference
number for each process
symbol.
NUMBERING
CONVENTION
Ø Other process numbers are
in the hierarchy of:
Ø (1, 2, 3,...);
Ø (1.1, 1.2, 1.3, ..., 2.1, 2.2, 2.3,...);
Ø (1.1.1, 1.1.2, 1.1.3,...).
 A context diagram gives an overview and
it is the highest level in a data flow
diagram, containing only one process
representing the entire system.
It should be split into major processes which
give greater detail and each major process
CONTEXT-LEVEL may further split to give more detail.
DIAGRAM
Ø All external entities are shown on the
context diagram as well as major data
flow to and from them.
Ø The diagram does not contain any data
storage.
Ø The single process in the context-level
diagram, representing the entire system,
can be exploded to include the major
processes of the system in the next level
diagram, which is termed as diagram 0.
 HAL YANG HARUS DIPERHATIKAN
•  harus konsisten dalam artian setiap entitas yang ada di pada diagram konteks juga harus ada
pada DFD level 1 ini jadi tidak ada Entitas yang hilang. selain itu konsisten juga pada arus data
yang ada. jangan sampai ada arus data yang hilang baik yang masuk ke dalam proses maupun
yang ke luar proses.
•  setiap proses menggunakan kata kerja dan harus unik. penomoran pada proses harus
diperhatikan misal dfd level 1 nomor proses 1 maka dfd level 2 untuk proses 1 nomornya akan
menjadi 1.1 dan 1.2 dan seterusnya.
•  setiap arus data harus berbentuk kata benda.
•  setiap proses harus memiliki input dan output. input tidak harus 1 tetapi bisa banyak begitu juga
output. tetapi yang terpenting adalah harus ada input dan output.
•  output bisa ke entitas ataupun ke data store. begitu juga dengan input bisa berasal dari data
store ataupun entitas.
•  tidak boleh ada arus data dari entitas yang langsung ke data store begitupun sebaliknya. harus
melewati proses terlebih dahulu.
•  tidak ada aturan baku untuk level DFD dari sebuah proses. sebuah proses bisa di turunkan
menjadi level 1, 2, 3 ... n. yang paling penting sebuah proses harus di buat dengan detil dan
tentunya konsisten.
DFD LEVEL 1
•  DFD Level 1 provides a more
detailed breakout of pieces
of the Context Level
Diagram.
•  You will highlight the main
functions carried out by the
system, as you break down
the high-level process of the
Context Diagram into its
subprocesses. 
DFD LEVEL 2
•  DFD Level 2 then goes one step deeper into parts of Level 1. It may
require more text to reach the necessary level of detail about the
system’s functioning. 

DFD Level 2 – Pendaftaran Anggota

DFD LEVEL 2 -
PEMBELIAN
DFD LEVEL 2 -
PENJUALAN
• Progression to Levels 3, 4
and beyond is possible, but
going beyond Level 3 is
uncommon. Doing so can
create complexity that
makes it difficult to
communicate, compare or
model effectively.
GOOD LUCK