As a project lead formalises use of the rewrite workflow for a governed project, which practice should be written into the standard operating procedure?
Select an answer to reveal the explanation.
Short Explanation
Put the review step in the SOP so it happens every time, not just when someone remembers. You need to verify functional equivalence for every generated Java module before you accept it.
Full Explanation
The correct practice is requiring every generated Java module to be reviewed for functional equivalence with its source COBOL before acceptance. A governed procedure formalises what should already be true of every module: a review for functional equivalence before acceptance, not an optional extra.
The practice of accepting generated modules automatically whenever the workflow reports that generation completed without an error is incorrect because a completion status from the workflow reflects whether generation finished, not whether the result is correct.
The practice of requiring review only for modules flagged by the workflow as low confidence is incorrect because confidence flags from the tool are not a substitute for actually verifying equivalence on every module, including ones the tool rates highly.
The practice of reviewing by confirming that the generated Java's comments match the original COBOL's comments is incorrect because matching comments checks documentation, not the business logic the module actually executes.
For the exam, a governed procedure should require equivalence review on every generated module, without exceptions.