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.
TWiki> Main Web>RmHome>RmScenarios>RmTraceabilityScenarios>RmChangePropagation (22 Feb 2010, IanGreen)

Scenario T9 - The impact of a change is assessed

Motivation

This scenario addresses the investigation of changes elsewhere that may require changes to a particular requirement.

Pre-conditions

A given requirement exists that is traced to other artefacts. This requirement is referred to as the 'root requirement'. Some of the other artefacts have changed since the last time an assessment was made.

Scenario

  1. An impact graph is assembled by following satisfaction relations from the root requirement to all other linked artefacts.
  2. All requirements in the impact graph that have changed since the last investigation are highlighted.
  3. If any changes are needed, the root requirement is modified.
  4. The assessment is marked as complete.

Post-conditions

Change has been propagated.

Notes

This is a generalisation of the DOORS "suspect links" feature.

-- JeremyDick - 12 Feb 2010

Edit | Attach | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 22 Feb 2010 - 17:19:50 - IanGreen
Main.RmChangePropagation moved from Main.ChangePropagation 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