Step 3 - Metrics 1
Creating a Metrics Program
Step 3: Define Metrics Required to Reach
Step 3 is to choose which software metrics will help achieve the goals of the metric
The goals for a metrics program determine the specific metrics on
which the program will be based. This section analyzes each of the
eight goals outlined in Step 2. The goals will be converted into a set
of metrics by applying the Basili GQM (Goals/Questions/Metrics)
model (Basili, 1984). The following diagram illustrates the Basili
Figure 3.2 :
Step 3 - Metrics 2
The GQM model helps you identify a set of metrics which support
your goals. This is done in 2 steps:
1. Determine a set of questions which, when answered, provide the
insight necessary to achieve the goals.
2. Determine a set of metrics which can be collected and analyzed
to help answer each question.
You should follow this procedure for each goal you selected in Step
2. The result will be a set of metrics which support your goals.
If you selected goals directly from the list in step 2, questions and
metrics will be provided for you in the following sections.
Keep in mind that the metrics defined at this stage are quite simple.
They are going to be used to help get the program going and to
establish a baseline. Later, when the mechanics of the metrics
program have been worked out, more complicated or specialized
metrics can be added. It can be tempting to go overboard and measure
everything right away, but this leads to information overload. Attempt
to focus on metrics which will help you achieve your initial goals.
Questions and Metrics for the Program Goals
In this section, questions are presented for the goals from step 2,
followed by tables that list metrics which support each question.
Some software attributes can be measured in various ways (e.g., size
can be measured in lines of code, function points, tokens etc.), and
there are no industry wide standards governing which metric to use.
The metrics used in SPC's Metricate database