Which validation approach best matches the intent of comparing original and transformed implementations?
Select an answer to reveal the explanation.
Short Explanation
Run both implementations against the same inputs and compare outputs, data effects, and edge cases. That’s how you prove they behave the same way.
Full Explanation
The correct approach is running both implementations against the same inputs and comparing outputs, data effects, and edge-case behaviour. This directly tests behavioural equivalence because it checks what the implementations do, not how they look. Comparing the source code line by line for textual similarity is wrong because COBOL and Java syntax are fundamentally different, so textual similarity is meaningless here. Comparing the file sizes of the original and generated source is wrong because file size has no relationship to correctness. Confirming both implementations were written by the same team is wrong because authorship has no bearing on whether behaviour matches. For the exam, describe validation as executed comparison against shared inputs, not a static comparison of the code itself.