diff --git a/process/process_areas/change_management/_assets/impact_analysis.drawio.svg b/process/process_areas/change_management/_assets/impact_analysis.drawio.svg new file mode 100644 index 0000000000..4abf0d31d5 --- /dev/null +++ b/process/process_areas/change_management/_assets/impact_analysis.drawio.svg @@ -0,0 +1,4 @@ + + + +
Feature
Requirements
Feature...
fulfills
fulfills
Feature
Architecture
Feature...
satifies
satifies
Component
Requirements
Component...
Source Code
Source Code
Stakeholder
 Requirements
Stakeholder...
satifies
satifies
fulfills
fulfills
Component
Architecture
Component...
satifies
satifies
1, *
1, *
Detailed
Design
Detailed...
satifies
satifies
implements
implements
implements
implements
Feature
Safety Analysis
Feature...
Feature
Assumptions of use
Feature...
Platform
Tests
Platform...
Feature
Integration Tests
Feature...
verifies
verifies
violates
violates
mitigated_by
mitigated_by
verifies
verifies
Component
Integration Tests
Component...
verifies
verifies
Component
Safety Analysis
Component...
Component
Assumption of use
Component...
violates
violates
mitigated_by
mitigated_by
mitigated_by
mitigated_by
mitigated_by
mitigated_by
verifies
verifies
Unit Test
Unit Test
verifies
verifies
verifies
verifies
not needed, not safety relevant
not needed, not safe...
not needed, should fail (all verifies links)
not needed, should f...
both ways
both ways
follow the arrow
follow the arrow
follow back the arrow
follow back the arrow

Which changes to follow for impact analysis

Which changes to follow for impact analysis
Text is not SVG - cannot display
diff --git a/process/process_areas/change_management/_assets/impact_iteration.drawio.svg b/process/process_areas/change_management/_assets/impact_iteration.drawio.svg new file mode 100644 index 0000000000..724f87bb08 --- /dev/null +++ b/process/process_areas/change_management/_assets/impact_iteration.drawio.svg @@ -0,0 +1,4 @@ + + + +
Detailed
Design
Detailed...
implements
implements

How to follow changes for impact analysis iteratively

How to follow changes for impact analysis iterative...
Component
Requirements
Component...
Component
Architecture
Component...
Detailed
Design
Detailed...
satifies
satifies
implements
implements
implements
implements
Feature
Requirements
Feature...
Feature
Architecture
Feature...
satifies
satifies
fulfills
fulfills
satifies
satifies
Component
Safety Analysis
Component...
mitigated_by
mitigated_by
Source Code
Source Code
Source Code
Source Code
Component
Requirements
Component...
Component
Architecture
Component...
Detailed
Design
Detailed...
satifies
satifies
implements
implements
implements
implements
Source Code
Source Code
Text is not SVG - cannot display
diff --git a/process/process_areas/change_management/guidance/change_management_reqs.rst b/process/process_areas/change_management/guidance/change_management_reqs.rst index 921f9c6a36..1dcc3ec2fb 100644 --- a/process/process_areas/change_management/guidance/change_management_reqs.rst +++ b/process/process_areas/change_management/guidance/change_management_reqs.rst @@ -172,5 +172,32 @@ Change Request Traceability Impact Analysis Tool It shall be reported, which work products and elements are affected by adding a new feature or component or by a modification of an existing feature or component. + Below picture illustrates the relations: + + .. figure:: ../_assets/impact_analysis.drawio.svg + :width: 100% + :align: center + :alt: Which changes to follow for impact analysis. + + The picture is derived from the building blocks metamodel containing all the work products + (:ref:`general_concepts_building_blocks`). Its arrows show how every work product is + linked (manually) to other work products (e.g. feature requirements are linked to + stakeholder requirements via "satisfies"). The color code describes which of these Links + need to be followed for the impact analysis (so for the example this means: if a stakeholder + requirement is changed, the feature requirements linked are affected, but not the other way round). + "Black" links do not need to be followed, these are the "verifies" links. And these are + expected to fail after implementation change, so the impact on testing will be detected + by the test automation without the need for an additional tooling. Note that for some + links it is expected to have both directions followed (red arrows) - these are the + artefacts which reside in different repositories. + + Note also: The impact analysis needs to follow the links iteratively, so first to the directly + connected work products, then to the next, ... (see the next illustration): + + .. figure:: ../_assets/impact_iteration.drawio.svg + :width: 100% + :align: center + :alt: How to follow changes for impact analysis iteratively. + .. needextend:: docname is not None and "process_areas/change_management" in docname :+tags: change_management