Percentage of Tested to Implemented Requirements
This metric tracks the percentage of implemented requirements that have been tested.
Relationships
Related Elements
Main Description

Purpose

This metric helps the team confirm they are delivering working software by tracking which implemented requirements have actually been tested.

Definition

Count:

  • Number of implemented requirements
  • Number of tested requirements

Percentage of Tested Requirements to Implemented Requirements = (Tested Requirements / Implemented Requirements) * 100

Optionally group by Requirement Type (e.g.  Use Case, Supplementary).


Analysis

Monitor this metric using a trend line. Plot the percentage on the Y axis and iterations on the X axis. It is also helpful to track what percentage of tests passed.

Expected trend - Ideally, the percentage should always be close to 100% for teams adopting iterative development. Otherwise, it is acceptable for the percentage to be low early on, and approach 100% at the end of the lifecycle.

Low percentage or declining curve - These trends indicate that project functionality is not being properly tested. Determine the cause for the discrepancy. Are staff levels an issue? Has additional functionality been added without an adjustment to the test plan?

Upward slope - An increasing percentage over time indicates that testing is "catching up" with implementation. Confirm that there is sufficient time for testing all functionality prior to the scheduled release.

In the example report below, the team has implemented a significantly higher number of requirements than they have tested. In Iteration 4, only 10% of the implemented requirements were tested. Of those tested, 70% passed.

Percentage of Test Requirements to Implemented Requirements (lower line = percent tested, upper line = percent passed)

Percentage of Implemented to Tested Requirements

Percentage of Test Requirements to Implemented Requirements (lower line = percent tested, upper line = percent passed)


The example below, which shows the percentage of Tested Use Cases to Implemented Use Cases, focuses on Use Cases only. Horizontal axis represents the iteration numbers. Notice the sharp drop in tested use cases in Iteration 3.

Percentage of Tested Use Cases to Implemented Use Cases

Frequency and reporting

The team reviews Percentage of Implemented to Tested Requirements at the end of each iteration during their iteration assessment.


Collection and reporting tools

Data is collected in IBM® Rational® Team Concert®  and IBM® Rational® Quality Manager®.   IBM® Rational® Insight® reports on this metric.