0% found this document useful (0 votes)
25 views11 pages

SW Measurement

Uploaded by

Wajot
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views11 pages

SW Measurement

Uploaded by

Wajot
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

1I

MEASUREMENT – SOME QUOTATIONS

 Count what is countable. Measure what is measurable. And what is not


measurable, make measurable (Galileo Gallilei)
 A science is as mature as its measurement tools (Louis Pasteur)
 In God we trust. All others bring data (W. Edwards Deming)
 Measurement is an excellent abstraction mechanism for learning what
works and what doesn’t (Victor Basili)
 Not everything that can be counted counts, and not everything that
counts can be counted (Albert Einstein)

2
POSITIONING OF SOFTWARE MEASUREMENT
Modeling

Real world of Formal models


Selection and Simulation,
Software - Processes
implementation Measurement,
Engineering - Products
of decisions Analysis
- Resources

Decision Support

 (Software) Measurement is the process by which values are assigned to


attributes of entities in the real (software) world.
 A measure (or metric) of an attribute associates a value (either numbers
or symbols) to each entity, in such a way that our knowledge/intuition
about the attribute is not contradicted.
3|
Can anybody name any
software metric?

4
5
CODE CHURN

 Code churn represents the


number of lines of code
that were modified,
added or deleted in a
specified period of time. If
code churn increases,
then it could be a sign that
the software development
project needs attention.

Source: https://stackify.com/track-software-metrics/
6
DEFECTS IN DEPENDENCE OF SYSTEM FUNCTIONALITY

50 Number of Faults 3.5


3.4
45 Fault Density (Faults/KSLOC)
Average Fault Density (Faults/KSLOC) 3.0
40
2.6
35 2.5
2.1
30
2.0
1.8
25
1.8
1.5
20

15 1.0
0.7
10
0.5
5

0 0.0

Dispensing Management Console Tool Driver Data

7|
HOW? - THE GOAL-QUESTIONS-METRICS METHODOLOGY

Goal (object, purpose, quality aspect, viewpoint, environment)

variation
factors Quality models
implicit
Q1 Q2 Q3 Q4

INTERPRETATION
models
DEFINITION

The picture can't be displayed.

M1 M2 M3 M4 M5 M6 M7 M8 …

8
EXAMPLES OF MEASUREMENTS OF QUALITY OF THE WORK PRODUCT (1/2)

 Number of issues raised at requirements inspection


 Number of requirements issues open
 Number of requirements issues closed
 Number of issues raised during code inspection
 Number of defects opened during unit testing

Adapted from: www.iteam.com

9
EXAMPLES OF MEASUREMENTS OF QUALITY OF THE WORK PRODUCT (2/2)

 Number of defects opened during system testing


 Number of defects opened during UAT
 Number of defects still open
 Number of defects closed
 Defect age

Adapted from: www.iteam.com

10
EXAMPLE DIRECTIONS FOR ANALYSIS

 Technology evaluation (effort, time, performance, usability)


 Find strength and limitations of technologies
 Find preferred areas of applications of technologies
 How long does it take to learn/train?
 Comparison between technologies
 Usefulness
 Usage (Who? How much?)

11

You might also like