The strategy describes the general approach that will be adopted during the implementation of systems, based on a desire to minimize dependencies or interfacing requirements, cost and organizational change. The document identifies the key considerations on which the strategy is based, and defines the types of implementation (big-bang, shadow, fade-out, etc.) that will be employed. The strategy will in a later stage be the input for the Implementation Plan.
For each implementation strategy, the following elements are considered:
General requirements
The way business systems and data stores are dealt with in the strategy e.g., the level of automation, the use of standard packages, and the sharing of systems and data stores throughout the enterprise.
The use of technology
The level of sophistication, the speed of implementation of technical components, and the overall business impact (the competitive edge) of the technical solution. This part of the strategy relates to the technical architecture options of the task Define Technical Architecture.
The organizational impact
The required changes in the IM organization, the special staffing and educational needs for this strategy and the impact on the overall organization's tasks, structures, and required policies.
Transition from existing systems
A global view is given on the order and speed of the new systems analysis and development.
» Created by task A3.7.6 Define implementation strategy
ð Updated by task A3.7.9 Develop design area project plan
ð Updated by task A3.14.1 Assess implementation strategy
ð Updated by task A4.2.1 Revise implementation strategy.
ð Updated by task A4.8.5 Sequence the implementation areas.
ð Updated by task A4.13.1 Finalize design for implementation.
» Created by task A11.2.5 Identify implementation requirements
ð Updated by task A11.5.3 Review implementation plan
Next : This is the last Sub-Deliverable of Deliverable D3.7
Previous : D3.7.4
Activity Overview : D3.7
Stage Overview : Analysis Stage
Overview : Table of Contents