Objectives: Introduction Over View of System Analysis and Design


Table 9.1 Methods of Systems Conversion



Download 0.94 Mb.
View original pdf
Page122/140
Date13.11.2023
Size0.94 Mb.
#62581
1   ...   118   119   120   121   122   123   124   125   ...   140
ms-04

Table 9.1 Methods of Systems Conversion

Method
Description
Advantages
Disadvantages
Parallel system
The old system is operated along with the new system Offers greatest security. The old system can takeover if errors are found in the new system or if usage problems occur. Doubles operating costs. The new system may not get fair trail.
Direct conversation
The old system replaced by the new one. The organization relies fully on the new system. Forces users to make the new system work. There are immediate benefits from new methods and controls. There is no other system to fallback on if difficulties arise with new system. Requires the most careful planning.
Pilot system
Working version of system implemented in one part of the organization. Based on feedback, changes are made and the system is installed in rest of the organization by one of the other methods. Provides experience and live test before implementation. May give the impression that the old system is unreliable and not error- free.
Phase – in
Gradually implement system across all users. Allows some users to take advantage of the system early. Allows training and installation without unnecessary use of resources. Along phase – in causes user problems whether the project goes well (over enthusiasm) or not resistance and lack of fair trial.

9.3.1.2 Direct Cutover
The direct cutover method converts from the old to the new system abruptly, sometimes over a weekend or even overnight. The old system is used until a planned conversion day, when it is replaced by the new system. There are no parallel activities. If the analyst must make the change and wants to ensure that the new system fully replaces the old one so that users do not rely on the

previous methods, direct cutover will accomplish this goal. Psychologically, it forces all users to make the new system work they do not have any other method to fallback on. The advantage of not having a fallback system can turn into a disadvantage if serious problems arise with the new system. In some instances, organizations even stop operations when problems arise so that difficulties can be corrected. One organization allocated its entire accounting staff to entering data to start anew automated system. The task took approximately three weeks, during which time none of the regular accounting operations that were to be converted to the new system were performed. Consequently, a three – week backlog of work developed. However, such backlog was expected and management had planned to authorize overtime work and the hiring of temporary assistance to catch up after conversion. Approximately two days before the direct cutover was to take place, a senior manager realized that the accounting department was not planning to preserve the data for accounts receivable aging. The manager stopped the conversion. As a result, the accounting staff had to catch upon three weeks work and reschedule the conversion to a date one-month later, when many of the previous steps had to be restarted. The system was finally implemented three months later, after much extra work, overtime, and staff frustration because of the way the cutover was handled. Stopping conversion was a particularly drastic measure. It would have been doubly bad had the steps been taken because of technical problems needing correction. If users know that a system was once halted because of difficulties, they may not be fully confident that the system will be reliable, even if analysts tell them that the problems have been corrected. The time it takes to redo work that was stopped because of the conversion can be both lengthy and costly, and time lost can never be recaptured. Direct cutover require careful planning. Training sessions must be scheduled and maintained. The installation of all equipment must be on time, with ample days allowed in the schedule to correct any difficulties that occur. Any site preparation must be complete before the conversion can be done. Direct conversions are quite common, particularly with purchased or turnkey systems. For example, a hotel operation decided to install an automated reservation system. The entire system was implemented during a one – week period, when the computer system was setup, the

software loaded, and the system tested. During that week, a separate training crew worked with all the accounting and front desk personnel to familiarize them with the operation and use of the system. These activities occurred Monday through Saturdays. On Sunday, all personnel were brought into enter reservations, guest charges, and accounting information into the new system so that it coincided with the current system. On Sunday, evening, after the close of business for the day, the new system was started and used permanently. The old paper reservation file was removed, and the cash registers and bookkeeping machines were replaced with the terminals. The new system became live at midnight on Sunday. There was no old system to fallback on.

Download 0.94 Mb.

Share with your friends:
1   ...   118   119   120   121   122   123   124   125   ...   140




The database is protected by copyright ©ininet.org 2024
send message

    Main page