Application Analysis

The AveriSource Runner is the workhorse behind our ability to efficiently process large applications. It contains our legacy language code construct libraries and develops all of the software artifacts that populate our metadata database. A true learning engine, it can be easily updated for new languages and constructs, so its capabilities continually improve.

Complete Repository

AveriSource first provides missing file references to confirm a complete application codebase will be analyzed.

Expand Code

Externally referenced code, such as copybooks, is pulled into each program and catalogued for future reference.

Parse Code

The AveriSource Runner parses the code and identifies and incorporates any unique code constructs before proceeding.

Categorize Code

All aspects of the code are traced and categorized so they can be referenced accordingly and used to develop business rule reports.

Generate Metadata Database

With all code parsed and categorized, a master database is created.

Create iSAT

The iSAT reporting database is generated from the metadata database and connected to the iSAT front-end through the service layer.

Test

Automated tests ensure completeness and accuracy.

Code Transformation

The software artifacts developed by the AveriSource Runner are a key input to the AveriSource Autotransform engine. References, Definitions and Tags are each used to provide context around the actions the Autotransform engine performs in each iteration.

Create iSAT

Application analysis information is an integral input to the code transformation process.

Architect

It is critical to confirm end-state architecture and database structure before transforming code.

Iteration 1

The first iteration generally requires limited client/partner input and can follow AveriSource’s standard transformation routines.

Iteration 2

Second iterations generally move the code towards an object-oriented structure.

Iteration 3

Database calls can be transformed to reflect modern data access objects.

Iteration 4

End-state frameworks such as Hibernate or Spring can be implemented.

Iteration N

Additional iterations can take many forms and are often governed by the ROI.