Scenario T2 - A requirement is reviewed

Motivation

This scenario addresses the review of a requirement during the development process. Requirements may be reviewed at any stage. Typical issues that may be addressed include completeness, correctness, justification (i.e. whether the requirement has one or more valid 'parents'), satisfaction (i.e. whether the requirement has one or more valid 'children'), progress towards completion, etc.

Pre-conditions

A requirement exists at some stage of development. This requirement is referred to as the 'root requirement'.

Scenario

1. A package of information related to the root requirement is assembled by following the traceability graph rooted in that requirement (via specific relationships, directions, depths, artefact types):
   1. The collection of parent requirements
   2. The collection of child requirements
   3. The collection of impacting issues
   4. The collection of supporting evidence
   5. Any associated argument
2. The collection of parent requirements is reviewed to ensure that root requirement is justified.
3. The collection of child requirements is reviewed for necessity and sufficiency.
4. Impacting issues are reviewed for progress and closure.
5. Supporting evidence is reviewed for relevance and currency.
6. The root requirement is reviewed for correctness, completeness and other attributes of 'goodness'.
7. Any actions arising from the review are recorded as issues, updating existing issues or creating and linking new issues as required.

Post-conditions

The status of the requirement is understood, and any decisions arising from the review have been suitably recorded. Decisions that require changes to content and traceability will be implemented by the requirement elaboration scenario.

Notes

-- SimonWills - 05 Feb 2010