EWM:The benefits of impact analysis
The benefits of impact analysis
The TD/OMS kernel software offers the functionality to move components through the software change management cycle.
The first question that pops up when looking at a (clearly defined) request for change is: What is the impact of the requested change on our application ?
To answer this question you can start looking at the programs or you can use TD/OMS to define and execute the impact analysis rules. Your TD/OMS installation must have a valid TD/OMS Impact Analysis license key to enable definition and execution of the impact analysis rules.
The definition of the Impact analysis rules is not part of the GUI and (in most cases) the responsibility of the TD/OMS (application) manager.
The defined rules can be used to:
- Obtain the correct components by selecting a specific definition in the Impact analysis view.
- Select all components to attach to a task
- Select the task the components must be connected to (if not done yet).
- Connect the components to the task by selecting the appropriate connect action.
Or you can decide to save an image of the Impact analysis view after step 1. In general an image will make it easier to explain the complexity (and therefore the amount of expected development time) for a requested change.
See for more information about using Impact Analysis function in Impact Analysis view