Application modernization is fast becoming one of the most important items on the CIO’s agenda. There are several reasons for this for example:
- The desire for most organizations to move their applications to the cloud.
- The skills needed to maintain legacy applications are leaving the workforce as they get older.
- To reduce the cost of out of date infrastructure.
Organizations are also learning from experience that application modernization cannot be done successfully manually – automation is essential. Here are some things that should be considered when picking a product to automate the process.
How do you intend to modernize?
What does modernization mean to your organization? Are you looking to:
- Rewrite code in modern languages
- Understand the business rules and move those to a business rules engine for application assembly
- Move from legacy code to microservices for cloud enablement
- Use the existing application specifications as part of RFPs for package replacements
- Understand the applications so you can decide on the best approach to modernization
See what’s out there
Look at what is available in the marketplace. Watch videos on the prospective client websites, review case studies and most importantly talk to others that have used the products before.
Get advice from Gartner
At the time of writing this Gartner does not have a magic quadrant for application modernization tools but it has carried out research into the marketplace and has researchers that specialize in this subject.
Define your portfolio
What is the set of applications that you want to modernize? Do you know what the complete application portfolio looks like, so you can identify all applications in a related area and ensure you are analyzing all the correct systems before deciding on those that need modernization.
Build the repository
Now that you know which applications you will be modernizing they can be moved into the repository. The repository will provide the information on what the application does, what data it uses and how it does it. It should also tell us if we are missing components that are needed for a complete analysis.
Having one repository means that all application are analyzed and documented in exactly the same way. The same style of analysis and documentation means that when comparing systems that comparison becomes so much easier.
Prove the concept
Once you have identified the tool(s) you think might work for you then you should carry out a proof of concept.
Take as much of an application as the vendor will work with and go through the process. Test the outcomes to match what you are trying to achieve. For example, if you are planning a complete migration from legacy to modern language then do that and carry out full testing of the new version to make sure the conversion has happened properly.
The challenge is that the first time you do this you will expect it to be quick and easy – it won’t.
That means when you are budgeting for the resources and the money to run the project then you should expect it to cost more and take more resources than you expected.
If you have selected a good vendor then they should work closely with you on the first project and they will either do it for you or provide experienced practitioners who gave advise and guide your team through their first application modernization project.
EvolveWare prides itself on the service we give our customers – and they would agree. If you would like to find out more about a world-class platform and a company that works with its customers to ensure success then contact us.