Question 170
During an Architecture Development Method planning meeting at fictional Brookfield Digital, the team reports: An enterprise project closes requirement records after Phase A despite new constraints appearing during Phase C. What distinction in TOGAF architecture work best accounts for the problem?
Explanation
Correct Answer
Requirements Management is ongoing and feeds and receives information from ADM phases. Applying this distinction points to the response: Operate Requirements Management as a central ongoing process supplying relevant requirements to every ADM phase. The evidence to seek is: Requirements changes are considered continuously across phase work rather than disappearing between handoffs.
Incorrect Answers
The offered principle describes: Architecture scoping matches architectural work to the intended problem and decision horizon. The situation in this question instead depends on: Requirements Management is ongoing and feeds and receives information from ADM phases. These are different technical conditions.
This alternative is valid when phase H provides ongoing architecture change management, not first-time Architecture Vision approval. The facts here establish a different controlling reason: Requirements Management is ongoing and feeds and receives information from ADM phases.
“Phase E identifies implementation opportunities and initial transition approaches rather than executing the migration” reflects the mechanism: Phase E identifies implementation opportunities and initial transition approaches rather than executing the migration. The actual reported symptoms are better explained by: Requirements Management is ongoing and feeds and receives information from ADM phases.