V.31.1 Review technology and project risks associated with the reengineering task.
V.31.2 Identify potential technical side effects that reengineering application may cause for interoperable systems.
V.31.3 Assign risk probabilities to each risk and side effect.
V.31.4 Estimate risk/side effect impact.
V.31.5 Determine high priority risks/side effects.
V.31.6 Develop plan for mitigating, monitoring and managing
V.31.7 Review risks with management/customer.
These tasks are conducted using the approach defined in the risk analysis umbrella task.. For these tasks, application scope is replaced by the reengineering requirements developed as part of Tasks V.29.
In addition to the generic and technology risks discussed in Tasks U.8, the following application reengineering risks must be considered:
risks due to side effects generated by reengineering;
risks due to changes in hardware environment;
risks due to multiple customers with conflicting needs;
risks due to unforeseen implementation difficulties;
risks due to "cut-over" when the reengineered system goes on-line
Use Browser "back" arrow or return to APM Process Design Language Description