The optimization step in the current plan is described only as "improve the code," nothing more specific. What should optimization of transformed mainframe applications actually aim for?
Select an answer to reveal the explanation.
Short Explanation
You optimize transformed mainframe code for clarity and maintainability, not cleverness. Keep the required function exactly the same, because optimization isn't a licence to change behaviour.
Full Explanation
Optimization after transformation is scoped to clarity and maintainability of code whose required function is already fixed and validated; it is not a licence to change what the program does. The aim of improving clarity and maintainability without changing the required function is correct because the transformed program's behaviour has already been established and validated. Rewriting the code in the most concise or clever form the language allows, regardless of readability, is incorrect because cleverness that sacrifices readability works against maintainability, the goal it is meant to serve. Adding new functionality that the original COBOL program never had is incorrect because adding functionality goes beyond optimization and reopens equivalence questions the transformation already settled. Adjusting the required behaviour so it is easier to implement in Java is incorrect because behaviour is fixed by the business requirement, not adjusted to suit the target language. For the exam, keep optimization scoped to clarity and maintainability with function held constant.