Hanya digunakan di lingkungan Universtias

Presentasi berjudul: "Hanya digunakan di lingkungan Universtias"— Transcript presentasi:

1 Hanya digunakan di lingkungan Universtias
Catatan Kuliah Rekayasa Perangkat Lunak (Software Engineering) Bagian 1 copyright © 2006 R.S. Pressman & Associates, Inc , Hanya digunakan di lingkungan Universtias Hanya boleh digandakan untuk mahasiswa di lingkungan universitas yang menggunakan buku Software Engineering: A Practitioner's Approach. Selain itu dilarang keras menggandakan. Presentasi, slide atau hardcopy tidak boleh digunakan untuk short courses, seminar industri, atau kepentingan konsultasi. These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

2 Software Engineering: A Practitioner’s Approach, 6/e Bab 2 Proses : Pandangan Umum copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. Hanya digunakan di lingkungan Universtias Hanya boleh digandakan untuk mahasiswa di lingkungan universitas yang menggunakan buku Software Engineering: A Practitioner's Approach. Selain itu dilarang keras menggandakan. These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

3 Definisi Pembangunan dan Pengggunaan prinsip-prinsip rekayasa dalam rangka mendapatkan perangkat lunak yang ekonomis yang handal dan bekerja efisien pada komputer yang nyata (Fritz Bauer) IEEE Aplikasi pendekatan sistematik, disiplin, terquantifikasi pada pengembangan, operasi, perawatan perangkat lunak, yaitu aplikasi rekayasa pada perangkat lunak Studi pendekatan-pendekatan di atas These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

4 Teknologi Berlapis Rekayasa Perangkat Lunak tools methods
process model a “quality” focus These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

5 Software Engineering Software engineering mencakup proses, teknik manajemen, metoda-metoda teknis dan penggunaan tools. These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

6 Pandangan Umum RPL Rekayasa : analisis, desain, konstruksi, verifikasi, dan manajemen entitas teknis (dan sosial) Problem apa yang harus diselesaikan ? Karakteristik entitias apa yang digunakan untuk menyelesaikan masalah ? Bagaimana entitas (dan solusinya) direalisasikan ? Bagaimana entitas di konstruksi ? Pendekatan apa yang digunakan untuk menemukankesalahan yang dibuat pada desain dan konstruksi entitas ? Bagaimana entitas didukung dalam jangka panjang, dimana koreksi, adaptasi, dan peningkatan selalu diminta pengguna pada entitas These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

7 Tiga Fase Umum RPL Fase definisi, fokus pada pertanyaan “apa”
Fase pengembangan, fokus pada pertanyaan “bagaimana” Fase dukungan, fokus pada “perubahan” : Koreksi Adaptasi Peningkatan Pencegahan These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

8 Bingkai Kerja Proses Bingkai Kerja Proses Aktivitas Bingkai Kerja
Tugas-tugas Produk-produk milestones & deliverables QA checkpoints Aktivitas Payung These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

9 Aktivitas Bingkai Kerja
Komunikasi Perencanaan Pemodelan Analisis Kebutuhan Desain Konstruksi Menyusun kode Pengujian Produksi These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

10 Aktivitas Payung Manajemen Proyek PL Review Teknik Formal
Jaminan Mutu PL Manajemen Konfigurasi PL Persiapan dan Produksi Produk Pekerjaan Manajemen Penggunaan Kembali Pengukuran Manajemen Resiko These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

11 Model Proses : Adaptabilitas
Aktivitas-aktivitas bingkai kerja akan selalu diaplikasikan pada setiap project, tetapi …. Tugas-tugas (dan derajat kekakuan) pada setiap aktivitas akan bervariasi bergantung pada : Tipe proyek Karakteristik proyek Penilaian umum; persetujuan tim proyek These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

