Pemodelan Terstruktur
Model yang dibuat harus fokus pada kebutuhan yang relevan dengan
domain permasalahan WHAT
Setiap model kebutuhan harus bisa dilacak ke model perancangan
traceability
Setiap elemen dalam model kebutuhan harus mampu memperjelas
pemahaman secara utuh terhadap kebutuhan PL domain masalah,
fungsionalitas dan perilaku sistem
Minimalisasi kopling antar klas
Memastikan bahwa model kebutuhan memiliki nilai manfaat untuk seluruh
stakeholders
Model dibuat sesederhana mungkin notasi yang sederhana, non
duplikasi informasi
Scenario-based models
Berdasarkan sudut pandang aktor
Data models
Menjelaskan domain informasi dari masalah
Class-oriented models
Merepresentasikan klas-klas yang relevan dengan kebutuhan PL
Flow-oriented models
Merepresentasikan proses dan data dari sistem
Behavioral models
Merepresentasikan perilaku sistem berdasar event
Processes
Data Behavior
Process
Data Object
Specification
Description
(PSPEC)
Data Flow
ER Diagram Diagram
(DFD)
Data
Dictionary
State
Transition
Diagram
(STD)
Control
Specification
(CSPEC)
Data Dictionary
Representasi Simbol :
= : composed of + : and
{} : iterations of [….|…] : selection / or
() : optional “ “ : literal
* * : comment/description
Vend product (partly) :
Name Element Type
object [coin | slug](product) data
product [ice cream | coffee | candy] data
coins 0{[quarter | nickel | dime]}8 data
product available [TRUE | FALSE] control
[“YES” | “NO”]
quarter *25 cents US currency*
coin return request [TRUE | FALSE] control
Entity Relationship Diagram (Data
Model)
Komponen ERD :
Entitas (atribut dan nilai atribut)
Sebuah barang (sesuatu) atau obyek yang dapat dibedakan dari obyek lain
Relasi
Hubungan antara 2 atau lebih entitas
Atribut
Properti yang dimiliki oleh sebuah entitas
Data object
represents a composite information
consists of a number of different attributes or properties
encapsulates data only no operation applied to its data
can be external entity, thing, occurrence/event, role, organizational unit,
structure, etc.
e.g. dimensions (height, weight, depth), cars (make, model, ID, body type, color,
owner)
can be represented in a tabular representation
Process
Representasi aktifitas sistem
1
Notasi: lingkaran Proses A
Memproses data
Storage
Representasi tempat penyimpanan data
Notasi: dua garis paralel data X
Data flow in = diubah, data flow out = dibaca
Control bar
Representasi spesifikasi kontrol
Notasi: garis tegak
RPL - Rekayasa Kebutuhan PL - Pemodelan / Tri A. Kurniawan.,S.T, M.T, Ph.D
Panduan DFD
Harus konsisten
Pada masing-masing diagram
(tiap level) hanya memiliki satu
control bar
object
returned coins
0*
customer
selection Vend
Customer Customer
product
slug
product
coin return
request product
available
RPL - Rekayasa Kebutuhan PL - Pemodelan / Tri A. Kurniawan.,S.T, M.T, Ph.D
Data/Control Flow Diagram (DFD/CFD
level 1)
coin return
object request
coins
1* 5* returned coins
slug payment Dispense
Get
customer change
payment change due
sufficient
coin detected payment 3p
Validate product
payment product
price 6p
available product
2p Dispense
dispensed
Get product
product
4p valid selection
price valid selection
price table Get valid
selection
customer product products
selection
RPL - Rekayasa Kebutuhan PL - Pemodelan / Tri A. Kurniawan.,S.T, M.T, Ph.D available
Data/Control Flow Diagram (DFD/CFD
level 2)
DFD/CFD level 2 : Dispense change
coin return
request
product
change due
available
5.2p
payment coins
Get
coins payment
coin
payment
RPL - Rekayasa Kebutuhan PL - Pemodelan / Tri A. Kurniawan.,S.T, M.T, Ph.D
Process model – Process specification
Waiting for a
coin payment returned
accept new coin
coin detected
accept customer coin return request
request return payment
product dispensed
Waiting for Returning
accept new coin
selection payment
product
sufficient payment available=FALSE
dispense product return payment
Dispensing
product
Behavior model (1)
TRUE TRUE 1 0
D/C FALSE 0 1