This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

Scenario T7 - A traceability report is generated

Motivation

This scenario addresses multiple needs for traceability reporting.

Pre-conditions

Requirements exist at various levels and are traced. A report is required on the traceability between one collection of artefacts (e.g. a set of user requirements) and another (e.g. a set of system requirements).

Scenario

  1. The collection of 'source' artefacts is assembled.
  2. The collection of 'destination' artefacts is assembled.
  3. A traceability graph is created that contains all of the source artefacts, all of the destination artefacts, and all of the intermediate traceability (linked via a named relationship).
    1. This traceability graph may include further, intermediate artefacts if the traceability between source and destination artefacts is not direct

Post-conditions

A traceability graph exists that contains all source and destination artefacts, all intermediate artefacts, and all relevant relationships between them.

Notes

This scenario is general, and could be applied to reporting on any linked artefact sets (e.g. system requirements to test cases).

-- SimonWills - 05 Feb 2010

Topic revision: r4 - 22 Feb 2010 - 17:19:23 - IanGreen
Main.RmTraceabilityReport moved from Main.TraceabilityReport on 22 Feb 2010 - 17:19 by IanGreen - put it back
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback