Architecture Vision

The Architecture Vision is created in Phase A. It provides a high-level summary of the changes to the enterprise - that will follow the successful deployment of the Target Architecture. The purpose of the vision is to agree at the outset the desired outcome of the architecture. Architects can then focus on the details necessary to validate the feasibility and other specific details.

The Architecture Vision provides a summary of the full Architecture Definition - that supports any stakeholder communication. Business scenarios are an appropriate and important technique that can be used as part of the process in developing an Architecture Vision document.

TOGAF recommends the following contents for the Architecture Vision

  • Problem description
  • Stakeholders and their concerns
  • List of issues/scenarios to be addressed
  • Objective of the Statement of Architecture Work
  • Summary views necessary for the Request for Architecture Work
  • The high-level Business, Application, Data, and Technology Architectures
  • Mapped requirements
  • Reference to Draft Architecture Definition Document

There is a difference between the Statement of Architecture Work and the Architecture Vision. The Architecture Vision describes the future dream, and the Statement of Architecture Work details the practical implementation aspects.