Introduction

This measurement is the Number of modification, addition, de-scope and extraneous 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 “11 – Requirements Stability” from the pulldown list.

Note this view shows deleted and not deleted requirements with their created and last modified date sorted by last modified on. This view displays the information need to collect the needed data to show the high level requirement stability.

This view holds all requirements even the one with no changes since the 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 11 – Requirements Stability 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.

New requirements

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

In the 11 – Requirements Stability view count the number of new requirements for this time period. Count this number of DOORS objects where the date created is greater then the date of the last measurement. In the view the date created and the last date modified should both be greater then the last date the measurement was made. Being sorted by the last date modified makes them easy to find and count.

Modified Requirements

This measurement is the count of modified 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 11 – Requirements Stability view count the number of modified requirements for this time period.

Note: During this time period modifications can be made to new objects. Can count of not count them as a change, just be consistent.

Here you count the number of objects with the last modified date greater then the time period. This does not count deletions or objects with a date created greater then when the last measurement was created.

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 reapply 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 this module.

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.