QualitoMeter™ is a balanced set of metrics that provide indicators
helping managers get an insight into the quality of the product,
software reliability, and the effectiveness of testing by measuring
various parameters like requirement stability of a particular
iteration, stability of a build with respect to the previous build, and
stability of the entire build with respect to release readiness.
Qualitometer™ enables us to maintain the quality of our QA process.
It’s designed in such a way that it is uses only a few manageable and
important metrics which signal quality deterioration. This helps to take timely corrective actions
when the measurements listed fall below a preset threshold. This
helps determine schedule slips, quality of product being developed
and amount of rework/maintenance once product is in production.
Qualitometer™ comprises of the following set of metrics:
Requirement Traceability Metrics(RTM) – Measure the requirement stability of a particular iteration
Efficient requirements management can help prevent defects early in the
test cycle, thereby reducing project costs. RTM helps us track
down the state of critical business requirements in various phases.
It performs the mapping between software requirements and test
cases. It gives us an indication of specific requirements that are
lagging behind in terms of writing use cases and getting them
reviewed/base lined.
Test Progress Metrics – measure the stability of a build with respect to the previous build by measuring the following parameters:
 |
Number of test cases executed against the documented requirements |
|
Number of test cases successfully completed |
|
Number of invalidated test cases |
|
Number and type of defects logged against each requirement |
Defect Metrics – Measure the stability of the entire build with respect to the release readiness by measuring the following:
| |
The number of defects detected and fixed i.e find to fix ratio |
|
The type and severity of the defects |
|
Relationship between the status of bugs/new feature with respect to the requirement for a particular duration. |
|
Defect
Containment Effectiveness: measure the effectiveness in containing
defects found during testing prior to production, by comparing the number
of defects found and closed from iteration to iteration |
|
Defect Resolution Effectiveness: measure the effectiveness in defect
discovery and resolution by comparing the number of defects found and
closed prior to release, with the number that remain open
after release. |
Our unique methodology deals with identifying a customized and balanced
set of metrics that will help your organization track the progress of
the project towards the ultimate goal i.e setting up clear release
criteria and objectively signing off on the quality of the product. It
explores the possibility of quantifying and assessing various aspects
of the software resulting in a successful organization-wide metrics
program.
For more details on sample metrics we track, please visit our Test Process section under Innovation |
