An organization is implementing a new system that supports a month-end business process. Which of the following implementation strategies would be MOST efficient to decrease business downtime?
An organization is implementing a new system that supports a month-end business process. Which of the following implementation strategies would be MOST efficient to decrease business downtime?
A parallel implementation strategy runs both the old and new systems simultaneously and independently of each other. This minimizes the risk of business downtime, as if there is an issue with the new system, the old system can still be relied upon to continue business operations. This ensures continuity and allows for a trial period where issues can be identified and corrected without impacting the business workflow.
Parallel running should have the least downtime
I think cutover is the correct answer since you are going to use the new system only while on parallel you will be using the two systems which is time consuming. pilot could be a correct choice as well since you already tested the new system.
Definitely parallel, Pilot is only temporarily for small parts of the system
D is the right answer
I also thought "D" is the right answer.
C and D are the only changeover techniques here. and out of 2, D is the correct answer. Pilot is not even an option.
I vote for parallel
Parallel running should have the least downtime
D is the reliable for downtime but NOT EFFICIENT since increase redundancy. Remaining option that still can reliable enough for downtime and also efficient should be PILOT CMIIW
D is more safety
Why the hell are they saying pilot is correct if everyone is voting for parallel
The purpose of parallel testing is to ensure that the implementation of a new system will meet user requirements.
Parallel is the most efficient yet most costly one
pilots explaination is different
C. Pilot - A pilot implementation tests the new system with a small group of users or in a limited part of the organization. It can be useful for identifying issues before a full rollout but does not necessarily decrease downtime for the entire business during the transition.
To ensure downtime, running the new system in tandem (parallel) with the old one ensures the least downtime. It's common sense
Parallel execution is the safest because it allows both systems (old and new) to operate simultaneously, reducing the risk of failures during the transition. However, this strategy is the most costly and does not necessarily minimize downtime, as both systems must operate simultaneously for an extended period, and databases may need to be merged and more configurations modified than in a cutover to initiate the parallel process and move it to production. If only downtime is considered, cutover is better.