Jovial to C++

Modernizations

Case Studies

Boeing required a new version of a mission-critical avionics software package for its Advanced Light Weight Combat Aircraft. TSRI successfully converted the J73 JOVIAL into C++, delivering Boeing an accurate error free avionics package which compiled and linked cleanly.

In support of the MILSTAR sattelite modernization effort, TRW contracted TSRI to assess and transform 143,000 lines of JOVIAL code. The automatically generated C++ upgrade of MILSTAR's primary control system was launched in 2004 and now provides enhanced communications for the United States Armed Forces.

Computer Sciences Corp. (CSC) won a down select as a subcontractor to Integral Systems, Inc. (ISYS) following a TSRI to demonstration of its automated J73 JOVIAL to C++ assessment and transformation capabilities. CSC then used TSRI's comprehensive JOVIAL documentation to identify the MILSTAR Mission Unique Software, allowing system integration.

Using a module from the Ballistic Missle Early Warning System (BMEWS), TRW and TSRI performed an early demonstration of automated software re-engineering capabilities. The transformation of J3 JOVIAL into C++ established the initial framework for TSRI's automated tools and services, including automated assessment, transformation, re-factoring and web-enablement.

The USAF completed a year long manual modernization of a 50,000 line JOVIAL module from the F-16 cockpit. TSRI's automated transformation of the same module attained C++ code of comparable quality to the manually converted code. The Air Force was further impressed when a single TSRI engineer automatically transformed a 2nd similar JOVIAL module into C++ in only 15 minutes.

TSRI's approach to Jovial system modernization permits gradual integrated steps within a model-driven methodology. Each step adds to a repository of knowledge about the application portfolio and guides subsequent steps in the modernization process. TSRI's automated processes insure consistent code integrity so manual intervention is seldom if ever used. Human decision-making is introduced only when necessary to guide the automated processes.

TSRI legacy system modernization begins by applying transformation rules to generate a platform independent model from the legacy application source code. TSRI calls this the Intermediate Object Model (IOM™). Platform specific rules are then applied to the IOM™ to derive the modernized application's source code. Any changes to the model-driven modernization process are accomplished by modifying rules or models. The software tool set developed by TSRI containing these models, rules, and automated processes is called JANUS™.

UML documentation can be generated to support multiple views of all modernization products. Code models and UML design can be interchanged using XML Metadata Interchange (XMI) with other vendors' tools. JANUS™ traces all rules to every object model touched or created during the transformation process. TSRI solves the O(N-squared) language transformation combinatorial problem by transforming all legacy source languages into the IOM™, a common platform and language neutral model. From the IOM™ multiple modern object oriented target languages can be generated for platform specific targets. The IOM™ consists of a set of language constructs common to all languages. By using the IOM™ as an intermediate model, the inherently O(N-squared) language transformation problem is reduced to an O(N) problem and model driven processes for assessment, analysis, metrics, documentation and re-factoring are reduced to O(1) problems. These are consistently and uniformly solved for all languages and platforms within the IOM™.

As an Object Management Group (OMG) Platform Member, TSRI is a leading contributor to the Architecture Driven Modernization Task Force (ADM TF) where TSRI seeks to advance OMG standards supporting best practices. TSRI's JANUS™ technology tools and services adhere to the OMG ADM TF standards and recommended practices.