Introduction
This measurement is the percent of high level requirements which have associated lower level requirements. 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 and Metrics module
-
Open the Stakeholder Requirement Specification
-
Open the Metrics module
Collecting the measurement
In the Stakeholder Requirement Specification, set to the view to: “09 – Unsatisfied requirements” from the pulldown
list.
This view uses the right link module "Satisfies" and shows all the requirements 'not' linked. For this measurement you
want the percent of requirements are linked.
This view contains all requirements not allocated
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. It is
this percent of objects which do not pass which will give you the value needed.
To find this Percent; go to the filter definition icon and re apply the filter. Once this is done in the status box
the number accepted are the ones without allocations (links). The ones rejected are the ones allocated and it is this
number you take to give you the percent of requirements allocated during a given time period.
Recording results
Take this measurement and place is in “Requirement Traceability Coverage” attribute in the object created to record
this measurement on this date from this modules.
Manage the collected DOORS measurements throughout the lifecycle
The metrics module can contain 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.
|