📈
Unit 2: Measurement,
Estimation and Data Analysis
Type Lecture
Reviewed
Role of measurement, estimation and
data analysis
To support reliable quantitative comparisons, evaluations, predictions and
decision-making relevant to software projects and their artefacts
Project resource estimation C, T
Project health tracking Q, C T, P
Productivity measures and models P
Quality measures and models Q
Structural and complexity measures Q
Evaluations of models, methods, and tools Q, C, T, P
C = Cost, T = Time, Q = Quality, P = Productivity
Operational level (short term)
Collecting 'raw' data
Measuring, estimating and predicting
Analysing data
Developing and applying quantitative models
Interpreting (e.g. outcomes of data analysis)
Experimenting, evaluating
Unit 2: Measurement, Estimation and Data Analysis 1
, Tactical level (medium term)
Obtaining meaningful information that facilitates effective management of
software projects
Better Planning
Improved understanding
More effective control
Strategic level (longer term)
Contribute to organisation-wide improvement of software processes, and
hence to organisation's strategic aims
Diagnose what’s not so good
Determine changes needed to improve
Monitor effects of applying changes
Use as a management tool to answer questions
How is the progress coming along?
This thing has an atypical feature . . . why is that?
Do X and Y exhibit some relationship?
How do A and B compare?
Why has ___ happened?
If we make ___ change will ___ be the better outcome?
Key Measurement Concepts and
Measurement Theory
Definition and Key concepts
Measurement
Process of assigning value to some attribute of an entity, where value
is obtained on a particular scale
e.g. elapsed time of testing phase of software package
Unit 2: Measurement, Estimation and Data Analysis 2
Unit 2: Measurement,
Estimation and Data Analysis
Type Lecture
Reviewed
Role of measurement, estimation and
data analysis
To support reliable quantitative comparisons, evaluations, predictions and
decision-making relevant to software projects and their artefacts
Project resource estimation C, T
Project health tracking Q, C T, P
Productivity measures and models P
Quality measures and models Q
Structural and complexity measures Q
Evaluations of models, methods, and tools Q, C, T, P
C = Cost, T = Time, Q = Quality, P = Productivity
Operational level (short term)
Collecting 'raw' data
Measuring, estimating and predicting
Analysing data
Developing and applying quantitative models
Interpreting (e.g. outcomes of data analysis)
Experimenting, evaluating
Unit 2: Measurement, Estimation and Data Analysis 1
, Tactical level (medium term)
Obtaining meaningful information that facilitates effective management of
software projects
Better Planning
Improved understanding
More effective control
Strategic level (longer term)
Contribute to organisation-wide improvement of software processes, and
hence to organisation's strategic aims
Diagnose what’s not so good
Determine changes needed to improve
Monitor effects of applying changes
Use as a management tool to answer questions
How is the progress coming along?
This thing has an atypical feature . . . why is that?
Do X and Y exhibit some relationship?
How do A and B compare?
Why has ___ happened?
If we make ___ change will ___ be the better outcome?
Key Measurement Concepts and
Measurement Theory
Definition and Key concepts
Measurement
Process of assigning value to some attribute of an entity, where value
is obtained on a particular scale
e.g. elapsed time of testing phase of software package
Unit 2: Measurement, Estimation and Data Analysis 2
