0% found this document useful (0 votes)
57 views

Parallel Change

Parallel changeover involves running the new and old systems concurrently until the new system is proven to work reliably with low risk. This allows users time to familiarize themselves with the new system while assuring a fallback to the old system if issues arise. However, it overstrains resources and requires data to be entered twice. Direct changeover replaces the old system entirely on a set date, using fewer resources but providing no fallback if problems occur. Pilot changeover tests the new system at a single site first before broader rollout, catching issues at smaller scale. Phased changeover implements parts of the new system gradually until complete to combine benefits of parallel and direct while limiting impact of any failures.

Uploaded by

Boru
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
57 views

Parallel Change

Parallel changeover involves running the new and old systems concurrently until the new system is proven to work reliably with low risk. This allows users time to familiarize themselves with the new system while assuring a fallback to the old system if issues arise. However, it overstrains resources and requires data to be entered twice. Direct changeover replaces the old system entirely on a set date, using fewer resources but providing no fallback if problems occur. Pilot changeover tests the new system at a single site first before broader rollout, catching issues at smaller scale. Phased changeover implements parts of the new system gradually until complete to combine benefits of parallel and direct while limiting impact of any failures.

Uploaded by

Boru
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Parallel changeover

It involves running both the new and old system concurrently until you are confident that the new
system is working effectively with low risk. The strategy assures a rollback to old system in-case
something goes wrong with the new system. The strategy also allows user time to familiarize with new
system and gain confidence to use it.

parallel changeover

The main shortcoming of this strategy is that it over strains resources because they are required in both
systems. It requires large storage capacity to accommodate both systems. User will be required to do
double entry of data, both in the old and new systems. It is also difficult to compare the two systems
and how they output data because they may be completely different. Another problem comes in
determining for how long you should run the old system before replacing it completely.

Direct changeover

In direct changeover the old system is replace on time with a new system. It is mostly used when the risk
of losing data from the old system is significantly low or if the system has most the functions that are
new. It uses less resource because only one system is running.

direct changeoverWith this system if something happens with the new system then it means no going
back to the old system because it is no more. Users are not confident enough to use system on initial
day of system implementation hence they operate relatively slow on the operation involved.

Pilot changeover

It means choosing a specific location or branch of the organization and implementing the system in that
branch first. The branch (location) where the system is first test before it is implemented in the whole
organization is called pilot site. It allow to test the system on a small scale on all it functionality and
make any changes necessary to avoid any problems when later it is rolled on all organization branches.

pilot changeoverThe strategy is used as alternative to parallel change over because it cost less and it
almost achieves the same results.
Phase changeover

Phased involves implementing a module of the system at a time until the whole system is implemented.
It combines the parallel and direct change over strategies. The module can be a functional part of the
system or a specific subsystem. Each sub system is implemented until it succeeds that when the next
one is implemented. It means in case the new system fail then it is only that part that is affected and not
the whole system.

phased changeover

The main challenge is that before the whole system is implemented it may take long time.

Different strategies are used at different time depending with the organization circumstances at that
particular time.

You might also like