Scenario T4 - Requirements are traded

Motivation

This scenario addresses the need to review requirements for their relative priorities, costs and benefits in order to support trading.

Pre-conditions

Requirements exist at various levels and are traced. A high-level requirement is being considered for trading.

Scenario

1. An impact graph is assembled by following satisfaction relations from the root requirement to all other linked requirements.
   1. This graph becomes an independent resource, individually addressable, and separate from the underlying requirements structure

Post-conditions

An impact graph exists that can be used to assess the 'cost' of a given high-level requirement.

Multiple impact graphs can be created for different high-level requirements to support competitive trading exercises.

Notes

This scenario could be extended to allow the impact graphs of two high-level requirements to be compared, thus allowing assessment of the extent to which these requirements are 'entangled'. This could be useful in trade assessments, but is probably a client issue rather than an API issue.

-- SimonWills - 05 Feb 2010