Chapter 05

Supplementary Slides for
Software Engineering:
A Practitioner's Approach, 5/e
copyright © 1996, 2001

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.
This presentation, slides, or hardcopy may NOT be used for

short courses, industry seminars, or consulting purposes.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
1
Chapter 5
Software Project Planning
2
Software Project Planning
The overall goal of project planning is
to establish a pragmatic strategy for
controlling, tracking, and monitoring
a complex technical project.
Why?
So the end result gets done on time,

with quality!
3
The Steps
 Scoping—understand the problem and the
work that must be done
 Estimation—how much effort? how much
time?
 Risk—what can go wrong? how can we avoid
it? what can we do about it?
 Schedule—how do we allocate resources
along the timeline? what are the milestones?
 Control strategy—how do we control
quality? how do we control change?
4
Write it Down!
Project Scope Software

Estimates Project
Risks Plan
Schedule
Control strategy
5
To Understand Scope ...
 Understand the customers needs
 understand the business context
 understand the project boundaries
 understand the customer’s motivation
 understand the likely paths for change
 understand that ...
Even when you understand,

nothing is guaranteed!
6
Cost Estimation
project scope must be explicitly

defined
task and/or functional
decomposition is necessary
historical measures (metrics) are
very helpful
at least two different techniques
should be used
remember that uncertainty is
inherent
7
Estimation Techniques
 past (similar) project experience
 conventional estimation techniques
 task breakdown and effort estimates
 size (e.g., FP) estimates
 tools (e.g., Checkpoint)
8
Functional Decomposition
Statement functional
perform
of Scope a decomposition
"grammatical
parse"
9
Creating a Task Matrix
Obtained from “process framework”
framework activities
application Effort required to

functions accomplish
each framework
activity for each
application function
10
Conventional Methods:
LOC/FP Approach
 compute LOC/FP using estimates of

information domain values
 use historical effort for the project
11
Example: LOC Approach
Functions estimated LOC LOC/pm $/LOC Cost Effort (months)
UICF 2340 315 14 32,000 7.4
2DGA 5380 220 20 107,000 24.4
3DGA 6800 220 20 136,000 30.9
DSM 3350 240 18 60,000 13.9
CGDF 4950 200 22 109,000 24.7
PCF 2140 140 28 60,000 15.2
DAM 8400 300 18 151,000 28.0
Totals 33,360 655,000 145.0
12
Example: FP Approach
measurement parameter count weight
number of user inputs 40 x 4 = 160
number of user outputs 25 x 5 = 125
number of user inquiries 12 x 4 = 48
number of files 4 x 7 = 28
0.25 p-m / FP = 120 p-m
number of ext.interfaces 4 x 7 = 28
algorithms 60 x 3 = 180
count-total 569
complexity multiplier .84
feature points 478
13
Tool-Based Estimation
project characteristics
calibration factors
LOC/FP data
14
Empirical Estimation Models
General form:
exponent
effort = tuning coefficient * size
usually derived
as person-months empirically
of effort required derived
usually LOC but
may also be
either a constant or function point
a number derived based
on complexity of project
15
Estimation Guidelines
estimate using at least two techniques

get estimates from independent sources
avoid over-optimism, assume difficulties
you've arrived at an estimate, sleep on it
adjust for the people who'll be doing the
job—they have the highest impact
16
The Make-Buy Decision
simple (0.30)
$380,000
$450,000
difficult (0.70)
build
$275,000
minor changes
(0.40)
reuse
system X $310,000
simple (0.20)
major
changes
buy (0.60) $490,000
complex (0.80)
minor changes $210,000

contract (0.70)
$400,000
major changes (0.30)
without changes (0.60) $350,000
$500,000
with changes (0.40)
17
Computing Expected Cost
expected cost =
(path probability) x (estimated path cost)
i i
For example, the expected cost to build is:
expected cost build = 0.30($380K)+0.70($450K)
= $429 K
similarly,
expected cost reuse = $382K
expected cost buy = $267K
expected cost contr = $410K
18

Chapter 05

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

Chapter 05

Uploaded by

Copyright:

Available Formats

Supplementary Slides for

copyright © 1996, 2001

For University Use Only

This presentation, slides, or hardcopy may NOT be used for

So the end result gets done on time,

Project Scope Software

Even when you understand,

project scope must be explicitly

application Effort required to

 compute LOC/FP using estimates of

Functions estimated LOC LOC/pm $/LOC Cost Effort (months)

UICF 2340 315 14 32,000 7.4

2DGA 5380 220 20 107,000 24.4

3DGA 6800 220 20 136,000 30.9

DSM 3350 240 18 60,000 13.9

CGDF 4950 200 22 109,000 24.7

PCF 2140 140 28 60,000 15.2

DAM 8400 300 18 151,000 28.0

Totals 33,360 655,000 145.0

number of user inputs 40 x 4 = 160

number of user outputs 25 x 5 = 125

number of user inquiries 12 x 4 = 48

complexity multiplier .84

feature points 478

estimate using at least two techniques

minor changes $210,000

without changes (0.60) $350,000

You might also like