Displaying items by tag: modernization

When it becomes apparent that legacy code must be replaced, modernization is often the best possible strategy. With code modernization it is possible to refine the original code and bring it up to modern practices, as well as integrating it with existing software. One of the problems with modernization, however, is that critical applications tend to have thousands of lines of code and a manual rewrite is often impossible. To re-create the software requires a project of similar magnitude to the original development; to leave most of the code intact as a “black box” and build around it results in numerous security issues and inefficiencies, as well as inability to leverage emerging technologies.

If you've ever seen the MUMPS language (used by many healthcare applications in the federal government), it's not the easiest language to understand. One of my colleagues describes it as looking like "a cat walked across the keyboard". Modules are represented by numbers, so "laboratory" might be 332 and "x-ray" might be 497. That's only the beginning.

Modernization of code demands a high degree of precision. It is absolutely critical that the reengineered software performs in the same manner as the original. This requires two things: a rigorous approach to code refactoring based upon tried principles which retain the underlying logic; and a well-planned and consistent program of testing to ensure that logic is preserved and improvements do not in any way alter the function of the code. Testing is vital. Companies need to be certain that their modernized critical software will perform according to exact the same rules as the original.

Enormous amounts of COBOL code have been created and relied upon for decades. It really is the bedrock of early computing. But now, ancient COBOL systems are challenged because the original assumptions under which the code was written are no longer valid. COBOL was designed as a robust business language to handle batch oriented database operations in an ACID environment. Today, these vital systems, including financial, security, transportation, and healthcare solutions continue to run. But access is changed, processing requirements have changed, and the availability of coders to understand, maintain, and augment the systems diminishes year-by-year.

The recent successful and attempted attacks on critical government legacy information systems at the Office of Personal Management and the IRS have provided a stark reminder of just how vulnerable these older systems are. Commercial systems are not immune to criminal and foreign agencies either, and in fact, may have more to lose in the near term in lost revenue, IP theft, negative branding, and the scandals lingering often for years. Sony, Anthem, Banner Health, Home Depot and many others can testify to this fact.

Premera Blue Cross required the assessment, transformation and re-factoring of its existing Automated Document Assembly System (ADAS). ADAS was written in WANG COBOL and self generated WANG COBOL programs tailoring health care booklets for specific customer needs. TSRI was selected to assess, transform, and re-factor the WANG COBOL code, migrating the system into a C++ Windows NT environment with full functional equivalency.

Customer:  Premera Blue Cross Source & Target Language: COBOL to C++ Lines of Code: Nearly 50,000 Duration: 4 Months Services: Code Transformation, Automated Refactoring, Testing and Implementation Support, Transformation Blueprint®

Raytheon has partnered with TSRI on several successful modernization projects. Specifically, several years before the Patriot-Japan project was initiated, Raytheon was tasked with modernizing a set of Patriot Missile Simulation software. Following a formalized decision process, TSRI was selected as the best option for transforming the code from FORTRAN to C++, due to our unique fully automated transformation technology.  So, when Raytheon began modernizing Battalion Simulation Support System and its Preprocessor for the Japanese Patriot Missile system, TSRI was contacted and began work.  

Customer: Raytheon Source & Target Language: Fortran to C++ Lines of Code: 25,927 Duration:  10 months Services: Code Transformation from Multiple Legacy Languages, Automated Refactoring, Installation and Testing Support, Transformation Blueprint®​

Capita, a company based in England and Wales, determined that one of their important software assets called PRISM required modernization, including code transformation, platform migration, and database migration. Capita engaged TSRI, with their proven automated modernization services, to complete this project, which was finished in 3 months.

Customer: Capita Source & Target Language: BASIC to PL/SQL Lines of Code: 660,000 Duration:  3 months Services: Transformation Blueprint®, Automated Code Transformation, Automated Refactoring, Integration and Testing Support

BAE Systems received an award from South Korea's Defense Acquisition and Procurement Agency for a multi-year project to upgrade 134 Korean Air Force F-16 (KF16) fighters.  The upgrade included obsolescence management for the computers and operating systems for near real-time tactical data and voice information and including the Core operational flight programs: Advanced Mission Computer (AMC), Upgraded Central Interface Unit (UCIU), Cockpit Display Generator (CDG) and the Center Pedestal Display (CDP).  BAE Systems employed TSRI for their modernization services to modernize and document the Jovial source code to C++.

Customer: Bae Systems Source & Target Language: Jovial J73 to C++ Lines of Code: 340,000 Duration:  6 months Services: Code Transformation, Automated Refactoring, Installation and Testing Support, Transformation Blueprint®, Application Blueprint®

Stanley and Assoc. contracted TSRI to modernize the Battle Command Software - Advanced Field Artillery Tactical Data System (AFATDS).   This system is an integrated system that provides the Army, Navy, and Marine Corps automated fire support command, control and communications.  Prior to this modernization, AFATDS was written in legacy Ada-83.  The target code selected for the AFATDS modernization was Java.

Customer: Stanley and Assoc. and The US Army Source & Target Language: Ada to Java   Lines of Code: 5.1 million Duration:  10 months Services: Application Blueprint®, Automated Code Transformation, Transformation Blueprint®, Automated Refactoring, Engineering Support