The primary reason is that most projects from other vendors focus on the changes required, and not on the testing required to assure that the work was done accurately. Unfortunately, testing is not a well-implemented discipline. If adequate test time and resources are not planned into the project, it is at risk before it starts. The Forecross methodology and supporting technology is designed to absolutely minimize these risks, while increasing accuracy in the result and minimizing costs. Unique in the industry, our methodology mitigates risk by automation of both the conversion and the highest cost phases of testing.
Automation introduces consistency, reduces costs, and improves predictability and accuracy.
Manual efforts produce the opposite. These effects become more pronounced as the size of the project increases. The basic methodology is to capture all of the data input to and output from a program during execution prior to migration, including the logic path taken through the program. The captured input data are then replayed into the migrated program and the output data from the replay execution automatically compared to the output data from the pre-migrated program. If there are differences, a report is produced to assist a programmer in quickly identifying whether the discrepancy represents a problem.