What condition discovered during ADDI analysis should trigger an Optimize phase before Refactoring begins?
Select an answer to reveal the explanation.
Short Explanation
If ADDI analysis shows significant dead code, duplicated logic, or high-complexity programs, you optimize first. Otherwise, you just modernize bloat into a new platform. That’s how you keep scope and quality under control.
Full Explanation
Significant dead code, duplicated logic, or high-complexity programs should trigger Optimize first, because transforming bloated COBOL directly into Java perpetuates quality problems and inflates scope. Line count alone, embedded SQL, or missing CICS RESP checks do not by themselves require prior optimization.