Exam OG0-091 topic 1 question 133 discussion

7.2.2: Architecture Vision describes how the new capability will meet the business goals and strategic objectives and address the stakeholder concerns when implemented. 7.5 > Outputs: Architecture project description and scope.

32.2.8 Architecture Vision Purpose The Architecture Vision is created early on in the ADM cycle. It provides a summary of the changes to the enterprise that will accrue from successful deployment of the Target Architecture. The purpose of the Architecture Vision is to provide key stakeholders with a formally agreed outcome. Early agreement on the outcome enables the architects to focus on the detail necessary to validate feasibility. Providing an Architecture Vision also supports stakeholder communication by providing a summary version of the full Architecture Definition.

The best description of the Architecture Vision document is: C. A description of the scope and approach for completion of the architecture project. The Architecture Vision document in the TOGAF ADM (Architecture Development Method) is created during the initial phase of the architecture development process. It provides a high-level description of the desired future state of the architecture and outlines the scope, objectives, and approach for completing the architecture project. The Architecture Vision document sets the direction and establishes the foundation for the subsequent phases of the architecture development process. It helps stakeholders understand the purpose and goals of the architecture project and provides a roadmap for achieving the desired outcomes.

32.2.8 Architecture Vision Typical contents of an Architecture Vision are: 1. Problem description: - "Stakeholders and their concerns". - List of issues/scenarios to be addressed. 2. Objective of the Statement of Architecture Work. 3. Summary views necessary for the Request for Architecture Work and the Version 0.1 Business, Application, Data, and Technology Architectures created; typically including: - Value Chain diagram. - Solution Concept diagram. 3. Mapped requirements. 4. Reference to Draft Architecture Definition Document.

https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap05.html 6.5.2 Creating the Architecture Vision The Architecture Vision provides the sponsor with a key tool to sell the benefits of the proposed capability to stakeholders and decision-makers within the enterprise. Architecture Vision describes how the new capability will meet the business goals and strategic objectives and address the stakeholder concerns when implemented. https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap32.html 32.2.8 Architecture Vision The Architecture Vision is created early on in the ADM cycle. It provides a summary of the changes to the enterprise that will accrue from successful deployment of the Target Architecture. The purpose of the Architecture Vision is to provide key stakeholders with a formally agreed outcome. Early agreement on the outcome enables the architects to focus on the detail necessary to validate feasibility. Providing an Architecture Vision also supports stakeholder communication by providing a summary version of the full Architecture Definition.

Architecture Vision describes how the new capability will meet the business goals and strategic objectives and address the stakeholder concerns when implemented.