An architecture vision offers an initial, broad sketch of both the baseline and the target architecture across the domains of business, information, data, application and technology, and gives the sponsor a means of persuading stakeholders of the capability's benefits. The key stakeholders and what concerns them, the enterprise's requirements and the architecture views that will meet them are identified; so are goals, strategic drivers and constraints. Architecture objectives are lined up with programme priorities; the capabilities and options for reaching the goals are understood; readiness for change is assessed; and the scope of baseline and target is set. The vision is then built from stakeholder concerns, capability requirements, scope, constraints and principles, and the architecture principles are confirmed and worked out in more detail. Risks arising from the change are identified, with a mitigation for each significant one. Approval is obtained through a concept business case, outline plans and a statement of architecture work, and the value propositions, goals and metrics of the target architecture are defined.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.