12 Software Engineering Institute (SEI) Capability Maturity Model (CMM)
Level 1: Mengawali (ad hoc software processes) Level 2: Mengulang (bisa mengulang keberhasilan terdahulu) Level 3: Menentukan ( manajemen dan dokumentasi proses rekayasa, standarisasi, dan integrasi ke bentuk organisasi -proses software yang lebih luas) Level 4; Mengatur (proses software process dan produk secara kuantitas dan dikontrol menggunakan tingkat pengukuran yang rinci) Level 5: Optimasi (secara kontinyu meningkatkan proses yang dimungkinkan dengan cara secara kuantitatif memberikan feedback mengenai idea proses dan inovasi pengujian) These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

13 CMMI CMMI menentukan setiap area proses dalam hal “tujuan spesifik” dan “langkah-langkah spesifik” yang dibutuhkan untuk menggapai tujuan-tujuan tersebut. Tujuan-Tujuan Spesifik membangun karakteristik-karakteristik yang harus ada jika aktivitas yang dilakukan sebuah proses adalah efektif. Langkah-Langkah Spesifik membuat sebuah tujuan menjadi sekelompok aktivitas-aktivitas yang berkaitan dengan proses. These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

14 Pola-Pola Proses Pola-pola proses menentukan sekelompok aktivitas, aksi, tugas-tugas pekerjaan, produk-produk pekerjaan dan/atau perilaku yang berkaitan Sebuah template digunakan untuk menentukan pattern/pola Contoh-contoh umum : Komunikasi pelanggan (sebuah aktivitas proses) Analisis (sebuah aksi) Pengumpulan Kebutuhan (sebuah tugas proses) Review sebuah produk kerja (sebuah tugas proses) Model Desain (sebuah produk kerja) These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

15 Asesmen Proses Sebuah proses harus dinilai untuk memastikan bahwa mereka memenuhi sekumpulan kriteria proses dasar yang penting bagi rekayasa PL yang sukses. Beberapa pilihan penilaian yang tersedia : SCAMPI CBA IPI SPICE ISO 9001:2000 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

16 Penilaian dan Peningkatan
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

17 Proses Personal PL (PSP)
Rekomendasi 5 aktivitas bingkai kerja : Perencanaan Desain level tinggi Review Desain level tinggi Pengembangan Postmortem Penekanan pada kebutuhan software engineer untuk mengidentifikasi kesalahan di awal waktu, dan memahami tipe-tipe kesalahan tersebut These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

18 Proses Tim PL (TSP) Setiap proyek diluncurkan menggunakan sebuah script yang mendefinisikan tugas-tugas yang harus diselesaikan Tim diarahkan secara mandiri Pengukuran dianjurkan Pengukuran dianailisis dengan tujuan meningkatkan proses tim These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

19 Tujuan Utama Proses PL : Kualitas Tinggi
Ingat: Kualitas Tinggi = Proyek pendek Mengapa? Sedikit/Tidak ada Pekerjaan ulang! These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005

20 Process as Problem Solving

21 The Linear Model

22 Iterative Models Prototyping RAD

23 The Incremental Model

24 An Evolutionary (Spiral) Model

25 Still Other Process Models
Component assembly model—proses memanfaatkan s/w untuk digunkan kembali merupakan tujuan pengembangan Concurrent process model—bagian proses yang berbeda dipisahkan dalam proses lain Formal methods—proses diterapkan ketika spesifikasi matematis dikembangkan Cleanroom software engineering—menekankan pada tidak adanya error sebelum pengujian

26 Software Process Models
Linear Sequential Model (old fashioned but reasonable approach when requirements are well understood) Prototyping Model (good first step when customer has a legitimate need, but is clueless about the details, developer needs to resist pressure to extend a rough prototype into a production product) Rapid Application and Development (RAD) Model (makes heavy use of reusable software components with an extremely short development cycle) Incremental Model (delivers software in small but usable pieces, each piece builds on pieces already delivered) Spiral Model (couples iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model) Win-Win Spiral Model (eliciting software requirements defined through negotiation between customer and developer, where each party attempts to balance technical and business constraints) Concurrent Development Model (similar to spiral model often used in development of client/server applications) Component-Based Development (spiral model variation in which applications are built from prepackaged software components called classes) Formal Methods Model (rigorous mathematical notation used to specify, design, and verify computer-based systems) Fourth Generation (4GT) Techniques (software tool is used to generate the source code for a software system from a high level specification representation) These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005