In last weeks post, we looked at the potential disaster that is being faced by organizations that are reliant on legacy applications.

However, it is not all doom and gloom. There are solutions available that will help you work through to avoid the disaster in a step by step approach.

The first thing that any organization needs to do in this scenario is to understand what applications they have and what they do. To do this you need to be able to process the code and turn it into standard documentation so that for every application there is a consistent set of diagrams and reports to explain the functionality.

The next step in legacy modernization is to know fully what each of the business rules embedded in the code are and do. To do this the business rules need to be extracted from the source code, pieces of logic need to be combined or split to form meaningful rules and then the programming jargon should be translated into business terminology.

Now, the organization has a complete set of the business rules that are being performed by the legacy applications and can do several things:

  1. Compare the business rules across applications to identify duplication
  2. Score the rules from a business and technical viewpoint so it is possible to pick the best ones.
  3. Once you know which are best you can choose to either rewrite those rules in a modern language or you can use them in an RFP so bidders know exactly what is required or they can be compared to COTS packages to see coverage and convergence.

The final stage is to use the logic embedded in the business rules to generate the application(s) in modern languages.

This whole process can be supported by EvolveWare’s Intellisys platform and by using this approach will help in avoiding the disaster that we have been discussing.

For a demonstration of what Intellisys does click here or contact us for an immediate conversation.

retirement of knowledge