September 22, 2014

How to Perform Impact Analysis with TestTrack

Helix ALM
Requirements Management
TestTrack’s impact analysis tools take the guesswork out of understanding and approving requirement changes. You can quickly understand the scope of changes in the context of the entire project and make better choices about which changes to approve. To perform impact analysis on a specific requirement, open the requirement and click the Traceability tab. Click Impact Analysis and then select the option for Forward Impact, Backward Impact, or both. [caption id="attachment_14464" align="aligncenter" width="400"]Impact analysis is available on the requirement Traceability tab. Impact analysis is available on the requirement Traceability tab. (Click to enlarge.)[/caption] Requirements that are related in a requirement document or linked to each other are displayed, as well as linked test cases, test runs and defects. Detailed information is displayed for each dependent item to help you determine the item’s status and view more about its relationship with the requirement. [caption id="attachment_14470" align="aligncenter" width="600"]Impact analysis displays detailed information about requirement relationships. (Click to enlarge.) Impact analysis displays detailed information about requirement relationships. (Click to enlarge.)[/caption] Forward and backward impact analysis both display directly and indirectly impacted items. The following table includes the items that are displayed for each type of impact analysis.
Impact analysisImpact typeDisplays:
Forward impactDirectChild requirements one level down in the requirement document hierarchyItems with child or peer links to the requirement
IndirectItems with child or peer links to the directly impacted items
Backward impactDirectParent requirements one level up in the requirement document hierarchyItems with parent or peer links to the requirement
IndirectItems with peer or parent links to the directly impacted items
The following example shows the table of contents for a requirement document. Notice the relationships that FR-25 has. It is the parent requirement of requirements FR-20, FR-26, and FR-21. [caption id="attachment_14461" align="aligncenter" width="470"]Requirement relationships Requirement relationships are based on the requirement document hierarchy. (Click to enlarge.)[/caption] In this forward impact analysis example, the child requirements of FR-25 are displayed in the Impact Analysis area. Test cases and test runs linked to the requirement FR-25 are also displayed. If the requirement changes, these dependent items should be investigated to determine if additional changes are needed. [caption id="attachment_14472" align="aligncenter" width="600"]Forward impact analysis displays downstream dependencies. Forward impact analysis displays downstream dependencies. (Click to enlarge.)[/caption] In the following backward impact analysis example, parent requirements of requirement FR-25 are displayed. Requirement FR-25 may be affected if these requirements change. [caption id="attachment_14476" align="aligncenter" width="600"]Backward impact analysis displays upstream dependencies. Backward impact analysis displays upstream dependencies. (Click to enlarge.)[/caption]

Make Informed Decisions with Impact Analysis

TestTrack’s impact analysis tools provide a clear picture of relationships between items so you can accurately determine the impact of changing requirements. A better understanding of these relationships will help you ensure that changes are not missed and do not negatively affect the project outcome. To learn more about TestTrack's impact analysis tools, download our "Analyzing the Impact of Requirement Changes" guide.