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.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

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?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

The Waterfall Model

Com m unic a t ion

proje c t init ia t ion
re quire m e nt ga t he ring

Planning
es timating
sc heduling
tra cking

Mode ling
analysis
design

Const r uc t ion
code
t est

De ploy m e nt
de liv e ry
s upport
f e e dba c k

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

The Incremental Model

increment # n
Co m m u n i c a t i o n
Pla nning
M ode ling
analy s is
des ign

Co n s t ru c t i o n
c ode
t es t

De p l o y m e n t
d e l i v e ry
fe e dba c k

deliv ery of
nt h increment

increment # 2
Co m m u n i c a t i o n
Pla nning
M ode ling
analy s is
des ign

Co n s t ru c t i o n
c ode

De p l o y m e n t

t es t

d e l i v e ry
fe e dba c k

increment # 1

deliv ery of
2nd increment

Co m m u n i c a t i o n
Pla nning
M ode ling
analy s is
des ign

Co n s t ru c t i o n
c ode

De p l o y m e n t

t es t

d e l i v e ry
fe e dba c k

deliv ery of
1st increment

project calendar t ime

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

The RAD Model

Team # n
M o d e lin g
business m odeling
dat a m odeling
process m odeling

C o n s t r u c t io n
com ponent reuse
aut om at ic code
generat ion
t est ing

Team # 2

Com m unicat ion

Mo d eling
b u si n e ss m o d e l i n g
dat a m odeling
p ro ce ss m o d e l i n g

Planning
Co nst r uct io n

Team # 1

co m p o n e n t re u se
a u t o m a t i c co d e
g e n e ra t i o n
t e st i n g

Mode ling

De ploym e nt
int egrat ion
deliv ery
feedback

business modeling
dat a modeling
process modeling

Const r uct ion

component reuse
aut omat ic code
generat ion
t est ing

6 0 - 9 0 days
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

Evolutionary Models: Prototyping

Qu ick
p lan
Quick

Com m unicat ion

plan

communication
Mo
d e lin g
Modeling
Qu ick d e sig n

Quick design

Deployment
Deployment
De live r y
delivery &
& Fe e dback

feedback

Const r uct ion

Construction
of
ofot
prototype
pr
ot ype

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

Evolutionary Models: The Spiral

planning
estimation
sch eduling
risk analysis

communication
modeling
analysis
design
start

deployment
delivery
feedback

construction
code
test

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

Evolutionary Models: Concurrent

none
Modeling act ivit y

represents the state

of a software engineering
activity or task

Under
development

A wait ing
changes

Under review
Under
revision
Baselined

Done

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

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, architecturecentric, iterative and incremental software process
closely aligned with the Unified Modeling Language
(UML)

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

The Unified Process (UP)

Elab
o r at io n
elaboration
Incep t io n
inception

inception

co nst r uct io n
Release
soft ware increment

t r ansit io n

p r o d uct io n
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

10

UP Phases
UP Phase s
Incept ion

Elaborat ion

Const ruct ion

Transit ion

Product ion

Wor kflows
Requirements
Analysis
Design

Implementation
Test
Support
Iterations

#1

#2

#n-1

#n

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

11

UP Work Products
Incept ion phase
Vision document
Init ial use-case model
Init ial project glossary
Init ial business case
Init ial risk assessment .
Project plan,
phases and it erat ions.
Business model,
if necessary .
One or more prot ot y pes
I nc e pt i o
n

Elaborat ion phase

Use-case model
Supplement ary requirement s
including non-funct ional
Analy sis model
Soft ware archit ect ure
Descript ion.
Execut able archit ect ural
prot ot y pe.
Preliminary design model
Rev ised risk list
Project plan including
it erat ion plan
adapt ed workflows
milest ones
t echnical work product s
Preliminary user manual

Const ruct ion phase

Design model
Soft ware component s
Int egrat ed soft ware
increment
Test plan and procedure
Test cases
Support document at ion
user manuals
inst allat ion manuals
descript ion of current
increment

Transit ion phase

Deliv ered soft ware increment
Bet a t est report s
General user feedback

These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005

12