Case Study: Updating a Visual Basic middle tier for a legacy financial application, saving a software provider millions

The Challenge

A major financial software provider was operating a legacy green screen application with a Visual Basic 6.0 middleware frontend. While the application was wildly successful it created a significant issue for several of the organization’s banking clients due to the fact that it could only be run on Windows 3.5 or earlier. Modern banking establishments were unable to run the software on Windows 7, or even Windows XP or 2000.

Updates in technology were about to make the system – which was the system of record for most home loans and mortgages – inaccessible. This presented the client with a critical problem, as major financial institutions were paying hundreds of thousands of dollars per month to leverage the software.

The software required logic updates and was not designed for modern consumer and commercial products. Additionally, its original creator was no longer available, and no one else on the client’s development team had a grasp on all of the business logic. The client engaged Magenic to create a middle tier while maintaining some of the business logic behind the core application.

Enterprise financial app becoming inaccessible

The Solution

Magenic leveraged CSLA .Net to create a middle tier which performed some of the original business logic. Magenic advised the client’s development team to update the host applications on the new CSLA .NET middle tier.

Magenic created updated, more usable screens to accommodate new business products; this was required to validate fields within the middle tier. Our new solution validated data before sending it back to the mainframe, and combined pre-existing fields from separate screens on the same screen. This allowed the new application to function utilizing the new screens and user interface. Instead of sending each individual field back to the mainframe, Magenic’s application stores the information in bulk and forwards it back in bulk.

Because the client development team was unfamiliar with the business logic, Magenic reverse-engineered the logic to provide the client better understanding. The total development effort spanned the course of three years

Custom CSLA tier, reverse-engineer logic

The Result

Magenic’s solution allowed the software to work with Windows XP and beyond and is still the system of record for many home loans and mortgages to this day. The new application was so successful that the client’s parent company bought them out. It continues to generate millions of dollars in revenue on a monthly basis.

Other software developers have attempted to build similar programs to serve as competitors, but Magenic’s solution has helped to ensure that our client’s application remains the go-to system of record for home loans and mortgages.

Custom Software Development Case Study
Compatible with XP and beyond
Download PDF

Click to download the Major Financial Software Provider case study as a PDF.

Application Becoming Obsolete

A major financial software provider’s primary application was about to become obsolete. Because the application generated hundreds of thousands per client in monthly income, the green screen application that only ran with Windows 3.5 or earlier put the client’s business in jeopardy as technology changes approached. The application needed to be updated to work with newer versions of Windows and also needed its business logic updated to handle variable interest loans.

Custom Software Development Case Study
Summary

Upgrades in technology were about to make a major financial software provider’s application inaccessible. Incompatible with Windows versions beyond 3.5, the organization stood to lose millions of dollars if its application were no longer the system of record for home loans and mortgages. Magenic developed a CSLA .NET middle tier that allowed the application to work with Windows XP and beyond. On top of that, we also reverse-engineered the business logic to provide the client development team a better understanding of the logic, as the original creator was no longer available to do so.

Technology Used
  • CSLA .NET
Copyright 2013 Magenic, All rights Reserved