What is a significant drawback associated with the Parallel Strategy Conversion method?

What is a significant drawback associated with the Parallel Strategy Conversion method?

• A. Time-consuming process
• B. Expensive to maintain
• C. Requires extensive user training
• D. High risk of data loss

Answer: (B)

The parallel strategy conversion method involves running both the old and new systems concurrently during a transition period. This approach allows for immediate comparison between the two systems, ensuring that any errors or issues with the new system can be promptly identified and addressed. However, a significant drawback of this method is that it can be expensive to maintain. Running two systems simultaneously requires resources for both sets of operations, including hardware, software, and personnel. The duplication of effort can lead to increased operational costs, making it an expensive choice for organizations, especially if the transition period is prolonged. Furthermore, continuing to support both systems can strain IT resources and budget, leading to potential operational inefficiencies. While this method offers the benefit of reduced risk during the transition, the financial implications of running two systems can be substantial, especially for organizations with limited budgets.

The parallel strategy conversion method involves running both the old and new systems concurrently during a transition period. This approach allows for immediate comparison between the two systems, ensuring that any errors or issues with the new system can be promptly identified and addressed.

However, a significant drawback of this method is that it can be expensive to maintain. Running two systems simultaneously requires resources for both sets of operations, including hardware, software, and personnel. The duplication of effort can lead to increased operational costs, making it an expensive choice for organizations, especially if the transition period is prolonged.

Furthermore, continuing to support both systems can strain IT resources and budget, leading to potential operational inefficiencies. While this method offers the benefit of reduced risk during the transition, the financial implications of running two systems can be substantial, especially for organizations with limited budgets.