During system deployment, which conversion strategy activates one module or subsystem of the new information system at a time to reduce risk and ease cutover?

Introduction / Context:
Cutover strategies determine how a new system replaces an old one. Options include direct (big bang), parallel, pilot, and phased conversions. Choosing the right strategy balances risk, cost, and speed. This question targets the approach that turns on pieces of the new system incrementally.

Given Data / Assumptions:

• Modules can be decoupled functionally (e.g., order entry before billing).
• Operational risk should be limited at each step.
• Users can adapt progressively.

Concept / Approach:

Phased conversion introduces the new system in segments by function, department, or geography. Each phase stabilizes before proceeding, enabling feedback and fixes without jeopardizing the entire operation. It contrasts with pilot (one site only) and direct cutover (all at once), and is not a tool (CASE) nor the SDLC itself.

Step-by-Step Solution:

Verification / Alternative check:

Implementation guides recommend phased cutovers when inter-module dependencies are manageable and risk tolerance is low.

Why Other Options Are Wrong:

CASE tool and SDLC are process/tool concepts, not conversion strategies.

Success factors are conditions for success, not a method.

Common Pitfalls:

Poor dependency mapping can stall phased rollouts; plan data migration and interface bridges carefully.

Final Answer:

Phased Conversion