III.17.1 Identify enhancement-specific risks and side effects.
Risks associated with enhancement can be isolated by considering which aspect(s) of the system are being enhanced. If function is extended, risks associated with algorithmic error, poor existing descriptions of modules, and other component-level features must be considered. If data are to be extended, limitations of the data structure(s) are the dominant concern. If behavior is modified, the state-transition description of the software must be explored to determine if new/modified events cause the proper stae-to-state transition.
III.17.2 Project likelihood that risks and side effects will occur.
See Risk Analysis umbrella activity for details.
III.17.3 Project impact of risks and side effects on developers / customers and on overall enhancement strategy.
See Risk Analysis umbrella activity for details.
III.17.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 enhancement requirements developed as part of Tasks III.15.
In addition to the generic and technology risks discussed in the Risk Analysis umbrella activity, the following product enhancement risks must be considered:
• risks due to side effects generated by enhancement;
• 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
