Metrics for Process and Projects

Chapter 15 & 22
Roger S. Pressman(6th Edition)

Md. Mahbubur Rahman

Lecturer, Dept. of CSE, DIU
E-mail- [email protected]
Phone- +8801521 238 777

1
Measurement
 Provides a mechanism for objective
evaluation
 Assists in
 Estimation
 Quality control
 Productivity assessment
 Project Control
 Tactical decision-making
 Acts as management tool

2
Measures, Metrics and
Indicators
 A measure provides a quantitative indication of the
extent, amount, dimension, capacity, or size of some
attribute of a product or process.
 E.g., Number of errors
 The IEEE glossary defines a metric as “a quantitative
measure of the degree to which a system, component,
or process possesses a given attribute.”
 E.g., Number of errors found per person hours expended
 An indicator is a metric or combination of metrics
that provide insight into the software process, a
software project, or the product itself.
3
 Motivation for Metrics
 Estimate the cost & schedule of future projects

 Evaluate the productivity impacts of new tools and

techniques

 Establish productivity trends over time

 Improve software quality

 Forecast future staffing needs

 Anticipate and reduce future maintenance needs

4
Metrics in the Process and Project Domains :

 Process metrics are collected across all projects

and over long periods of time
 Project metrics enable a software project manager
to
 Assess the status of an ongoing project
 Track potential risks
 Uncover problem areas before they go “critical”
 Adjust work flow or tasks
 Evaluate the project team’s ability to control
quality of software work products
5
 Process Metrics and Software
Process Improvement
Product

Customer Business
characteristics conditions

Process

People Development Technology

environment

Fig.-22.1: Determinants for s/w quality and organizational effectiveness

6
Process Metrics and Software
Process Improvement
 Error
 Some flaw in a s/w engineering work product
that is uncovered before the s/w is delivered to
the end-user

 Defect
 A flaw that is uncovered after delivery to the
end-user

7
Project Metrics
 Used during estimation
 Used to monitor and control progress
 The intent is twofold
 Minimize the development schedule
 Assess product quality on an ongoing
basis
 Leads to a reduction in overall project
cost
8
Typical Project Metrics
1. Effort/time per software engineering
task
2. Errors uncovered per review hour
3. Scheduled vs. actual milestone dates
4. Changes (number) and their
characteristics
5. Distribution of effort on software
engineering tasks

9
Software Measurement
 S/W measurement can be categorized in
two ways:
1. Direct measures of the s/w process (e.g., cost
and effort applied) and product (e.g., lines of
code (LOC) produced, etc.)
2. Indirect measures of the product (e.g.,
functionality, quality, complexity, etc.)
 Requires normalization of both size- and
function-oriented metrics
10
1.Size-Oriented Metrics

 Lines of Code (LOC) can be chosen as the

normalization value
 Example of simple size-oriented metrics
 Errors per KLOC (thousand lines of code)
 Defects per KLOC
 $ per KLOC
 Pages of documentation per KLOC

11
Size-Oriented Metrics
Project LOC Effort $(000) Pp. doc. Errors Defects People

alpha 12,100 24 168 365 134 29 3

Beta 27,200 62 440 1224 321 86 5

gamma 20,200 43 314 1050 256 64 6

. . . . . . . .
. . . . . . . .

12
 Size-Oriented Metrics
 Controversy regarding use of LOC as a key measure
 According to the proponents
 LOC is an “artifact” of all s/w development projects
 Many existing s/w estimation models use LOC or
KLOC as a key input

 According to the opponents

 LOC measures are programming language
dependent
 They penalize well-designed but shorter programs
 Cannot easily accommodate non procedural
languages
 Difficult to predict during estimation
13
2. Pros & Cons of FP
 Controversy regarding use of FP as a key measure
 According to the proponents
 It is programming language independent
 Can be predicted before coding is started
 According to the opponents
 Based on subjective rather than objective data
 Has no direct physical meaning – it’s just a number

