When defining modular boundaries in IBM Refactoring Assistant, which data-related consideration is most critical?
Select an answer to reveal the explanation.
Short Explanation
When you define modular boundaries, you want each module to own its data stores and keep cross-module data sharing to a minimum. That keeps the boundary clean and stops shared state from creating tight coupling.
Full Explanation
Data ownership defines boundaries: each module owns its data stores and exposes data via APIs, minimizing shared state. Identical copybooks, CICS LINK versus COBOL CALL, and matching compiler optimization levels are consistency or performance choices, not the core data-ownership rule.