In contrast, Pfleeger and Atlee[5] focus on the risks associated with changes and state that IA is: "the evaluation of the many risks associated with the change, including estimates of the effects on resources, effort, and schedule".
Both the design details and risks associated with modifications are critical to performing IA within the change management processes.
In traceability IA, links between requirements, specifications, design elements, and tests are captured, and these relationships can be analysed to determine the scope of an initiating change.
Within software design, static and dynamic algorithms can be run on code to perform dependency IA.
Review meeting protocols,[11] informal team discussions, and individual engineering judgement[12] can all be used to determine the consequences of a modification.[how?]
Following these dependencies in reverse order is a convenient way to identify the impact of changing the contents of a software package.