Why should mainframe subject-matter experts stay involved after project kickoff rather than being excluded once requirements are gathered?
Select an answer to reveal the explanation.
Short Explanation
You need mainframe SMEs around after kickoff because they’re the only ones who can confirm the COBOL’s real business rules. They validate generated code and proposed boundaries as the work progresses.
Full Explanation
Mainframe subject-matter experts should stay involved after project kickoff because business rules embedded in COBOL are rarely fully documented, and SMEs are the ones who can confirm that a transformed module still behaves the way the business needs. Their input is needed throughout, not just at kickoff, to validate that generated code and proposed boundaries reflect real business rules. The option saying they must write the Java code themselves is incorrect because SMEs contribute domain knowledge, not necessarily Java implementation. The option saying they are needed only to sign the initial project charter is incorrect because a signature at kickoff does not substitute for ongoing validation. The option saying their role is to approve the choice of development tooling and nothing else is incorrect because tooling choice is a technical decision separate from their domain expertise. For the exam, keep SMEs engaged across the project, not just during initial discovery.