Application Assessment

 An application assessment both initiates a TSRI application modernization project, as well as completes the project for customers looking for detailed, cost-effective application documentation.

For customers wishing to retain their existing systems written in COBOL, PL/1, PowerBuilder, MUMPS, Ada, or any of more than 32+ languages, TSRI's code-level documentation enables your existing developers the ability to quickly and easily understand, maintain, and develop the application.

Many of TSRI's customers find that this documentation pays for itself within weeks or a few months, and TSRI offers a free sample of this solution in our Transformation Blueprint® Preview.

Application Assessment Services

During this phase, TSRI will set up JANUS Studio® to ingest and parse the source code. Once the code is parsed, we can then analyze the legacy system by transforming it into a model, according to standards set forth by the Object Management Group (OMG). This standard, a legacy Abstract Syntax Tree (AST), is an international modeling standard which TSRI helped author, and which allows TSRI to produce an Application Blueprint® (legacy "As-Is" documentation) for all source languages. The blueprint, an HTML-based detailed evaluation of the existing system’s UML design and architecture, provides clients with information that greatly reduces time spent maintaining and developing the legacy application (even during a full application modernization project).

For full transformation projects, the next step is an Internal and External Dependency Analysis, to identify internal and external interfaces and identify missing definitions. Then, we undertake a first-pass, Developer-Ready or “Baseline” Transformation and from that initial code transformation, the Baseline Transformation Blueprint® is generated to identify gaps in the transformation rule sets for generating the source languages. The Application Blueprint® and Baseline Transformation Blueprint® allow inspection of the baseline modernization and provide analytics and metrics for building a detailed understanding of the design and architecture of the target system. This is necessary to support planning of the Target Architecture Design, which will guide subsequent steps in the refinement of the modernization process.

(1) Setup

Modification of the TSRI JANUS Studio® toolset to be able to ingest and parse the customer’s source code and the generation of the baseline model of the application in the Intermediate Object Model (IOM). This IOM is augmented with semantic analyses including Control Flow, Data Flow, State Model, Cause–Effect and Class Models, Code Complexity Metrics, and Code Redundancy Clusters. The conclusion of this effort is the generation of an inventory report.

(2) Application Blueprint® (Legacy Documentation)

A detailed presentation of the projects source languages along with the structure and flow of the source code. As defined, the presentation includes Legacy Code and Design Metrics, Navigation Indices, Control Flow Diagrams, Structure Charts, Data Element Tables, State Machine Models, State Transition Tables, Cause Effect Graphs, and hyper-linked code as a web-based documentation that can be hosted on TSRI secure Cloud.

(3) Transformation (Developer-Ready)

The application is run through TSRI’s JANUS Studio® to generate a detailed initial or baseline transformation of the modernized application. The source code is automatically rewritten into the target code with all external system calls “stubbed out”.

(4) Baseline Transformation Blueprint®

A detailed presentation of the structure and flow of the modernized code that supports future code maintenance and any system restructuring and/or enhancement. As defined, the presentation includes Transformed Code and Design Metrics, Navigation Indices, Control Flow Diagrams, Structure Charts, Data Element Tables, State Machine Models, State Transition Tables, Cause Effect Graphs, and hyper-linked source and target code in HTML format hosted on TSRI’s secure Cloud. An example of a Transformation Blueprint® which models the “As-Is” and “To-Be” code and UML for side-by-side presentation is generated following transformation.

(5) Internal and External Dependency Analysis

This is a detailed analysis of all internal dependencies to aid in incremental deployment and testing of subsystems of the application.

(6) Target Architecture Design

Definition and development of a detailed plan for implementing the new system’s architecture. This design activity is conducted with the Client's architects and analysts. Because our language-neutral process allows for code modernization from any practical combination of source and target languages, the Client enjoys the freedom of deciding upon a modernized target architecture of their choice.


Stay up to date on Architecture-Driven Modernization: