Pemodelan Sistem 1 Rev
Pemodelan Sistem 1 Rev
Pemodelan Sistem 1 Rev
SISTEM
Dosen
Dosen : Asrul Harun Ismail
Email :
[email protected]
[email protected]
2
Komponen Penilaian
TUGAS & LATIHAN : 30 %
UTS : 30 %
UAS : 40 %
3
REFERENSI
_, System Engineering Fundamental,
DAU, 2001.
Murthy, D.N.P., Page, M.W., and
Rodin,E.Y., Mathematical Modelling,
Pergamon Press, 1990.
Makalah dari beberapa Jurnal Nasional
dan Internasional
BAGIAN 1
PENDAHULUAN
SISTEM dan MODEL
Outline Kuliah:
Sistem (System)
Model
Berpikir Sistem (Systems Thinking)
Teknik Industri Definisi, masalah
khas TI, dan Kebutuhan pendekatan
komprehensif untuk pemecahan
masalah (pengambilan keputusan)
Industrial Engineering (IE)
SISTEM
Definition:
a collection of entities (people, factory orders,
cars, phone calls, data packets, ) which interact
to accomplish some logical purpose.
A collection of elements that function
together to achieve a desired goal
Kumpulan elemen/komponen yang bekerja
bersama untuk mencapai tujuan yang
diharapkan
8
Komponen Sistem
Components of a system:
1. Entities:
- Items processed through the system such as
products, customers, and documents.
2. Attributes:
- Properties of an entity.
3. Activities:
- An operation carried out by entity during a specified
period of time.
- Tasks performed in the system that are either directly
or indirectly involved in the processing of entities.
-Collection of operations that transform the state of an
entity
11
Contoh Sistem Sederhana
12
Sistem dan Lingkungan Luarnya
System: Relationship between Elements
Integrated System
Typical IE Questions
Eksperimen Eksperimen
dengan sistem dengan model
sebenarnya
20
What Does IE Do?
MODEL
Representasi dari sistem
22
What is a Model?
A model is a representation
of a real system.
Physical Models: Toys, flight simulators, wind
tunnels
Mathematical Models: Differential equations,
stochastic models, statistical models, mathematical
programs
Computer Models: Simulation models,
Mathematical programming, stochastics, statistics,
video games, weather forecasters
Bahan Ajar Kuliah Permodelan Sistem
Jurusan Teknik Industri UP 23
KLASIFIKASI MODEL
Tipe Klasifikasi Tipe Model
Fungsi Deskriptif (kondisi nyata )
Prediktif (meramalkan)
Normatif ( seharusnya )
Waktu Statik
Dinamik
Tingkat Uncertainty Deterministik
(Ketidakpastian) Probabilistik
Interaksi dgn Terbuka
lingkungan Tertutup
Tingkat Kuantifikasi Kualitatif
Kuantitatif
Dimensi 2 dimensi
3 dimensi
24
I/O Model of An Open System
QUIZ
Jelaskan apa itu sistem !
Sebutkan komponen komponen sistem,
berikan penjelasannya masing-masing !
Jelaskan apa itu model !
Sebutkan Tipe Klasifikasi Model !
26
BAGIAN 1I
BERPIKIR SISTEM
(System Thinking)
A process is work performed on, or in response to,
incoming data flows or conditions.
Feedack and
Control Loop
A System is a Process
8/29/2017 28
Decomposition is the act of breaking a system into its component
subsystems, processes, and sub processes. Each level of
abstraction reveals more or less detail.
8/29/2017 29
APPLICATION OF SYSTEMS
THINKING
Thinking about phenomena as
hierarchically organised wholes
Identification of some common
principles which enable a system to
be defined and a boundary drawn
around it.
Defining the inputs and outputs
which cross the system boundary.
APPLICATION OF SYSTEMS
THINKING
Identification of the mechanisms of
control by the means of which the
system maintains its identity and
coherence
Identification of the purpose or goals
of the system, and principles by
which its component, or sub-systems
are organised
Depict Conceptual Model
Conceptual (logical) Models
Logical system models depict what a system is
or what a system must donot how the
system will be implemented. Because logical
models depict the essential requirements of a
system, they are sometimes called essential
system models.
Process models (e.g., data flow diagrams)
Data models (e.g., entity relationship diagrams)
Interface models (e.g., context diagrams)
Object models (e.g., Uniform Modeling Language diagrams)
8/29/2017 32
A decomposition diagram or hierarchy chart shows the
top-down, functional decomposition of a system.
8/29/2017 33
Contoh Soal IPO-1
Sistem Informasi Penilaian berjalan sebagai berikut :
1. Data nilai dari dosen diserahkan ke bag
administrasi
2. Bag administrasi mencatat nilai-nilai tsb untuk
dihitung nilai akhirnya
3. Mahasiwa dapat melihat daftar nilai akhir melalui
tampilan dan menerima lembar hasil studi yang
memuat seluruh mata kuliah yg diambil
4. Ketua jurusan menerima laporan hasil studi
Buatlah identifikasi kebutuhan sistem
komputerisasi
(a)proses, (b)data-data, dan (c)model sistemnya
34
Jawab Soal-1
(a) Proses
35
Jawab Soal-1
(b) Data
Masukan (Input / I ): Catatan :
1. Data mahasiswa Masukan adalah data
input yg bisa berupa
Keluaran (Output / O): file, dokumen atau
tampilan
1. Lembar hasil studi
Keluaran adalah data
2. Lap hasil studi
output hsl proses yg
bisa berupa file,
dokumen atau
tampilan
36
Jawab Soal-1
(c) Model Sistem Informasi
38
Jawab Soal-1
(c) Model Sistem Informasi (Lanjutan)
5. P : membuat laporan hasil studi
I : data nilai akhir, data mata kuliah
O : laporan hasil studi.
39
Contoh Soal IPO-2
Sistem Informasi Persediaan Barang berjalan sbb :
1. Dokumen penerimaan barang dari supplier
diterima oleh gudang
2. Bag gudang akan memperbaharui data persediaan
yang ada
3. Petugas dari supplier menerima bukti terima
barang
4. Bag. Administrasi mengajukan permintaan
barang ke gudang, petugas gudang memeriksa
data yg diminta dan mencatat pengeluaran
barang dan memperbaruinya
5. Bag administrasi menerima bukti permintaan
barang
6. Kepala bagian menerima laporan persediaan
barang. 40
Jawab Soal-2 :
Identifikasi Kebutuhan Sistem
Komputerisasi : (a) Proses
41
Jawab Soal-2 :
Identifikasi Kebutuhan Sistem Komputerisasi : (b)
Data Masukan/Keluaran
42
Jawab Soal-2 :
Identifikasi Kebutuhan Sistem Komputerisasi : (c)
Model Sistem Informasi
43
Jawab Soal-2 :
Identifikasi Kebutuhan Sistem Komputerisasi : (c)
Model Sistem Informasi
44
Jawab Soal-2 :
Identifikasi Kebutuhan Sistem Komputerisasi : (c)
Model Sistem Informasi
45
Jawab Soal-2 :
Identifikasi Kebutuhan Sistem Komputerisasi : (c)
Model Sistem Informasi
46
Sebuah Toko swalayan melayani penjualan barang secara
tunai dan kredit (khusus untuk karyawan toko tsb.).
Agar pelayanan yang lebih cepat, sistem ingin dibantu
oleh komputer dengan prosedur sebagai berikut :
1. Pembeli datang dan membawa barang yang dibelinya ke
kasir.
2. Petugas kasir memasukkan barang yang dibeli ke
komputer dan merekamnya ke file penjualan dan secara
otomatis data saldo barang pada file barang di-
updatenya.
3. Petugas menginformasikan total pembayaran ke
pembeli, lalu petugas menerima pembayaran dan
mencatatnya di komputer untuk direkam ke file
pembayaran. Untuk penjualan kredit, petugas mencatat
identitas pembeli dan jumlah uang pembayaran ke file
piutang.
4. Petugas mencetakkan bukti pembayaran untuk pembeli.
5.Setiap hari petugas membuat Laporan penjualan dan
laporan keuangan untuk Supervisor, serta laporan
permintaan barang untuk Gudang.
47
BAGIAN III
PERANGKAT PEMODELAN
SISTEM
(Konvensional)
3.1. Flow Chart
is a type of diagram that
represents an algorithm or
Flow Chart
LS LF LS LF
Activity Name Activity Name LS Activity Name LF
Duration Duration ES Duration EF
ES EF ES EF
PRECEDENCE ARROW
ES : Earliest Start EARLIEST FINISH (EF)
EF : Earliest Finish (EF) = (ES) + (D)
LS : Latest Start
LF : Latest Finish
LATEST START (LS)
(LS) = (LF) - (D)
55
Network Diagram Dependency Types
1. Finish-to-start (FS)
FS
Activity A Activity B B can start if A finishes
2. Start-to-start (SS)
Activity A
SS
Activity B
B cant start until A starts
3. Finish-to-finish (FF)
Activity A
FF B cant finish until A
Activity B
finishes
Activity A
4. Start-to-finish (SF)
Activity B B cant finish until A starts
SF
56
Lag
delay in the successor task. Activity A
Network Diagram Duration = 14 d
Example : FS with 4 days lag
14 Activity B
0
Activity B cannot start until 4 Duration = 2 d
Activity A Lead
Duration = 14 d allows an acceleration of the
successor task.
0 14
FS 4 d lead Lead = - Lag
Example : FS with 4 days lead
Activity B
Duration = 2 d Activity B can start 4 days before
Activity A has finished
10 12
57
Network Diagram example
ACT. PRED. DEPENDEN
CY, LAGS
A10 - FS, 0
A20 A10 FS, 0
A30 A20 FS, 0
A40 A10 FS, 0
A50 A40 FS, 0
A60 A30, A50 FS, 0
58
Sample of Network Diagram
A20 A30
S F
T I
A N
R A10 A60 I
T S
H
A40 A50
59
CPM Calculations
time variable based
(Forward & Backward)
4 A 7 7 A 8
20 30
2 3 5 5 1 6
S F
T I
0 A 2 8 A 13
A N
10 60
R I
T 0 2 2 8 5 13 S
H
0 2 A 6 6 A 8
40 50 13
2 4 6 6 2 8
Terminator
Data Customer
Data Pem bayaran Bag.
Customer
Data Retur Daftar Bayar Keuangan
Sistem
Daftar Barang
Penjualan
Nota Bayar
Tunai
Nota Retur
Data Barang
B
A C F E G
Data
Data Customer
Customer
Data Pembelian Data Daftar 1 Nota 1
Barang Data Pembelian Barang Pembayaran Lap Data
Pembelian
Barang Lap. Data Customer
Barang
Lap.
Cek Daftar & Penjualan
Menghitung Buat Faktur
dftr Barang Penjualan
Cek Daftar
Pembelian
Periksa
& ACC
Data Barang
Laporan
Lap Data
Data Barang Faktur
Customer
Daftar 3 Penjualan
ACC
Pembelian Lap. Data
B
Daftar 2 Barang ACC
Pembelian Buat Lap.
Laporan Buat Penjualan
D Daftar 1
Data Barang Laporan ACC
Pembelian
Penjualan
Buat Lap
Customer
Lap Data 2
Customer
Lap Data
Customer
G
Data Flow Diagrams (DFDs) BAGIAN III
PERANGKAT PEMODELAN
SISTEM
(Konvensional)
3.4. Data Flow Diagram
Data Flow Diagrams (DFDs)
Graphic representation of a system
that uses a small number of symbol
shapes to illustrate how data flows
through interconnected processes
Most natural way to document
processes
Emphasis on processes rather than
data
B-72
Data Flow Diagrams (DFDs)
DFD Symbols
DFDs consist of four symbols
1) Environmental elements called
terminators
Person
Organization
Another system
2) Processes which transform inputs to
outputs
Labeled with verb and object
Also labeled with system or computer program
name
B-73
Data Flow Diagrams (DFDs)
DFD Symbols [cont.]
DFD symbols [cont.]
Data flows which consist of logically
related data elements that travel from one
point or process to another. In other words,
data in motion.
Structures
Diverge
Converge
Data stores which are data repositories. In
other words, data at rest.
B-74
Data Flow Diagrams (DFDs) Mail A Context Diagram of a
Customer Sales Commission System
Sales
Commission
System
Sales
commission
report
Sales
Manager
B-75
Data Flow Diagrams (DFDs)
When Drawing a Context Diagram
1. Use only a single process symbol
2. Label the process symbol to represent
the entire system
3. Do not number the single process
symbol
4. Include all terminators for the system
5. Show all the data flows between the
terminators and the system
B-76
A Data Flow Diagram (Figure
Mail
Data Flow Diagrams (DFDs) Customer
0 Diagram) of a Sales
1.
Open
Commission System
mail Sales
orders
Entered
2. sales orders
Enter sales Sales order
order data
Entered form file
sales order
data
3.
Sort
sales Sorted
order s sales
records
Sales commission
4. report Sales
Compute
sales manager
commissions
Data Flow Diagrams (DFDs)
Figure n Diagrams
Documents a single process of a DFD in
a greater amount of detail
n represents the number of the process
on the next higher level that is being
documented
The term leveled DFDs describe the
hierarchy of diagrams ranging from
context to the lowest-level figure n
diagram
B-78
Data Flow Diagrams (DFDs)
Figure 4 Diagram of a Sales Commission
Sorted System
3
sales
records
4.1
Compute
commission
amounts
Sales
commission
report
4.2 Sales
Accumulate manager
totals
Commission
amounts
Data Flow Diagrams (DFDs)
How Many Levels to Use?
Restrict a single DFD to no more than
six to eight processes
Use another tool to document the
lowest level of detail but use no more
than a single page.
B-80
Data Flow Diagrams (DFDs) Data Flow Diagramming
Guidelines
1. Label each data flow with a unique name.
2. Keep data flow names constant between
levels.
3. Show proper disposition of records deleted
from a data store.
4. When documenting a computer program, do
not include reads/writes.
5. Avoid read-only processes.
6. Write-only processes are permissible when
time serves as the trigger.
B-81
FFBD- Functional Flow Block Diagram BAGIAN III
PERANGKAT PEMODELAN
SISTEM
(Konvensional)
3.5. FFBD
FFBD- Functional Flow Block Diagram
definition :
WEAKNESSES
IDEF models might be so concise that only the
domain experts can understand.
IDEF models are sometimes misinterpreted as
representing a sequence of activities.
The abstraction away from timing, sequencing and
decision logic leads to comprehension difficulties
for the people outside the domain.
IDEF0- Function Modeling Method
EXAMPLE
IDEF0- Function Modeling Method
EXAMPLE (2):
IDEF0- Function Modeling Method
Approach:
IDEF0- Function Modeling Method
IDEF0- Function Modeling Method
Box Syntax:
IDEF0- Function Modeling Method
Arrow Position and role:
IDEF0- Function Modeling Method
Label and name semantic:
IDEF0- Function Modeling Method
Example Top Level:
IDEF0- Function Modeling Method
Structure
Decomposition
IDEF0- Function Modeling Method
Detail Reference
IDEF0- Function Modeling Method
Arrow Fork and Join Structure
IDEF0- Function Modeling Method
Connection Between Boxes:
IDEF0- Function Modeling Method
Boundary and internal arrow:
IDEF0- Function Modeling Method
Typical node tree:
IDEF0- Function Modeling Method Negative Node-Numbered Context :
Integrated Definition (IDEF)
BAGIAN III
PERANGKAT PEMODELAN
SISTEM
Distinguishing properties:
Persistent
May be individuated
Attributes:
Key
Non-key
Relations: Association between entities
IDEF1- Information Modeling Method
IDEF-1
IDEF1- Information Modeling Method
STRENGTHS
IDEF1 requires active participation of the information
users, which serves to accurately model where and
how the information is used and managed.
IDEF-1
STRENGTHS
Powerful tool for data modeling.
IDEF-1X
Denoted as arcs
Logic Process
Denoted as junction boxes Description
Diagram
Unit of Behavior
Denoted as boxes Object
Object State State
Denoted as circles Transition
State Transition Network
Denoted as arcs
Source: http://www.idef.com/idef3.html
IDEF3- Process Description Model
Organizing Structure: Scenario
A scenario can be thought of as a recurring situation, a set of
situations that describe a typical class of problems addressed
by an organization or system, or the setting within which a
process occurs.
IDEF-3
Example
Scenario:
Parts enter the shop ready for the primer coat to be applied.
We apply one very heavy coat of primer paint at a very high
temperature. The paint is allowed to dry in a bake oven after
which a paint coverage test is performed on the part. If the
test reveals that not enough primer paint has been sprayed
on the surface of the part, the part is re-routed through the
paint shop again. If the part passes the inspection, it is routed
to the next stop in the process.
Source: http://www.idef.com/idef3.html
IDEF3- Process Description Model
Process Description Diagram of the Example
IDEF-3
Source: http://www.idef.com/idef3.html
IDEF3- Process Description Model
Object State Transition Network of the Example
IDEF-3
Source: http://www.idef.com/idef3.html
IDEF3- Process Description Model
Other Example
IDEF-3
Is IDEF3 a good
way to represent
process
reference models
Schema ?
Process
Model
Source: http://www.isye.gatech.edu/~lfm/8851/ISyE8851.html
IDEF4- O-O Design Method
IDEF4 method is designed to assist in creating object-oriented
programming software.
IDEF4 provides a framework for navigating an evolving object-
oriented design.
IDEF-4
vocabulary.
General ontology construction steps:
1. catalog the terms;
2. capture the constraints that govern how those
terms can be used to make descriptive statements
about the domain; and
3. build the model.
IDEF5 - Ontology Description
Method
The IDEF5 ontology development process consists of
the following activities.
Data Collection of raw data needed for ontology
IDEF-5
development.
Data Analysis to facilitate ontology extraction.
Initial Ontology Development to develop a
preliminary ontology from the data gathered.
Ontology Refinement and Validation.
REALITY NARRATIVE
MODEL
INTERVENE
SYMBOLIC
MODEL
The
PLANNING
modeling
MODEL cycle COMPUTATIONAL
MODEL
I DEF
NORMATIVE
MODEL SYNTHETIC
MODEL
Rasmussen - Design Maps Definition
Map 1: Domain, tasks, and user in context
Map 2: Knowledge base
Map 3: Road maps for navigation
Map 4: Knowledge representation in
design
Map 5: Display composition
Side by Side Comparison
Map 1: Domain, tasks, IDEF0 (IDEF Function
and user in context Modeling)
Map 2: Knowledge base IDEF1 (IDEF Information
Modeling)
Map 3: Road maps for
IDEF1X (IDEF Data
navigation Modeling)
Map 4: Knowledge IDEF3 (IDEF Process
representation in design Modeling)
Map 5: Display IDEF4 (IDEF Object-
composition Oriented Design)
IDEF5 (IDEF Ontology
Description Capture)
Rasmussen Map 1 compared to IDEF0-
Diagram
Decomposition Diagram: links together the context
diagrams Means-Ends Representations/Properties
Goals, WHY
constraints
Abstract WHAT
WHY
functions
General WHAT HOW
functions WHY
Tenaga Kerja
Energi Harga
Kuantitas Produksi
Kuantitas Permintaan
Harga Harga
Kuantitas Kuantitas
Biaya Biaya
Komposisi Komposisi
147
A Systems View of Manufacturing
Manufacturing can be viewed either as a
transformation process or as a system.
As a Transformation Process: A
narrow definition of manufacturing is that
it a process of transformation where raw
material are converted into products.
As a System: Manufacturing is not
limited to materials transformation
performed in a factory. Rather, it is a
complex system comprising of several
elements.
Flow of Materials, Information and Cost
PLANNING
Information
RAW Flow of Materials
MATERIALS PROCESS PRODUCTS
Flow of
CONTROL
Flow
of cost
MANAGEMENT
TECHNOLOGY
OPERATIONS
OUTPUTS
PRODUCTS/SERVICES
FINANCIAL
CONSEQUENCES
HUMAN
CONSEQUENCES
Karakteristik
Memisahkan pengambilan keputusan menjadi
beberapa tahapan untuk masalah yang kompleks
Menyediakan kerangka analitik (berbasis rasional)
untuk pengambilan keputusan
Dapat diterapkan untuk proses yang kompleks,
interaktif, dan mahal
Menyeluruh (Comprehensive)
Sub-system dihubungkan melalui keputusan-
keputusan utama
Pendekatan sistem
Problem
Objectives Criteria
Definition
Constraints Alternatives
ukuran performa
Dapat dirangking dan dibandingkan
dengan tujuan
Harus relevant dan dapat diperoleh
(collectable)
Contoh: suhu, waktu, kecepatan, dsb
Kendala akan membatasi derajat
ketersediaan sumberdaya atau
CONSTRAINTS
permasalahan (problem)
Analis harus kreatif dan inovatif
Alternatif do nothing harus menjadi
salah satu alternatif yang
dipertimbangkan dan digunakan sebagai
dasar untuk membandingkan performa
alternatif yang lain
Data collection
Dapat berupa data primer atau data
sekunder
Data primer: langsung dari sumber
data kepada pengumpul data
Data sekunder: tidak langsung dari
sumber data, misalnya melalui orang
lain atau dokumen
Teknik pengumpulan data: wawancara,
kuisioner, observasi
Model matematis
Merupakan sebuah sistem persamaan-persamaan
dan ekspresi matematis yang mendeskripsikan
esensi dari masalah
Simbol-simbol matematis digunakan untuk
merepresentasikan variabel-variabel
Diasumsikan bahwa semua variabel bisa
dikuantifikasikan
Hubungan antara variabel diekspresikan sebagai
fungsi matematis untuk mendeskripsikan
perilaku sistem
Teknik matematis digunakan untuk
menyelesaikannya, misalnya linear programming
Contoh
Pembakaran bahan bakar A menghasilkan 3kg
polutant , sedangkan B menghasilkan 5kg
polutant per tonnya. Per tonnya, A
menghasilkan 10 unit energi, sedangkan B
menghasilkan 12 unit. Maksimum 4 ton bahan
bakar dapat diproses setiap jamnya dan tidak
lebih dari 15kg polutant yang diijinkan untuk
dihasilkan setiap jamnya. Untuk
memaksimalkan energi yang dihasilkan,
berapakah masing-masing bahan bakar
dapat diproses?
Model simulasi
Merupakan replikasi atau imitasi perilaku
dari sebuah sistem
Variasi acak dapat diperhitungkan
Hubungan yang kompleks dapat dimodelkan
Sample design dan teknik statistik digunakan
untuk menganalisis hasil
Evaluation
Merupakan perbandingan metodikal dari
alternatif, berdasarkan kriteria-kriteria
tertentu, seperti ekonomi, sosial, finansial,
dsb.
Dilakukan pula perbandingan akan prediksi
konsekuensi dari setiap alternatif.
Teknik multi-attribute analysis biasanya
digunakan, seperti AHP (analytical hierarchy
process).
Sensitivity analysis
Merupakan investigasi variabilitas efek-efek
yang diprediksi dari alternatif, kaitannya
dengan asumsi yang dibuat.
Contoh parameter:
Prediksi kondisi ekonomi, mis. suku bunga
Tingkat demand, mis. Tingkat pertumbuhan
Umur asset atau teknologi
Biaya operasional dan pemeliharaan
Implementation
Merupakan kegiatan menterjemahkan hasil
ke dalam instruksi operasional
Membutuhkan:
Systems Synthesis
Validation