In the context of a database information system, the hardware requirements
Training ensures participants are able to use the new system. The type of implementation is dependent upon the existing knowledge of the participants and the scope of the change. Management may decide to train some leaders who then instruct others. They may also employ training specialists or create training manuals. Technical support staff are often employed or out-sourced for use on an 'as-needed' basis.
Participants can compare both systems and obtain a good understanding of the differences between the systems. If there are any problems with the new system, they can be solved before the old system is discontinued.
However, parallel conversion results in additional workloads and is a low risk, high-cost method for participants, as they must operate both systems until the new system is accepted. It may also result in confusion about which system has the correct data.
Example scenario of using parallel conversion in context:
The old system ends and the new system starts. All data from the old system is transferred to the new system, and the participants stop using the old system and begin using the new system. Direct conversion is not commonly used even though there are minimal transition costs. One reason that direct conversion is not commonly used is that it does not allow the project team to check whether the new system will operate correctly and whether participants understand the system. Another reason is that, if the new system fails or problems occur, the old system is not available as a backup.
Example scenario of using direct conversion in context:
Certain operations of the new system are implemented while the remaining operations are completed by the old system. When one operation of the new system is successful, another operation is implemented until the new system is fully operational. Each operation is individually tested.
If there is a problem with an operation, it is possible to switch back to the old system. Unfortunately, phased conversion is often confusing because some participants are on the old system and some are on the new system.
Example scenario of using phased conversion in context:
Involves trialing the new system in a small portion of the organisation. The old system is still available if the new system fails or experiences problems. If pilot conversion works, it is usually easier to motivate the other participants of the organisation to change to the new system.
Information processes are continually tested during the implementation of the system over a period of time. Minor changes to procedures are immediately implemented.
Example scenario of using pilot conversion in context:
Operations manuals are ALWAYS created with the end user in mind.