Functionality Equivalence Verification
An editor has nominated this article for deletion. You are welcome to participate in the deletion discussion, which will decide whether or not to retain it. |
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Functionality Equivalence Verification is a technique used to prove that code modifications like code optimization, code restructure and dead code removal will not cause for any functionality change. This heuristic approach to testing functionality differs from both regression tests and sanity tests.
When functional equivalence has been reached and properly verified, the migrated application functions exactly in the same manner that the original application behaved—with the same functionalities, properties, and under the same conditions. Usually, reaching functional equivalence is a critical first step of a software modernization project. After an application's code has been successfully converted, generally using automated techniques, developers can proceed to add more functionality, and take advantage of the new code's characteristics to further improve upon and streamline the migrated application's existing functionality.