Chapter 3

Process Models

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Generic Process Framework

Communication

Planning

Modelling

Construction

Deployment

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Process Flow

Linear

Iterative

Mengulang 1 atau lebih aktifitas sebelum melanjutkan ke

aktifitas selanjutnya

Evolutionary

Menjalankan kelima aktifitas secara berurutan

Menjalankan kelima aktifitas secara berputar

Setiap perputaran menghasilkan versi SW yang lebih
lengkap

Parallel

Menjalankan satu atau lebih aktifitas secara paralel

Roger S. Pressman, Software Engineering a
Practitioner's Approach, 2010

Linear Process Flow

Communication

Planning

Modelling

Construction

Deployment

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Iterative Process Flow

Communication

Planning

Modelling

Construction

Deployment

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Evolutionary Process Flow

Planning
Modelling
Communication

Construction
Increment released

Deployment

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Parallel Process Flow

Communication

Planning
Time

Modelling

Construction

Deployment

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Process Models

Waterfall

Incremental

Spiral

..dll

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Waterfall

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Waterfall
Systematic sequential approach to software
development

Requirements are well understood

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Waterfall - disadvantages

Changes can cause confusion as the project

team proceeds
It's often difficult for the customer to state all
requirements explicitly
Customers must have patience
Some projects team members must wait for
other members of the team to complete
dependent tasks
Roger S. Pressman, Software Engineering a
Practitioner's Approach, 2010

Incremental

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Incremental

Combination of elements of linear and parallel

process flows
Initial software requirements are reasonably
well defined
May be a compelling need to provide a limited
set of software functionality to users quickly
Refine and expand the functionality in later
software releases
Roger S. Pressman, Software Engineering a
Practitioner's Approach, 2010

Incremental

The first increment is often a core product

Basic requirements are addressed but many
supplementary features (some known, others
unknown) remain undelivered

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010

Spiral

Roger S. Pressman, Software Engineering a

Practitioner's Approach, 2010