Prescriptive Process Models

Software Engineering: A Practitioner’s 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 Practitioner’s Approach, 6/e and are provided with
permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005 1
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?
The Waterfall Model
Co m m u n ic a t io n
p ro je c t in it ia t io n Planning
re q u ire m e n t g a t h e rin g estimating Mo d e lin g
scheduling
a na lys is Co n s t ru c t io n
tracking
de s ign De p lo y m e n t
c ode
t es t d e liv e ry
s u p p o rt
f e e dba c k
The Incremental Model
incre m e nt # n
Co m m u n ic a t i o n
P la n n in g
Mo d e lin g
a n a ly s is Co n s t ru c t i o n
d e s ig n
c ode De p l o y m e n t
t est d e l i v e ry
fe e d b a c k
d e liv e ry o f
in cre m e n t # 2 n t h in cre me n t
Co m m u n i c a t i o n
Pla n n in g
Mo d e li n g
d e s ig n code De p l o y m e n t
t es t d e l i v e ry
fe e d b a c k
d e liv e ry o f
in cre m e n t # 1 2 n d in cre me n t
Co m m u n i c a t i o n
Pla n n in g
Mo d e lin g
d e s ig n c ode
d e liv e ry o f
De p l o y m e n t
t est d e l i v e ry
fe e d b a c k
1 st in cre m e n t
project calen dar t ime
The RAD Model
Te am # n
Mo d e lin g
bus ine s s m o d e lin g
da t a m o de lin g
proc e s s m o d e lin g
C o n s t ru c t io n
c om p one nt re us e
Te am # 2 a ut om a t ic c od e
Co m m u n ic a t io n ge ne ra t ion
t e s t in g
Mo d e ling
b u s in e s s m o d e lin g
d a t a m o d e lin g
p ro ce ss m o d e lin g
Plan n in g
Co ns t ruc t io n De p lo y m e n t
Te am # 1 co m p o n e n t re u s e
in t e g rat io n
a u t o m a t ic co d e
g e n e ra t io n d e liv e ry
Mo d e lin g t e s t in g fe e d b ack
b u s in e s s mo d e lin g
d at a mo d e lin g
p ro ce s s mo d e lin g
Co n s t ru c t io n
co mp o n e n t re u s e
au t o mat ic co d e
g e n e rat io n
t e s t in g
6 0 - 9 0 d ay s
Evolutionary Models: Prototyping
Qu iQuick
c k p la n
Co m m u n ic a t io n plan
communication
Modeling
Mo d e lin g
Qu ic k d e s ig n
Quick design
De plo ym e n t
Deployment
De liv e ry
delivery & Co n s t ru c t io n
& Fe e d b a c k Construction
feedback of
pofroprototype
t o t yp e
Evolutionary Models: The Spiral
planning
estimation
scheduling
risk analysis
communication
modeling
analysis
design
start
deployment
construction
delivery code
feedback test
Evolutionary Models: Concurrent
none
Mode ling ac t ivit y
rep res ents the s tate

Unde r o f a s o ftware eng ineering
activity o r tas k
de ve lopm e nt
Awa it ing
c ha nges
Unde r re vie w
Unde r
re vis ion
Ba s e line d
Done
Still Other Process Models
 Component based development—the process to apply
when reuse is a development objective
 Formal methods—emphasizes the mathematical
specification of requirements
 AOSD—provides a process and methodological
approach for defining, specifying, designing, and
constructing aspects
 Unified Process—a “use-case driven, architecture-centric,
iterative and incremental” software process closely
aligned with the Unified Modeling Language (UML)
The Unified Process (UP)
Ela b o ra t io n
elaboration
Inc e p t io n
inception
inception
c o ns t ruc t io n
Re le a s e
t ra ns it io n
s oft wa re inc re m e nt
p ro d uc t io n
UP Phases
UP Phases
In ce p t io n Elabo rat io n Co ns t ru ct io n Tran s it io n Pro d u ct io n
Workflows
Requirements
Analysis
Design
Implementation
Test
Support
Iterations #1 #2 #n-1 #n
In ce p t io n p h as e
UP Work Products
Elab orat ion ph as e
Vis io n d o cu me n t
In it ial u s e -cas e mo d e l
In it ial p ro je ct g lo s s ary
Co ns t ruct ion ph as e
Us e -cas e mo d e l
In it ial b u s in e s s cas e Su p p le me n t ary re q u ire me n t s
In it ial ris k as s e s s me n t . in clu d in g n o n -fu n ct io n al De s ig n mo d e l
Tran s it io n p h as e
Pro je ct p lan , An aly s is mo d e l So ft ware co mp o n e n t s
p h as e s an d it e rat io n s . So ft ware arch it e ct u re In t e g rat e d s o ft ware De liv e re d s o ft ware in cre me n t
Bu s in e s s mo d e l, De s crip t io n . in cre me n t Be t a t e s t re p o rt s
if n e ce s s ary . Exe cu t ab le arch it e ct u ral Te s t p lan an d p ro ce d u re Ge n e ral u s e r fe e d b ack
On e o r mo re p ro t o t y p e s p ro t o t y p e .
In c e p t i o
Te s t cas e s
n Pre limin ary d e s ig n mo d e l Su p p o rt d o cu me n t at io n
Re v is e d ris k lis t u s e r man u als
Pro je ct p lan in clu d in g in s t allat io n man u als
it e rat io n p lan d e s crip t io n o f cu rre n t
ad ap t e d wo rkflo ws in cre me n t
mile s t o n e s
t e ch n ical wo rk p ro d u ct s
Pre limin ary u s e r man u al

Prescriptive Process Models

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Prescriptive Process Models

Uploaded by

Copyright:

Available Formats

Software Engineering: A Practitioner’s Approach, 6/e

For University Use Only

project calen dar t ime

Mode ling ac t ivit y

rep res ents the s tate

You might also like