legacy application migration

Yumasoft Migration Approach

Yumasoft Migration Approach

When organizations desire to re-architect the application and environment, while at the same time reusing a substantial portion of the existing business logic, until recently, the alternatives were:

  • Rewrite the code manually, often outsourced. This is the "big-team" approach, often leveraging low cost developers.
  • The traditional automated legacy transformation approach. This approach incorporates the use of emulation, hidden code and license fees for library routines.

Below are more details on each of these alternatives.

Solution #1: The Manual Rewrite

Rewriting a business application will take a huge amount of time and resources as well as some special individuals familiar with that "old" world, the "new" world and the world of the application. Studies show that many of these efforts fail. Whether done internally or outsourced, the time, labor and quality can be challenging.

The challenges include:

  • It takes a long time and the output is uncertain.
  • The legacy source code documentation may not exist and the authors are gone too.
  • Rewriting requires an army of developers will with many different styles and approaches on re-writing the code. They will also be introducing new interpretations of the legacy code as well as new bugs into the new system. The code and logic will need to be completely debugged and re-proven.
  • The larger the team of developers, the more complex the coordination of the effort becomes. Also, larger teams will have more duplication of effort and more overlap.
  • At some point, a larger team can complicate the project and will extend the development timeframe.

Solution #2: The 100% Automated

The 100% automatically migrated code takes the form of emulated code, proprietary code and XML code. This code is rarely readable, which makes is very difficult to support or customize.

The C# resources in-house can’t do much with the code and the C# tools are irrelevant as well.

The challenges include:

  • The code is very difficult to read and to work with.
  • The readily available C# developers and tools are not much help.
  • Future development and support efficiencies will not be realized.

legacy migration

New Solution: The Yumasoft Migration Approach

legacy migration solutions

Is there a better way? If the legacy code were to be manually rewritten, it would be readable, maintainable, natural code. Can that process be automated? Yes, it can; and that is what Yumasoft does.

Yumasoft will automatically migrate and creates 99% or more of the legacy Dialog System code to natural C# source code. This is done with custom rules to deal with idiosyncrasies in the legacy source code as well specific desired output in the new C# code.

So what would that all look like and would it save any time?

  • The time savings on the migration and generation of the new code are huge.
  • The business logic COBOL code is not migrated and works correctly in the new environment before introducing any new features or customization.
  • Redesign and re-architecture work can then begin and also take advantage of the power of the C# language and resources.
  • The new web-based user interface can be attached to the business logic code.vThe Yumasoft created natural C# code is easily readable making it highly maintainable and customizable, as it has no emulation or proprietary code involved. Any C# developer will be able to understand it, maintain it or modify it using standard tools.
  • Real C# applications that run in the .NET and SOA environments can be created.

Would you like to beat your competition to the internet enabled world of .NET and get informed about the Yumasoft' migration services without any obligation? Then please use the on-line contact form.

The Legacy Code Dilemma

Organizations struggle both in supporting legacy computing environments as well as in moving away from legacy computing environments to modern systems and environments. Yumasoft legacy migration offerings can help in the move to modern systems for both legacy modernization and legacy transformation initiatives.

What do organizations do with that business critical legacy code when they need to get to Web-based services and a SOA/.NET/C# environment?

For the IT team in enterprise organizations and software companies alike, creating new applications for the business is the primary focus, yet, maintaining and keeping the legacy business applications current is a huge endeavor that must be addressed but one where keeping time, dollars and resources to a minimum is critical. The problem looks like this:

In short, organizations desire to re-architect the application and environment, while at the same time reusing a substantial portion of the existing business logic.

Until recently, the alternatives included:

  • Rewrite the code manually, often outsourced. This is the "big-team" approach, often leveraging low cost developers.
  • The traditional automated legacy transformation approach. This approach incorporates the use of emulation, 'black boxes', hidden code and license fees for library routines.

Yumasoft solves this difficult problem by offering a new alternative in migrating legacy code to natural C# code, effectively offering a new approach to legacy modernization projects. Yumasoft does this by migrating the legacy code to natural C# code that can be plugged it into a new .NET architecture. The Yumasoft created code is clean and consistent. It is ideal for creating the C# application platform for today and for future development quickly and cost effectively.

Yumasoft creates natural C# code that works today and is designed to be a starting point for enhancements and future development. Maintaining dual code versions or continuing to

develop in the old legacy code base is no longer necessary. Yumasoft ties the best of an automated tool with intelligent intervention and augmentation to provide high quality, useable, natural C# source code.

The development cycle is drastically reduced, enabling the organization to focus on the architecture.

Additional benefits of this approach are:

  • The code looks like it was hand written by a single top developer, with a high quality, consistent style.
  • Consistent high quality C# code is ideal for moving forward from a maintenance and future development perspective.
  • The debugging and modification process is significantly simplified.