You can edit almost every page by Creating an account and confirming your email.

Functionality Equivalence Verification

From EverybodyWiki Bios & Wiki

Functionality Equivalence Verification is a technique used to prove that code modifications like code optimization, code restructure and dead code removal will not cause 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.


See also


This article "Functionality Equivalence Verification" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Functionality Equivalence Verification. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.