| |August 201819CIOReviewApart from choosing the best strategy for the digital modernization, the process involved is more significant for ensuring a smooth migration to a new systemalso comply with the newly redesigned application. A separate change requirements repository needs to be maintained for them as well if they are to be modified or replaced.4. SecurityLegacy systems always run the risk of being more sus-ceptible to security risks, since most of them are far beyond their warranty period and not updated for latest security updates from their vendors, resulting in consider-able security gaps. To ensure a robust, fool-proof modern-ized application, it is of para-mount importance to foster a development culture aimed for reduction of security and quality risks, especially in mis-sion-critical modules. Strin-gent testing should also be performed for unearthing se-curity lapses before going live. 5. Documenting the Project LearningsFunctional shortcomings or bad designs of the legacy system need to be documented to avoid repetition of the same in the new, redesigned application. Risk Assessment, as well as the risk mitigation techniques, should also be included. This should also encompass industry coding standards, best practices and other architecture standards for the application. This will ensure a good, understandable programming code which will be easy to maintain, debug and extend.6. Decommissioning the Legacy SystemModernizing a legacy system does not mean that the legacy system has to trashed immediately. It is important to allow the new system to settle down for a period long enough to be able to take care of all existing functionalities of the legacy system, shoulder the extra burden of added functionalities in terms of hardware capacity and acceptance from the users. Till then the legacy system will still have to be used in parallel, although in a reduced manner. This will ensure that any issue which is not manageable by the new system can still be addressed with the legacy system. The IT department needs to chalk out a retirement schedule in phases for the legacy system before completely decommissioning it.7. DevOps for SustainmentEmploying a DevOps model for modernization will be effective in using smart coding and uninterrupted maintenance of the legacy system whilst using the existing code. It will extend agile development to aid in leveraging automated tools for better integration during the entire lifecycle. This further collaborates a better working culture between software development and operations teams, leading to faster deployment as and when needed.8. Adequate Training and UpdatesModernization of IT also involves pulling up the human resources involved to the desired skill levels to be able to work in the new environment and to meet new expectations. Users of the legacy system will need time to migrate to the new system which will differ in terms of user interface, navigational aspects and operating methods. To ensure this, appropriate training budget should be allocated for imparting the correct know-how and guidance to users of the new system.Apart from this, the new system also needs to be updated with new features, functionalities and hardware from time to time­ the absence of which will pose a fresh challenge in the modernization process. Although the entire modernizing process may seem very daunting in terms of the complexity, risk and effort involved, companies still need to adopt it to attune themselves with the current technology demands of the digital age.
< Page 9 | Page 11 >