I was discussing a modernization project with a prospect the other day and they were using an automation tool and service provider to carry out the migration. They were not using Intellisys.
The prospect could not understand why I said they needed to keep the Intellisys platform once the project was over.
Their experience, from past projects, was that the services supplier would provide them with the new code, support it for 90 days and then walk away. Now that’s great for the services company but all the customer has got is a new legacy application because:
- The knowledge of how the code was written has just walked out the door.
- There was no documentation handed over – all the customer has are the original specifications.
- There is no correlation between the new code and the legacy code so the “heritage” of the code has been totally lost.
This is totally different from the approach we recommend.
Assuming the migration project has been carried out to an agreed methodology then at the end of the project there are certain deliverables that are mandatory:
- The new code which has been completely annotated not only with developer notes but also showing where the code came from – embedding annotations which shows the code from the legacy application
- The complete set of documentation – functional and data as the reference for the application.
- The capability to manage the new system – to make changes and enhancements while keeping the documentation up to date.
If you do not get these things as standard deliverables when doing a modernization project then you have just spent a lot of time and money creating a new legacy application.
The EvolveWare approach is that no matter the level of our involvement in the project we make sure that the new application is fully documented and, although we cannot force it, we strongly advise customers to keep using Intellisys as the life-cycle management tool for their new applications.
For more details or to discuss your project requirements contact us.