Software Engineering: A Practitioners Approach, 6/e

Chapter 3
Prescriptive Process Models
copyright 1996, 2001, 2005

R.S. Pressman & Associates, Inc.

For University Use Only
May be reproduced ONLY for student use at the university level
when used in conjunction with Software Engineering: A Practitioner's Approach.
Any other reproduction or use is expressly prohibited.

Thesecoursewarematerialsaretobeusedinconjunction

Prescriptive Models
Prescriptive process models advocate an orderly approach to
software engineering
That leads to a few questions
If prescriptive process models strive for structure and order, are they
inappropriate for a software world that thrives on change?
Yet, if we reject traditional process models (and the order they
imply) and replace them with something less structured, do we
make it impossible to achieve coordination and coherence in
software work?

Thesecoursewarematerialsaretobeusedinconjunction

The Waterfall Model

Communication
project initiation
requirement gathering

Planning
estimating
scheduling
tracking

Modeling
analysis
design

Construction
code
test

Deployment
delivery
support
f eedback

Thesecoursewarematerialsaretobeusedinconjunction

The Incremental Model

increment #n
Com
m
unicationPlanning

M
o
de
lin
g
a
dn
ea
sliy
gs
nis

delivery of
nth increment

increment #2
Com
m
unicationPlanning
increment #1
Com
m
unicationPlanning

M
od
e
ling
a
dn
ea
sliy
gs
nis

Co
ns
truction D
c
e
p
lo
ym
e
t
to
ed
se
t
d
e
liv
e
yn
fe
e
db
arc
k

Co
ns
truction D
c
e
p
lo
ym
t
to
ed
se
t
d
e
liv
e
re
yn
fe
e
db
a
c
k

M
od
e
ling
a
dn
ea
sliy
gs
nis

Co
ns
truction D
c
e
p
lo
ym
t
to
ed
se
t
d
e
liv
e
re
yn
fe
e
db
a
c
k

delivery of
2nd increment

delivery of
1st increment

project calendar time

Thesecoursewarematerialsaretobeusedinconjunction

The RAD Model

Team#n
Modeling

businessmodeling
datamodeling
processmodeling

Co
nstruction
componentreuse

Team#2

Communication

automaticcode
generation
testing

Modeling

businessmodeling
datamodeling
processmodeling

Planning

Construction

Team#1
Modeling

component reuse
automaticcode
generation
testing

Deployment
integration
delivery
feedback

business modeling
data modeling
process modeling

Construction

component reuse
automatic code
generation
testing

60 - 90 days

Thesecoursewarematerialsaretobeusedinconjunction

Evolutionary Models: Prototyping

Quick
plan
Quick
Communication
communication

plan

Mod
eling
Modeling
Quick design
Quick design

Deployment
Deployment
Delivery
delivery
&
&
Feedback
feedback

Construction
Construction
of
of prototype
prototype

Thesecoursewarematerialsaretobeusedinconjunction

Evolutionary Models: The Spiral

planning
estimation
scheduling
risk analysis

communication
modeling
analysis
design
start

deployment
delivery
feedback

construction
code
test

Thesecoursewarematerialsaretobeusedinconjunction

Evolutionary Models: Concurrent

no ne
M o deling a c t iv it y

represents thestate
of asoftwareengineering
activityor task

U nder
dev elo pm ent

A w a it ing
c ha nges

U nder rev iew

U nder
rev is ion

B a s elined

Done

Thesecoursewarematerialsaretobeusedinconjunction

Still Other Process Models

Component based developmentthe process to apply

when reuse is a development objective
Formal methodsemphasizes the mathematical
specification of requirements
AOSDprovides a process and methodological
approach for defining, specifying, designing, and
constructing aspects
Unified Processa use-case driven, architecture-centric,
iterative and incremental software process closely
aligned with the Unified Modeling Language (UML)
Thesecoursewarematerialsaretobeusedinconjunction

The Unified Process (UP)

Elaboration
elaboration
Inception
inception

inception

construction
Release
softwareincrement

transition

production

Thesecoursewarematerialsaretobeusedinconjunction

10

UP Phases
UP Phases
Inception

Elaboration

Construction

Transition

Production

Workflows
Requirements
Analysis
Design
Implementation
Test
Support
Iterations

#1

#2

#n-1

#n

Thesecoursewarematerialsaretobeusedinconjunction

11

Inception phase
Vision document
Initial use-case model
Initial project glossary
Initial business case
Initial risk assessment.
Project plan,
phases and iterations.
Business model,
if necessary.
One or more prototypes
Incept io
n

UP Work Products
Elaboration phase
Use-case model
Supplementary requirements
including non-functional
Analysis model
Software architecture
Description.
Executable architectural
prototype.
Preliminary design model
Revised risk list
Project plan including
iteration plan
adaptedworkflows
milestones
technical work products
Preliminary user manual

Construction phase
Design model
Software components
Integrated software
increment
Test plan and procedure
Test cases
Support documentation
user manuals
installation manuals
description of current
increment

Transition phase
Delivered software increment
Beta test reports
General user feedback

Thesecoursewarematerialsaretobeusedinconjunction

12