IV.24.1 Identify maintenance-specific risks and side effects.
IV.24.2 Project likelihood that risks and side effects will occur.
IV.24.3 Project impact of risks and side effects on developers / customers and on overall maintenance strategy.
IV.24.4 Write a Risk/Side Effect Mitigation, Monitoring and Management Plan. Review as required.
These tasks are conducted using the approach defined in the risk analysis umbrella activity. For these tasks, application scope is replaced by the maintenance requirements developed as part of Tasks IV.22.
In addition to the generic and technology risks discussed in in the risk analysis umbrella activity, the following product maintenance risks must be considered:
risks due to side effects generated by maintenance;
risks due to changes in hardware environment;
risks due to multiple customers with conflicting needs;
risks due to unforeseen implementation difficulties;
Use Browser "back" arrow or return to APM Process Design Language Description