Key takeaways
- A request starts scoping; it is not a Target Architecture.
- Drivers connect the initiative to enterprise needs.
- The Request and Statement of Architecture Work serve different purposes.
An explicit trigger
Business principles, objectives, and drivers provide the context for work. A driver may be a regulatory constraint, market change, operational problem, or strategic direction. The Request for Architecture Work formalizes a request to initiate an architecture cycle or piece of work. It expresses the initial need without claiming that the complete solution has already been defined.
The request may arise from capability preparation, a change identified in Phase H, or migration-related work. Knowing its origin helps establish urgency and connections with existing activities. The request must be considered within enterprise governance and priorities.
Information supporting initial scope
Useful information includes the sponsor, mission, objectives, strategic direction, budget, resources, constraints, and a description of the current situation. These help determine what needs study and initial boundaries. The Request does not replace the Statement of Architecture Work: Phase A subsequently defines the vision, scope, and commitments of the proposed work.
- Explain the problem and expected value.
- Identify who sponsors the request and who can authorize it.
- Record assumptions that remain uncertain.
TERMS TO KNOW
The terms, in context.
- Driver
- Factor motivating or requiring change.
- Request for Architecture Work
- Formal request to initiate architecture work.