Pert 5 model proses

1

Model Proses Perangkat Lunak

Rekayasa Perangkat LunakDosen : Citra Noviyasari, S.Si, MT

Rekayasa Perangkat Lunak - Citra N., S.Si, MT

2

Ciri-ciri software yang baik

• Maintainability (dapat dipelihara)– Software bisa menangani perubahan spek

kebutuhan• Dependability (dapat diandalkan)

–Aman, selamat, tidak menyebabkan keruksakan fisik• Efficiency (Efisien)

– Software mampu mengoptimalkan resource• Acceptability (Kemampupakaian)

– Software bisa diterima user sebagaimana rancangan. Mudah dimengerti, digunakan and compatible dengan sistem yang lain


3

Produk SoftwareGenerik (terbuka utk siapapun) ≈ DBMS,

Word Processor, Sistem Operasi, paket untuk menggambar, alat bantu manajemen proyek

◦ Spek hanya dikontrol oleh sendiri oleh Vendor Software

Pesanan (disesuaikan dgn kebutuhan pelanggan tertentu saja)

◦ Berdasarkan kontrak kerja◦ Spek dikontrol oleh pelanggan tertentu


4

Model Proses Software

Waterfall (linear)

Evolutionere (iterasi)

Component-based


5

Model Proses Software

Waterfall – pengembangan yang bersifat linear dari mulai spesifikasi s/d pemeliharaan.

Evolutionere – pendekatan tumpang tindih kegiatan spesifikasi, pengembangan, dan validasi. Sistem sejak awal dikembangkan dgn cepat berdasarkan spesifikasi abstrak, lalu disempurnakan berdasarkan masukan dari pelanggan sampai sistem dapat memenuhi kebutuhan pelanggan tersebut.

Component-based – pengembangan dengan cara menggunakan komponen yang dapat dipakai ulang.


6

Model Waterfall


#Bukan model linear murni

7

Analisis Waterfall

FeaturesSistematis, setiap tahapan prosesnya jelasSudah terbukti handalCocok untuk pengembangan software yang

bersifat generik◦ Prosesnya sudah benar-benar jelas dan tidak

berubah-ubah


8

Spiral model of the software process


Riskanalysis

Riskanalysis

Riskanalysis

Riskanalysis Proto-

type 1

Prototype 2Prototype 3

Opera-tionalprotoype

Concept ofOperation

Simulations, models, benchmarks

S/Wrequirements

Requirementvalidation

DesignV&V

Productdesign Detailed

design

CodeUnit test

IntegrationtestAcceptance

testService Develop, verifynext-level product

Evaluate alternativesidentify, resolve risks

Determine objectivesalternatives and

constraints

Plan next phase

Integrationand test plan

Developmentplan

Requirements planLife-cycle plan

REVIEW

9

Evolutionary development

• Exploratory development – Objective is to work with customers and to

evolve a final system from an initial outline specification. Should start with well-understood requirements and add new features as proposed by the customer.

• Throw-away prototyping– Objective is to understand the system

requirements. Should start with poorly understood requirements to clarify what is really needed.


10

Iterative


11

Component-based software engineering

• Based on systematic reuse where systems are integrated from existing components or COTS (Commercial-off-the-shelf) systems.

• Process stages– Component analysis;– Requirements modification;– System design with reuse;– Development and integration.

• This approach is becoming increasingly used as component standards have emerged.


12

Component Based


Requirementsspecification

Componentanalysis

Developmentand integration

System designwith reuse

Requirementsmodification

Systemvalidation

13

RUP phase model


Phase iteration

Inception Elaboration Construction Transition

14

The Systems Engineering Process


Systemintegration

Sub-systemdevelopment

System

design

Requirementsdefinition

Systeminstallation

System

evolution

Systemdecommissioning

* Software Engineering 7th ed, Ian Sommerville

15

Software Process

Serangkaian kegiatan dan hasil-hasilnya yang diperlukan untuk menghasilkan aplikasi tertentu.


Spesifikasi

Pengembangan

Validasi

Evolusi

16

Proses Rekayasa Persyaratan


Feasibilitystudy

Requirementselicitation and

analysisRequirementsspecification

Requirementsvalidation

Feasibilityreport

Systemmodels

User and systemrequirements

Requirementsdocument

17

Proses Perancangan Software


Tahapan perancangan bersifat urut/sekuensial

18

System evolution


Assess existingsystems

Define systemrequirements

Propose systemchanges

Modifysystems

Newsystem

Existingsystems

Pert 5 model proses

Engineering

Transcript of Pert 5 model proses