If you had to produce documentation for your legacy application tomorrow, could you do it? Maybe not tomorrow...you would have to find it. What about next week? That would give you time to find it, but it's a hard copy so it needs to be scanned and reformatted. A month from now? The information isn’t updated; that will take some time. A year from now? Surely that’s enough time to get the whole thing rewritten, but almost everyone who knew how the system really works has left the company, and the few remaining will be retiring soon.
Documentation of your legacy system is very important for a number of reasons. People are still using it! New hires will benefit from having a reference. Auditors may require documentation of your internal processes, which would include interactions with the legacy system.
When it comes time to migrate the applications to a new platform, the documentation becomes an invaluable tool for insuring that the new system functions the same as the old one. Even in the worst-case scenario, where the source code for an application has been lost, adequate documentation can be used as specs to facilitate a rewrite on the new platform.
The point of all this is to encourage you to make sure you have current documentation now, before it becomes a crucial issue. Resources may have to be pulled away from other tasks that are also important. Time and cost may have to be justified to upper-management. It’s easy to find an excuse to put it off, but that will only make it more time-consuming and costlier in the long run.
Here are some of the most common mistakes in legacy transformation projects and how to avoid them when designing your modernization strategy.
How do you test core enterprise applications that are being migrated from a mainframe to a private cloud in the timeframe of a weekend?
As technology advances, mainframe organizations are increasingly pressed to transition to more modern platforms. Here are some of the most common misconceptions that hinder their mainframe modernization journey.
The cost of not modernizing mainframe systems is generally far greater than the time, effort, and money required to make the transition. Here's why.
As mainframes host mission-critical applications, it's essential to ensure that the modernization process is accurate and causes minimal disruption to business operations. This is where automated migration and testing tools come in.
Get in touch with our experts and find out how Astadia's range of tools and experience can support your team.contact us now