Answer to Question #203559 in Management for natinael

Question

2. After a new business information system is developed, there are different conversion strategies that an Information System analyst team follows to switch from old system to the newly developed system. Discuss these conversion strategies briefly and suggest one which you think most risky in terms of information loss (assuming other things constant)

Answer 1

Conversion to a New System

Analysts can choose from a variety of conversion techniques and a contingency approach that considers numerous user and organizational aspects when determining which conversion method to apply. There is no one-size-fits-all approach to conversion. The need for proper conversion planning and scheduling and strategic user interaction, file backup, and suitable security cannot be overstated. The strategies are as follows:

Direct Changeover

This means customers will be forced to stop using the ancient structure on a specific date and begin using the current system. It works only when testing is done ahead of time and does best when significant processing delays can be endured. It can also be regarded as a dangerous conversion method as users are being forced to utilize a new technology without choice may cause workplace disruption.

Parallel Conversion

Running the old and new systems in parallel is what this term refers to. When the first-hand system produces the same effects over a period of time, the ancient system becomes withdrawn. One advantage of operating both of the systems in parallel is that there is the capability to compare new information to old information in classifying any processing difficulties in the new system.

Gradual Conversion

As the system is phased in, the volume of transactions fingered by the new system is gradually raised. Some of the advantages of this strategy include allowing users to gradually become accustomed to the system and recover from faults with minimal downtime and add functionality one at a while. This method is commonly used in agile techniques.

Modular Conversion

It gradually transitions from old to new systems by constructing self-contained, operational subsystems. Each module is extensively tested before being utilized, which is one advantage. Another advantage is that when each module becomes operational, users become familiar with it. Their input has aided in the development of the system's final features. This is a common strategy in object-oriented methods.

Distributed Conversion

It describes how many installations of the same system are being considered, such as in banking or franchises like restaurants or clothes stores. One site handles the complete conversion. After that conversion is performed successfully, subsequent conversions for other sites are carried out. Distributed conversion has the advantage of detecting and containing errors rather than inflicting them on all sites simultaneously. One downside is that, even if a conversion is successful, each location will have its own people and culture, as well as regional and local differences to deal with, all of which must be addressed appropriately.

Therefore, the direct changeover is risky from the above strategies since users' resentful at being forced to utilize a new technology without choice may cause workplace disruption.