Guideline: Measuring requirements churn with DOORS
This guideline describes how to collect and manage the measurements for Requirement Churn within the DOORS tool.
Relationships
Related Elements
Main Description
Introduction

This measurement is the number of changes to implemented requirements over time. This information is collected and entered into a Metrics module to help compare measurements over time and report on their status.

Open the Stakeholder Requirement Specification
  • Open the Stakeholder Requirement Specification
  • Open the Metrics module
Collecting the measurements

In The Stakeholder Requirement Specification Set the view to “12 – Requirement Churn” from the pulldown list.

This view uses the link module "traces" and shows all the requirements linked to the design. This is the implemented requirement set.

Note: This view shows deleted and not deleted requirements and the last modified on date sorted by last modified on. This view displays the information needed to collect the data to show the Requirement Churn.

This view holds all implemented requirements even the ones with no changes since the last time collected. It is important to only count the requirements with the last changed date greater then the date of the last measurement. Note: you can modify the view to only show modified requirements during a given time period

Deleted requirements

This measurement is the count of deleted DOORS requirement objects during the given time period.

In the 12 – Requirement Churn view count the number of deleted requirements for this time period. Count the number of DOORS object in red which fall within the time period. The last modified date will give you this information. The view is sorted on the last modified date placing the last deleted requirement first. Count them for this time period.

Modified Requirements

This measurement is the count of modified implemented requirements objects during the given time period.

Note: A changed object is defined but the attributes with their change history date set to on. Any change to any of these attributes will effect the last modified date.

In the 12 – Requirement Churn of implemented requirements view count the number of modified implemented requirements for this time period. Here you count the number of objects with the last modified date greater then the time period. This does not count deletions.

Finding the number of requirements

In the Stakeholder Requirement Specification, set to the view to: “07 - Requirements” from the pulldown list.

This view filters to show all the DOORS objects which are requirements.

Note: When you first apply a filter, there is a filter result box which shows you the number and percent of objects which pass and also the number and percent of object which do not pass the filter criteria. The number which pass is the number of requirements in the module

To find this number; go to the filter definition icon and re apply the filter. Once this is done in the status box the number accepted objects, which is the number of requirements

Recording results

The overall metric is the sum of “no of deleted requirements’, “no of new requirements”, and “no of modified requirements”, divided by the total number of requirements in the measured set. Express this result in percentage terms and record the result in the metrics module, in the object created to record these measurements on this date from these modules.

Manage the collected DOORS measurements throughout the lifecycle

The Metrics module can contains the measurements for different modules. There are attributes for each of the measurements taken. Each module you want to collect data on, the name is entered in a header object. The date and results of each measurement will be entered in a new text object below the module name and last measurement. This data can be collected monthly or when needed to produce the needed results.