Resistance to change is part of any system upgrade. Imagine that you are working

Question

Resistance to change is part of any system upgrade. Imagine that you are working for a large company that offers its services through a third-party website (such as Facebook). How would you handle change so that users are not turned away from frequent or radical changes, even though they have to be made from time to time?

Legacy systems are particularly difficult to replace, and the conversion strategy is often complex. What are some of the most challenging aspects of going from a legacy system to a new one? Which conversion strategy would you adopt? Support your answer with an example.

Explanation / Answer

Answer)

So as to prevent the users from turning away from radical changes one can perform the changes it at times when the users are less logged it so that it doesn't affect the business and the users work.

The challenges faced when changing the legacy system to new system is as follows:

1) Integration with the other systems

2) Millenial centric focus

3) New Architecture behaving differently

4) Efficiently using the data and not loosing it

5) Rapid updates

etc.

It is always advisable to upgrade the systems as the systems around the environment is changing and to adopt and be acceptable to the other systems upgrading one's system is much needed.

Example: Upgrading the systems (eg : CMA's website) to a newer version with a different coded language for an easy use for the users.

Hope this answer helps. Happy to help. :)

Related Questions

Navigate

• Browse (All)
• Browse R
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.