Question 600
At fictional Summit Square Mobility, the following issue emerges in a transformation risk assessment: A railway organization knows it wants better incident handling but has no shared scenario describing roles, triggers, and success. What distinction in TOGAF architecture work best accounts for the problem?
Explanation
Correct Answer
Business scenarios make stakeholder needs and constraints actionable for architecture work. Applying this distinction points to the response: Formulate a business scenario with concrete actors, events, business requirements, and success measures. The evidence to seek is: Architecture requirements have clear links to a validated business scenario and its desired outcomes. Applied here, the relevant facts are: A railway organization knows it wants better incident handling but has no shared scenario describing roles, triggers, and success.
Incorrect Answers
This alternative is valid when good Architecture Principles should guide decisions clearly without being needlessly ambiguous or contradictory. The facts here establish a different controlling reason: Business scenarios make stakeholder needs and constraints actionable for architecture work.
“Interoperability includes common meaning and coordinated behavior in addition to compatible interfaces” reflects the mechanism: Interoperability includes common meaning and coordinated behavior in addition to compatible interfaces. The actual reported symptoms are better explained by: Business scenarios make stakeholder needs and constraints actionable for architecture work.
This alternative is valid when architecture risk management spans decisions and implementation rather than a one-time end-stage checklist. The facts here establish a different controlling reason: Business scenarios make stakeholder needs and constraints actionable for architecture work.