14
Function-Oriented Metrics

 The most widely used function-oriented

metric is the function point (FP)
 Uses of FP: (from ref. book, pp. 472)
 Computation of the FP is based on
characteristics of the software’s information
domain and complexity

15
Information Domain
 Number of external inputs – from user or another
application
 Number of external outputs
 Number of external inquiries – request from user that
generates an on-line output
 Number of internal logical files (maintained by system)
 Number of external interface files (provides data but not
maintained by system)

16
Computing Function Points
Analyze information
domain of the Establish count for input domain and
application system interfaces
and develop counts

Weight each count by Assign level of complexity or weight

assessing complexity to each count

Assess influence of Grade significance of external factors, F i

global factors that affect
the application
such as reuse, concurrency, OS, ...

function points = (count x weight) x C

Compute
function points where:
complexity multiplier: C = (0.65 + 0.01 x N)
degree of influence: N = F
i
17
Analyzing the Information Domain
weighting factor
measurement parameter count simple avg. complex
number of user inputs 3 X 3 4 6 = 12
number of user outputs 5 X 4 5 7 = 25
number of user inquiries 2 X 3 4 6 = 8
number of files 4 X 7 10 15 = 40
number of ext.interfaces 1 X 5 7 10 = 7
count-total 92
complexity multiplier [0.65 + 0.01 × ∑(Fi)]
function points
count-total × [0.65 + 0.01 ×∑(Fi)]

18
Taking Complexity into
Account
Factors(Fi) are rated on a scale of 0 (not important)
to 5 (essential)

The following are some examples of these factors:

 Is high performance critical?
 Is the internal processing complex?
 Is the system to be used in multiple sites and/or by multiple
organizations?
 Is the code designed to be reusable?
 Is the processing to be distributed?
 and so forth . . .

19
An Example of FP-Based
Estimation (3)

Value Adjustment Factors 52 20

Computing Function Points
weighting factor
measurement parameter count simple avg. complex
40
number of user inputs 10 X 3 4 6 =
100
number of user outputs 20 X 4 5 7 =
number of user inquiries 25 X 3 4 6 = 100

4 40
number of files X 7 10 15 =
28
number of ext.interfaces 4 X 5 7 10 =
count-total 308

complexity multiplier [0.65 + 0.01 × ∑(Fi)] 1.35

function points count-total × complexity multiplier 415.8

21
Uses of Function Points(FP)
But how long will the project take and how
much will it cost?
 If programmers in an organization produce average 12
function points per month. Thus . . .
415.8 FP divided by 12 = 34 months

 If the average programmer is paid $1000 per month

(including benefits), then the [labor] cost of the project
will be . . .
 5 man-months X $500 = $2500
22
 H.W. :
 A system has 10 external inputs, 20 external outputs,
fields 25 different external queries, manages 4 internal
logical files and interfaces with 4 different legacy
systems (4 EIFs). Assume that all of these data are of
average complexity and all value adjustment factors
(VAF) are absolutely essential.
1. Compute the function point (FP) for the system.
2. If 5 programmers in an organization produce average
12 function points per month then how many
programmers will need to complete the project within
one month ?
3. If the average programmer is paid $500 per month 23
then the [labor] cost of the project will be ?
Likert Scale

0 1 2 3 4 5

Less importan Avg. Less Essenti Absolutely

Essential
imp. t Essential al
 H.W. :
A system has 15 external inputs, 30 external outputs,
fields 25 different external queries, manages 4 internal
logical files and interfaces with 5 different legacy
systems (4 EIFs). Assume that all of these data are of
complex complexity and 50% value adjustment factors
(VAF) are essential and others factors are average.

(i)Compute the function point (FP) for the system.

(ii)If 6 programmers in an organization produce average
10 function points per month then how many months
will need to complete the project?
3. If the average programmer is paid $600 per month
then the [labor] cost of the project will be ? 25