|
|
|
|
|
Sometimes our clients will make modifications to application programs while they are in the process of being converted. Such changes are difficult to control and can, if not precisely identified and incorporated into the converted program, greatly complicate parallel testing. Conversion Migration solves this problem by identifying the differences between the program as translated and the program as modified. The modifications can then be incorporated into the converted program. The emphasis on thorough unit testing often reduces costly system and parallel testing time. In short, Conversion Migration compresses the overall time needed for migration and minimizes the impact on your production staff and equipment. This is accomplished while improving the quality of the migration results using tools to measure the code tested and through automatic comparison of data.We make sure that the migrated programs will produce output functionally equivalent to that produced by the original programs.
Migration Implementation involves the following steps:
|
Conversion Migration produces a readable comparison of the output of the transformed program with that of the original program, pinpointing any discrepancies. The format permits to determine the exact position of mismatches and discerns error patterns at a glance. |
IMPLEMENTATION PHASE |
STAGES | TASKS | DELIVERY | TOOLS | ACTORS |
|
Incorporate Identified Modifications | Conversion Migration |
Project
leader |
||
Simulation |
Parallel Testing |
|
|
Project
leader |
|
Implementation |
Live Production Data Transfer |
|
Conversion Migration |
Project leader Project Leader CLIENT Application Manager CLIENT |
|
Final Delivery |
Final Validation |
Final Delivery Report |
Project Leader CLIENT |
Conversion migration project phases.
 |
 |
 |
 |
 |
 |
Integrating the programs and preparing
job control statements for system testing.
