Phase A: Architecture Vision and scope

Show the intended outcome

Phase A turns an initial request into scoped architecture work. It identifies stakeholders, their concerns, objectives, scope, and required resources. The Architecture Vision describes the intended outcome and its value at a high level. It makes change understandable without detailing the entire target design.

The vision must be realistic enough to support a decision. Examining relevant domains, constraints, and team capability helps avoid approval of an ambition that cannot be achieved. Descriptions and requirements often begin provisionally and are elaborated during subsequent phases.

Choose the work boundaries

Scope includes the breadth of the enterprise being studied, depth of detail, time horizon, and domains covered. It considers upstream architectures and decisions. Stakeholders should share an understanding of exclusions, uncertainty, and expected results. The Statement of Architecture Work then formalizes commitments and enables approval of the work.

• Describe value, major changes, and feasibility.
• Explicitly bound the domains and amount of detail.
• Check agreement on scope before elaborating the design.