Conversion method terminology: when users continue operating the old system alongside the new system during transition, this approach is called what?

Introduction / Context:
Cutover choices matter. To lower risk, organizations sometimes keep both the legacy and new systems running concurrently so results can be compared and teams can fall back if necessary. The term for this approach is “parallel run.”

Given Data / Assumptions:

• Users are already trained on the old system.
• New workflows and data structures exist in the new system.
• The transition period is temporary and has defined exit criteria.

Concept / Approach:
Parallel run duplicates transaction processing. It emphasizes reconciliation: totals, exception lists, and audit trails are matched between systems. This increases confidence and supports defect triage before retiring the legacy system.

Step-by-Step Solution:
Identify the option that names concurrent operation of old and new systems.Exclude unrelated computing terms such as multiprocessing and multitasking (CPU-level concepts).Select “parallel run.”

Verification / Alternative check:
Project plans often document “parallel run duration,” “reconciliation thresholds,” and “rollback triggers.” These artifacts apply specifically to the parallel run strategy.

Why Other Options Are Wrong:
Multiprocessing and multitasking describe hardware/OS execution modes, not rollout methods. “All of the above” cannot be correct because only one term refers to the conversion strategy.

Common Pitfalls:
Neglecting data synchronization, identity mapping, or cutover rules; parallel periods that last too long can be costly.

Final Answer:
parallel run