Enterprise Architecture Research Summary (20) -- Architecture Vision stage of TOGAF architecture development method (ADM)

Document directory

• Architecture Vision 1.2)

Architecture Vision 1.2)

Stages of Enterprise Architecture Development Method-Architecture Vision

1.2.1 Objectives

• Ensure that the progress of the architecture development cycle is recognized and supported by the enterprise management, and the necessary management lines are supported and recognized.
• Define and organize the architecture development cycle under the overall background of the architecture framework clearly defined in the preparatory stage.
• Verify the business principles, business objectives, strategic business driving force of the Organization, and the key performance indicators (KPIs) of the enterprise architecture ).
• Define the scope of the baseline architecture, and specify the components included and the priority of the components.
• Define stakeholders and their concerns and objectives
• Define the key business needs to be addressed by the architecture and the constraints that must be addressed
• Clarify the Architecture Vision and customize value propositions. These value propositions are used to explain responses to those needs and constraints.
• Create a comprehensive plan to indicate the planning progress, resources, finance, communication, risks, constraints, assumptions and dependencies, it should also be suitable for the enterprise's project management framework (PRINCE2 or PMBOK)
• Ensure formal approval is executed
• Understanding the interaction with other parallel enterprise architecture development cycles

1.2.2 Method

The Architecture Vision phase starts when the architecture organization receives the architecture work requirements from the architecture sponsor organization. In this phase, the Organization needs to define the scope of architecture work and the constraints to be addressed based on the assessment of current resources and their availability. These constraints are generally derived from the business principles and Architecture Principles formulated during the preparation phase. In the Architecture Vision phase, the Organization needs to confirm that these principles exist and are clear. If not, these principles need to be clearly defined at this stage. In addition, the methods involved in this phase also include:

Create Architecture Vision

The Architecture Vision is an excellent tool for architecture sponsors to promote their capabilities to stakeholders and decision makers. It describes how new capabilities meet the strategic and business objectives of the Organization, and how to solve the problems that stakeholders are concerned about when these capabilities are implemented. Therefore, the creation of the architecture vision is to clarify the objectives of the architecture and clarify how to achieve these goals through architecture development. The architecture vision gives a first impression on the baseline and target architecture at a very high level, this description should cover the four layers of business, Data, application and technology (this is just a brief description, and the specific content of these layers will be gradually refined in the subsequent stages ).

Once the Architecture Vision is defined and recorded in the architecture statement of work, consensus on the architecture vision among stakeholders will become a top priority, because without this consensus, then there is no way to talk about whether the final architecture can be accepted by the Organization. This consensus was achieved through the signing of the Architecture statement of work by the sponsors.

Business scenario

The business scenario method is used to identify and clarify implicit architecture requirements and business requirements hidden in new business capabilities (to meet the needs of key business driving forces. This technology is implemented through a loop iteration and described in different levels of detail for each layered decomposition component of the Business architecture.

1.2.3 Input and Output

The input materials required in the current phase and the deliverables output in this phase are summarized as follows:

Input Inbound	References	Architecture references
	Non-Intrusive Input	Architecture work requirements
		Business objectives, principles and driving force
	Intrusive Input	Enterprise Architecture organization model, including: Scope of affected organizations Maturity evaluation, gaps and solutions Roles and responsibilities of the Architecture Team Architecture work constraints Reuse requirements BUDGET REQUIREMENTS Change Request Governance and support policies
		Customized architecture frameworks, including: Customized architecture Method Customized architecture content (deliverables and products) Architecture Principles, including business principles (if exists beforehand) Configuration and deployment tools
		Architecture resource library with content already available
Input Output	Approved architecture statement of work, including: Scope and constraints Architecture Work Plan Roles and responsibilities Risks and mitigation measures Performance evaluation of work products Business Cases and KPI indicators
	Description of improved business objectives, principles and driving force
	Architecture Principles
	Capability Evaluation
	Customized architecture frameworks, including: Customized architecture Method Customized architecture content (deliverables and products) Configuration and deployment tools
	Architecture Vision, including: Improved requirements of key high-level stakeholders Baseline Service Architecture version 0.1 Baseline Technical Architecture version 0.1 Baseline data architecture version 0.1 Baseline application architecture version 0.1 Target Business Architecture version 0.1 Target Technical Architecture version 0.1 Target Data Architecture version 0.1 Target application architecture version 0.1
	Communication Plan
	Added content included in the architecture resource library

Step 1.2.4

The steps to be performed in the current phase are summarized as follows:

• Create architecture project
• Identify stakeholders, points of interest, and business needs
• Confirm and describe business objectives, drivers and constraints
• Evaluate business capability
• Evaluate Business Transformation preparation
• Definition range
• Confirm and elaborate on architecture principles, including business principles
• Development Architecture Vision
• Define the value proposition and main performance indicators of the target architecture
• Clarify business transformation risks and mitigation measures
• Develop Enterprise Architecture plans and architecture statement of work and ensure approval