http://www.brigidaarie.com
Process
OUTPUT
ACTIVITIES (TASKS), CONSTRAINTS, RESOURCES
[ Results ]
INPUT
[ Source ]
[ Product ]
[ Requirements ]
[ Set of Goals ]
PROCEDURES
[ Standards ]
TOOLS & TECHNIQUES
Karakteristik
Process
• Kegiatan-kegiatan • Menggunakan sumberdaya • Terdiri dari sub-proses • Memiliki kriteria In & Out FINAL OUTPUT [ Results ] [ Product ] [ Set of Goals ] [ Standards ]
• Dilakukan berurutan • Memiliki panduan • Memiliki kendala & kontrol
Proses Seleksi Calon Karyawan
INPUT [Data pendaftar]
ACTIVITIES (TASKS), CONSTRAINTS, RESOURCES
PROCEDURES TOOLS & TECHNIQUES
OUTPUT [Pendaftar diterima/ditolak]
Constraint • Kebutuhan
• Nilai gaji
Maintenance
Maintenance
System Delivery
Activity Activity Activity Activity
Activity
Activity
Definition phase
Strategy Planning
Maintenance phase
Feasibility Study
Requirements analysis & definition Testing
Requirement Analysis
Activity Integration Testing System Testing
Implementation
Program Implementation Unit Testing
Design
Development phase
System Design Program Design
Problem Definition
Technical Development
Status Quo
Solution Integration
Waterfall Model • “V” Model
Prototyping Model • Throw away • Evolutionary
RAD Model • Incremental Model • Iterative Model
Spiral Model
Model Waterfall Evaluasi costs & benefits Status Quo & Problem Identification
Output: feasibility report
Feasibility Study
Definisi permasalahan Pilihan solusi & benefits Sumber daya yang dibutuhkan & scheduling
Detailed Analysis Detailed Design Construction Testing System Delivery
System / Information engineering
Operation & Maintenance
[Roger. S. Pressman]
Model Waterfall Identitifikasi requirements Status Quo & Problem Identification
Feasibility Study Investigation Requirement Analysis
Fungsionalitas Kualitas
Output: req specification document
Detailed Analysis
Detailed Design
Functional req Non-functional req Quality controls
Construction Testing System Delivery
System / Information engineering
Operation & Maintenance
[Roger. S. Pressman]
Model Waterfall Status Quo & Problem Identification Feasibility Study Detailed Analysis System Design
Detailed Design
Program Design Construction
Pembangunan modul sistem Output: design spec. and document
Testing
S/W Architecture Its relationships
System Delivery
System / Information engineering
Operation & Maintenance
[Roger. S. Pressman]
Model Waterfall Status Quo & Problem Identification Feasibility Study Detailed Analysis Detailed Design Coding
Construction
Unit & Integration Test
Module Testing Testing
System Test: Tes fungsional Tes Kinerja User Acceptance Test Tes instalasi
System Delivery
System / Information engineering
Operation & Maintenance
[Roger. S. Pressman]
Terperinci dan detil
Cocok untuk developer pemula
Dinyatakan sebelum masuk tahap berikutnya
Berfokus pada dokumentasi
Jarang sesuai urutan yang direncanakan Iterations confusion Ketidakpastian (Kesulitan memetakan SEMUA user req) • Apakah sistem memenuhi harapan user?
Ketidak jelasan proses pengembangan • Tidak ada pengecekan kembali
Produk baru muncul diakhir tahapan Tidak terdapat pedoman, jika terjadi perubahan
Prototyping Model Pengembangan produk sebagian • Pemeriksaan thd Customers & developers • Memeriksa setiap aspek sistem yg diusulkan • Kesesuaian dan Ketepatan
Cepat Pembangunan (all / part)
Pemahaman dan klarifikasi masalah
Prototyping Model Lists of Revisions
Lists of Revisions
Lists of Revisions
Prototype Requirements
Prototype Design
Prototype System
System Requirements
Test
Delivered System
Prototyping Model
Alternatif desain mengungkap permasalahan Kembali dalam aktifitas req
Sediakan alternatif desain Direvisi sampai sesuai Lists of Revisions
Lists of Revisions
Lists of Revisions
Prototype Requirements
Prototype Design
Prototype System
System Requirements
Program mulai dibangun Tiap perubahan dibahas
Test
Delivered Delivered System
System
Waterfall-Prototype
Validation
Memastikan semua req terpenuhi, setiap fungsi dapat ditelusuri sesuai dengan req Verification Mengecek kesesuaian masing-masing fungsi (quality)
“V” Model Masalah yang ditemukan langsung diperbaiki, desain dan coding sebelum tesing dilakukan kembali V-model fokus pada aktifitas dan perbaikan berkesinambungan
Rapid Application Development Incremental • End-users melakukan evaluasi pada setiap tahap Siklus pengembangan pendek
• Adaptasi • Model linear (Waterfall) • Perkembangan yang pesat • Menggunakan pembangunan component-based • Periode singkat • 60 – 90 hari
Rapid Application Development
Pemodelan fungsi bisnis (information flow) What info ? business process What info is generated ? Who processes it ? Who generates it ? Where does info go to next ?
Team # 3 Business modeling Data modeling
Team # 2 Process modeling
Business modeling
Team # 1
Application generation
Data modeling
Testing & turnover
Process modeling
Business modeling
Application generation
Data modeling
Aliran informasi disempurnakan menjadi obyek data Karakteristik obyek data diidentifikasi Hubungan antara obyek data didefinisikan
Testing & turnover
Process modeling Application generation Testing & turnover
60 – 90 days
Rapid Application Development Obyek data berubah utk
Team # 3
melaksanakan fungsi bisnis Dibuat deskripsi pemrosesan Add, Modify, Delete & Retrieve Menggunakan 4th
Generation techniques (misal: Code generators) Reusable components Automated tools Menekankan
Team # 1
Business modeling Data modeling
Team # 2 Process modeling
Business modeling
Application generation
Data modeling
Testing & turnover
Process modeling
Business modeling
Application generation
Data modeling
Testing & turnover
Process modeling Application generation
penggunaan kembali
Banyak komponen yg telah diuji Komponen baru yg akan diuji
Testing & turnover
60 – 90 days
Incremental Model Requirements dipartisi menjadi subsistem dengan
fungsionalitasnya
Use Case 1
Use Case 1 Use Case 2
Use Case 1 Use Case 2 Use Case 3
Iterative Model Memberikan full-system diawal, kemudian merubah
fungsionalitas dari setiap subsistem dengan setiap rilis terbaru
Use Case 1 Use Case 2 Use Case 3 (release 1)
Use Case 1 Use Case 2 Use Case 3 (release 2)
Use Case 1 Use Case 2 Use Case 3 (release 3)
Sesuai utk proyek singkat
Pembangunan yg cepat • Automated tools
Kesulitan pengujian minimum • Reusable components
Pendekatan straight-forward
Keuntungan-RAD
Kekurangan-RAD Tidak sesuai utk proyek besar • Melibatkan banyak tim yg bekerja
Komitmen penuh tim deadlines Tidak sesuai untuk: • Systems fine tuning • System interaksi teknologi baru • System interaksi sistem yg lainnya
Spiral Model Bentuk Sederhana
• Model waterfall plus analisis resiko sebelum setiap tahap • Resiko tdk dpt diselesaikan -> Proyek dihentikan
Spiral Model
Spiral Model EVALUATE ALTERNATIVES AND RISKS
DETERMINE GOALS, ALTERNATIVES, CONSTRAINTS
Risk analysis4
Risk analysis3
Risk analysis2
Risk analysis1 Budget4
Budget3
Budget2
Budget1 start
Requirements, life-cycle plan
Prototype1
Prototype2
Prototype3
Prototype4
Concept of operation
Detailed design
Code
Unit test
Implementation plan
PLAN
Acceptance test
System test
DEVELOP AND TEST
Spiral Model Pengaturan Tujuan
• Tujuan khusus untuk setiap fase diidentifikasi
• Resiko dinilai dan kegiatan dilakukan Penilaian &Pengurangan Resiko utk mengurangi resiko Pengembangan dan Validasi
Perencanaan
• Model pengembangan dipilih • Proyek telah dikaji, selanjutnya dilakukan perencanaan
