In the ’70s and ’80s, we did not believe that we were writing legacy systems when we developed large business applications in COBOL. Yet, that’s what happened. So, how do you avoid creating another such situation? What happens in six years if the modernization language you choose today becomes unsupported and some new language is the new platform of choice? Well, if you modernize with Engineer, you will save dramatically on making further platform changes, because your code is properly structured and completely standardized – and chances are we will support the new platform and can re-generate the bulk of your code to fit.
We know that what needs to get delivered is working software – not labor hours or “months”. So why enter into a contract that simply has a monthly cost and a promise for delivery sometime years in the future?
Don’t forget, you can license ResQSoft® Engineer to maintain your new system, too. You don’t have to, of course; your new code can be maintained by your established support contractor, or by your staff, or by us, or by some combination, whatever you prefer. You get full source code, and you’re not locked in to ResQSoft as a vendor or our tools.
When faced with the need to modernize, re-engineering with automated code writing, aka code generation is one option. There is always some hand work to be done, because the code generators handle all the routine code, and some additional functionality will need human attention.
There are a number of vendors who promise to take your old code (HTML, COBOL, Visual Basic / VB, ASP), and give you back new code using a wholesale, line-by-line conversion into a new language. And, it will usually work, but the translated code retains the structure and naming from the old code.
ResQSoft’s adaptive reuse technology is equally proficient at developing custom applications from scratch or leveraging COTS software to build these systems by keeping configuration changes to a minimum and supplying additional needed functionality with bolt-in modules that are rapidly and inexpensively created with automation assistance. The key to success is our approach.
The usual options for business or government legacy software migration to the Web are pretty unattractive: you can use some kind of “screen scraping” technology, but then you are stuck with maintaining the legacy application and your users still don’t really get a modern Web interface. You can try to adopt a COTS software package, but even if you can find one, it probably won’t meet all of your requirements.
The ResQSoft® approach to legacy systems integration is very straightforward. Our process generates code in the Java or C# programming language that implements standard architectural patterns for legacy integration. We anticipate that most projects can be completed within a single budget cycle and at less than half the cost of manual code integration.
Looking to have your legacy applications modernized to .NET?
ResQSoft® is Flexible, we can modernize any legacy language; from Powerbuilder, ASP, or COBOL to a modern .NET implementation.
Check the current list of our supported legacy languages. Otherwise, if you don’t see yours, CALL US! We have tools that let us work with the HTML produced by almost any application that runs in a browser window. Additional tools allow us to handle IDEAL, Datacomm, and some other legacy mainframe environments. New languages take a matter of weeks to support. Check our FAQ page if you have more questions or Contact us directly. We’ll be more than happy to help you!
Yes, we have AngularJS 1.4 and 1.5, and now we are on to Angular 9!
For at least 8 years, the Gold Standard for legacy software modernization at the enterprise level has been Java – just ask Forrester or Gartner. Yes, Microsoft .NET is the #2 choice, and depending on whose figures you look at and what you include in the .NET category, Microsoft may be gaining ground. We don’t mind which one we do, we can handle both and help you pick the one that’s best for you.
Benefits of Moving to Java
The benefits of moving to Java are many. The process may seem arduous, and there is some initial outlay involved (although, over the life cycle, the savings are immense). But delay only makes it more difficult to move, and delay also puts off harvesting the cost savings and other benefits that are available. These other benefits include the ability to use modern tools and open-source frameworks, avoiding the effects of the dwindling pool of legacy developers, and the ability to readily put in place an enterprise architecture and implement a service oriented architecture (SOA) for the enterprise that allows ready sharing of data and services among applications.
Java Becomes Legacy, Too
About 20 years ago, Java was being used to build web applications and business systems. Those were the days of Java 2 Enterprise Edition (J2EE), and many of us used the Struts Framework to implement a Model View Controller design pattern in these applications. We wrote a lot of code — getters and setters, beans of all sorts, and a proliferation of object classes that seemed to be required by the dictates of software engineering. We worked with JDK 1.3 – 1.5, and then Java 6. Most of what we did in those years still works, of course, but Java and the frameworks have evolved a lot and new concerns – like cybersecurity – have taken on greater importance.