QualitoMeter™ is a balanced set of metrics that provide indicators helping the managers to 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 signals quality deterioration if any negative development is noticed. This helps to take timely corrective actions when the measurements revealed below these set of metrics fall below a preset objective. This helps in determining Schedule Slips. Quality of product being produced and amount of rework/maintenance once product is in production.
Qualitometer™ comprises the following set of metrics:
Requirement Traceability Metrics – Measures the requirement stability of a particular iteration
Efficient requirements management can help prevent Defects early in testing cycle, thereby reducing project costs. RTM helps us to track down the state of the critical business requirements in various phases. It performs the mapping between the software requirement and test cases. It gives us an indication of which requirement is 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
Test progress metrics measure 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 |
The defects summary enclosed in the chart alongside helps to determine and compare the stability of iteration with respect to the previous iteration.
Defect Metrics – Measure the stability of the entire build with respect to the release readiness.
Defect Metrics provide indicator which help managers to get an insight into the quality of the product, soft effectiveness of testing by measuring the following parameters:
| |
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: it measure the effectiveness in containing defects found during testing prior to the product into production by comparing the number of defects found and closed from iteration to iteration |
|
Defect Resolution Effectiveness It measure the effectiveness in defect discovery and resolution by comparing the number of defect found and closed prior to release into production, with the number remaining 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. It explores the possibility of quantifying and assessing various aspects of software and come out with a successful organization-wide metrics program. It looks at few manageable and important metrics which signals quality deterioration if any negative development is noticed. This helps to take timely corrective actions when the measurements revealed by these set of metrics fall below a preset objective. These timely signals helps in determining schedule slips, quality of product being produced and amount of rework/maintenance once product is in production. |
