Synopsis
Critical business processes running on legacy processing systems make them slow and inflexible. In order to reduce the burgeoning costs associated with these systems for the client, we assessed their existing DEC platform and restructured it to SQL server-based architecture. The restructuring of the system gave the client an updated user interface (UI) created with AJAX. We ensured a smooth transition to the new platform adding value to the client with an enhanced framework, partially automated workflows, and a .NET based GUI.
About the Client
A leading insurance company, the client takes care of the financial needs of approximately 13 million institutional and individual customers in the United States.
Business Challenge
The client’s processed orders for mutual fund units and securities using a legacy order entry and processing system. This system was developed using programming languages such as DEC Basic and DEC COBOL, and the UI was text based. The legacy nature of the DEC platform had its own limitations, and the client came to us looking for a trusted technology partner to migrate their legacy DEC processing system to an improved .NET framework. Our tool-based approach to assess the source code led to the formulation of an effective migration strategy.
Our Solution
The client partnered with us to:
Devise a strategy to migrate from a legacy processing system to a modern .NET framework and execute the migration Transfer data from Indexed Sequential Access Method (ISAM) files Upgrade the text-based UI to an improved AJAX supported graphical user interface (GUI) Test the migrated code for performance and functionality Automate processes using the Insight tool framework.
Our team was entering unfamiliar territory when they began assessing the DEC environment and its functionality. But after spending a week training with the client’s team, our team started assessing the source code of the DEC platform based on tools. Our team used the code slicing methodology in this migration project, adhering to global standards of .NET architecture migration. A strategy to ensure a seamless transition was developed after analyzing the inventory, redundancy, dead code, and source code in its entirety. Partnering with the client, the team initiated the manual migration of the source code. The migration was a success because when the team gave the code to the client and the users for testing, it matched the legacy system in capability as well as utility.
After the effective migration, the migration project team conducted workshops with the Coforge Insight tool group. This was done to identify the extent of automation that could be achieved with this new architecture using the Insight tool framework. The client wanted a .NET based GUI—making complete automation difficult to implement. Navigation and controller logic, as well as business logic along with the screens was automated. Apart from this, Virtual Machine Systems (VMS) control scripts and selected batch programs were also migrated.
Delivering More Value
Our solution streamlined the migration process for the client. This allowed them to upgrade their order entry system to a .NET framework in the most efficacious way, bringing with it all the benefits of modern architecture. The advantages to the client included:
More Efficiency: By using testing tools and regression testing, the involvement of the client in testing the new environment was kept to a minimum. More Productivity: Our team’s hybrid migration methodology of a tool-based approach and code slicing assisted the client in carrying out a comprehensive and fastidious migration project. More Automation: The adaptability of a .NET framework offers a system to developers that can be easily maintained and modified. More User- and Developer-friendly: .NET framework is an adaptable and revolutionary platform. With the initiation of this migration, the client has reduced any limitations that existed in the previous system due to a lack of interoperability. Since a batch portion of the application fulfilled the batch processing window requirements of the legacy DEC system, the migrated .NET system is now in production with the client.
