Natural / Adabas Conversion
Like so many other organizations today, the FAA wishes to reduce application hosting costs. As one of their initiatives, the FAA hired Trinity Millennium Group to modernize their Natural / Adabas applications. This effort involved millions of lines of source code, conversion to a Windows .Net platform, and migration of Adabas indexed data files to a relational database.
A critical feature of the Automation-Enabled Modernization (AEM) is the combined use of automation with software engineering best practices. Manual modernization efforts are slow, expensive and error-prone, while fully automated conversion results in simplistic, poorly architected applications that are difficult and expensive to maintain. Trinity provides the best of both worlds – our modernization consultants utilize our extensive library of automated conversion tools, and apply the human touch for critical design and re-factoring tasks. The following table shows how this approach provided a fast, cost-effective migration to a high-quality result for the FAA.
FROM
|
Conversion |
TO |
Natural procedural code & global data structures
|
90% Automation
10% Manual code polish
|
VB.Net code & SQL Server stored procedures
|
Natural screen maps
|
100% Automation
|
ASP.Net screen definitions
|
Adabas file definitions
|
Automated DDL generation with predefined design parameters, followed by manual DDL polishing
|
SQL Server database table definitions
|
JCL
|
100% Automation |
VBScript
|
Batch processes defined in Control-M
|
Manual integration of Tidal with converted application
|
Batch processes defined in Tidal Scheduler
|
Generated code, including manual re-factoring and polishing
|
Automated test cases for unit, integration and regression testing
|
Tested and debugged code delivered to the client
|
Trinity can provide the same results whether you wish to migrate to .Net, Java, or some other platform.
Contact us today to find out how quickly and cost-effectively
we can modernize your Natural / Adabas applications
|
