6 Ways to Modernize Your Legacy Systems
posted by John Spacey, December 06, 2012Unlike fine wine, systems don't age well.
Eventually, legacy modernization is a challenge for every organization. If you're experiencing risks, costs and inefficiencies with your old systems a legacy modernization project may be in your future.
There are 6 common approaches to legacy modernization each with it's own particular set of risks, costs and benefits.
1. Host Migration
The legacy application is migrated to new hardware. For example, a mainframe application may be migrated to Wintel to replace aging, out-of-support hardware.Host migration is a relatively low risk project but leaves you with your aging architecture.
2. Technology Migration
A translation of the existing system to a modern programing language and tool set. In many cases, automated tools can be used to speed development (e.g. source code transformation).This approach is most successful when the system is migrated as-is to simplify development, testing and business implementation. New business requirements can then be added in a phased approach when the technology migration is completed.
In practice, new requirements are usually included in the first release and may be difficult to avoid. For example, a new user interface may be required.
The technology migration approach is relatively low risk. It can dramatically extend the life of legacy investments.
3. Architecture Migration
An architectural transformation of the legacy code to a modern architecture (such as SOA).As with technology migration, this approach is most successful when the system is migrated as-is (no new requirements).
The architectural migration approach dramatically extends the life of existing system investments and is relatively low risk.
4. New Development (Greenfield)
Discarding the legacy system and building a new system from requirements.This approach is common when the legacy system is unpopular with users. The business wants to move beyond the legacy system by completely discarding it.
Modernizing a legacy system with new development is typically challenging. This is especially true when the legacy system is big. User requirements may miss business rules that were built into the original system for good reason.
New development works best as a phased approach with the legacy and new system running in parallel until the modernization is complete.
5. Package Implementation
Replacing a legacy system with a package such as ERP or CRM.Implementation of large packages such as ERP is a challenging undertaking that requires transformation of your business. Organizational maturity is required to align business units with the new system and implement business process changes.
6. Hybrid Approaches
It's common to apply more than one approach to legacy modernization. For example, the legacy system may be migrated to a new architecture such as SOA and integrated with an ERP.
|
How to architect an organization. |
|
The most important diagram in all of business architecture — without it your EA efforts are in vain. |
|
The exciting world of ITIL metrics. |
|
Yes and no. There's no ITIL certification process offered by ITIL itself. However, an organization that's reached ITIL maturity can generally be ISO 20000 certified. |
Recently on Simplicable
| The Big List of Information Security Vulnerabilitiesposted by John SpaceyUnderstanding your vulnerabilities is the first step to managing risk. |
| The Big List of Information Security Threatsposted by John SpaceyUnderstand the threats to your organization. |
| 8 Enterprise Architecture Risksposted by Anna MarEnterprise Architecture (EA) is supposed to help manage IT risks — but is it possible that EA itself introduces new risks? |
| Security Through Obscurityposted by Anna MarSecurity through obscurity is generally considered a bad idea ... |
