ATERAS

automated solutions for legacy migration and modernization™

Application Conversion

The Application Conversion phase begins immediately after the assessment phase. All components can be re-named for use in the new target environment. The new applications will be generated in their new languages and will execute against the new relational database structures.

The Application Software Conversion and the Database and Data Conversion phases take place concurrently. It is recommended that the database administration teams be involved in the Database and Data Conversion thread, and that the application teams be involved in the Application Conversion thread.

This conversion phase includes application pre-conversion setup, application conversion and iterations, and testing support at several levels. The primary deliverables are those that comprise the converted application software.


 

The Application Conversion phase begins immediately after the Assessment phase. New applications are generated in the target languages and execute against the new relational database structures. If necessary, components are re-named for use in the new target environment.

Overview

The application software conversion and the database and data conversion phases take place concurrently. It is recommended that the database administration teams be involved in the Database and Data Conversion, and that the application teams be involved in the Application Conversion.

Process

This conversion phase is an iterative process that includes application pre-conversion setup and application conversion. Testing support is provided at multiple levels.

Deliverables

ATERAS packages and delivers the converted applications ready for installation, compilation and testing.

Tasks

ATERAS performs the following high-level tasks during the application conversion phase:

  • Provide JCL to collect software from all source code repositories
  • Define and implement a secure customer database within DB-Shuttle™
  • Import all source code from the collection files into the secure database
  • Provide reports on components referenced and not referenced in Logical Applications
  • Provide detailed and summary reports of collected components
  • Review and understand renaming and rules definitions submitted by customer teams
  • Enter the renaming/processing rules defined in the Conversion Workbook into DB-Shuttle
  • Generate reports of proposed renaming and conversion rules
  • Define a secure FTP site for delivery of Converted Components
  • Generate Converted Components
  • Perform preliminary compiles of converted code in the ATERAS environment
  • Deliver the first pass of the Supplier Deliverables to the FTP site
  • Conduct a walkthrough of the Software Installation process and target architecture
  • Assist customer teams with installation of new software into target environment
  • Provide new and revised components as required to resolve any conversion issues
  • Conduct maintenance training for converted applications and databases.

Reports

The ATERAS Conversion produces the following reports:

  • Converted Online Detail Report
  • Converted Common Code Detail Report
  • Converted Dictionary Detail Report
  • Converted Maps Detail Report
  • Converted Edit Components Detail Report
  • Software Delivery by Component
  • Software Delivery by Type
  • Software Delivery for COBOL
  • Software Delivery for JCL
  • Language-specific detail analysis reports as required