The Statement of Architecture Work is a key output of the Architecture Vision (Phase A) and a primary input to the Business Architecture (Phase B). This document defines the scope, constraints, plan, and deliverables for an architecture project. According to the TOGAF® Standard, it is intended to be the basis for a formal agreement or contract between the sponsoring organization (the consumer) and the architecture organization (the supplier) that outlines precisely what architecture work will be undertaken.

A. Architecture Vision: This document describes the high-level, aspirational future state of the enterprise but does not detail the scope of work, schedule, or deliverables required for a contractual agreement.

B. Business principles, goals, and drivers: These are foundational elements that guide and constrain the architecture work; they are inputs to the process, not the contractual document defining the engagement.

D. Architecture Roadmap: This is a major output of the ADM, developed across several phases (including B, C, D, E, and F). It outlines the transition plan, not the initial agreement to perform the work.

1. The Open Group. (2018). The TOGAF® Standard

Version 9.2. Van Haren Publishing.

Section 7.3

Inputs to Phase B: Lists "Statement of Architecture Work" as a key architectural input from Phase A.

Section 36.2.20

Statement of Architecture Work: "The Statement of Architecture Work is a statement of the work required to develop an architecture... It will form the basis for any contractual agreements."

Figure 6-1

The ADM Cycle: Shows the Statement of Architecture Work as a major output of Phase A

which then feeds into subsequent phases.

A value network is a business analysis model that focuses on the complex web of relationships and value exchanges among various participants, such as customers, suppliers, partners, and other stakeholders. Its primary concern is to identify these actors (or nodes) and understand how they collaborate and interact to co-create value. Unlike linear models, it visualizes the multi-directional flow of both tangible assets (money, goods) and intangible assets (information, knowledge, reputation) between the involved parties, making it the approach most centered on the participants themselves.

B. Value chains: This model focuses on the linear sequence of internal activities a single firm performs to deliver a product, not the broader network of external participants.

C. Value streams: This approach maps the end-to-end sequence of activities required to deliver value to a customer, emphasizing process flow and efficiency over identifying the participants.

D. Lean value streams: This is a specific application of value stream mapping that is primarily concerned with identifying and eliminating waste (muda) within the process flow.

1. The Open Group Standard

The Open Agile Architecture™ Standard (C228)

January 2022. In Section 3.1.28

"Definitions"

a Value Network is explicitly defined as: "A set of roles

actors

and stakeholders and the value exchanges between them." This definition directly highlights the focus on participants.

2. The Open Group Guide

Value Streams (G178)

October 2017. Section 2.3

"Value Network"

states: "A value network is a set of connections between organizations and/or individuals interacting with each other to benefit the entire group... A value network describes the social and technical resources within and between businesses." This reinforces the focus on the interacting participants.

3. The Open Group Guide

Value Streams (G178)

October 2017. In contrast

Section 2.1

"Value Stream"

defines it as a concept that "denotes the flow of value in the context of an end-to-end perspective

" emphasizing the flow of activities rather than the participants.

The image provided illustrates the Business Model Canvas, a strategic management and entrepreneurial tool. It allows you to describe, design, challenge, invent, and pivot your business model. The canvas is composed of nine distinct building blocks: Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, and Cost Structure. The specific layout and terminology shown in the diagram are the defining characteristics of this widely adopted framework, originally proposed by Alexander Osterwalder and Yves Pigneur.

B. The Four Box Framework is a simpler model focusing on only four components: Customer Value Proposition, Profit Formula, Key Resources, and Key Processes.

C. The Business Model Cube is a more complex, three-dimensional conceptual model used for analyzing and classifying business models, not the 2D canvas shown.

D. The Business Model Innovation factory refers to a conceptual process or environment for systematically generating and testing new business models, not a specific visual template.

1. Osterwalder

A.

& Pigneur

Y. (2010). Business Model Generation: A Handbook for Visionaries

Game Changers

and Challengers. John Wiley & Sons. The nine building blocks are defined and illustrated on pages 15-44. The full canvas diagram is presented on page 44.

2. The Open Group. (2018). The TOGAF® Standard

Version 9.2. Van Haren Publishing. In Part II: Architecture Development Method (ADM)

Section 8.2.3 "Business Models

" the standard notes: "A popular technique for describing a business model is the Business Model Canvas." This confirms its relevance within The Open Group's frameworks.

3. Blank

S. (2013). Why the Lean Start-Up Changes Everything. Harvard Business Review

91(5)

63-72. This article describes the Business Model Canvas as the tool that precedes business plan development in the lean start-up methodology

stating

"The business model canvas is a diagram of how a company creates value for itself and its customers." (p. 66).

The primary purpose of mapping business capabilities to value stream stages is to establish a clear line of sight between what an organization does (its capabilities) and how it delivers value to stakeholders (its value streams). This cross-mapping is a critical analytical technique that reveals which capabilities are essential to execute each stage of a value stream. By understanding these dependencies, architects and planners can identify and prioritize the most critical capabilities for investment, improvement, or transformation, ensuring that resources are focused on the areas that most directly impact value creation.

A. This describes a fundamental characteristic of a business capability (being independent of organizational structure), not the purpose of mapping it to a value stream.

C. This describes a service-oriented view of the business, which is a different architectural perspective from the specific goal of capability-to-value-stream mapping.

D. This describes the purpose of creating a business capability map itself (i.e., organizing capabilities), not the specific act of cross-mapping them to value streams.

1. The Open Group

TOGAF® Series Guide: Value Streams (Document No. G178)

January 2017.

Section 4.4

"Value Stream and Business Capability Cross-Mapping

" Page 13: "Cross-mapping value streams to business capabilities identifies which capabilities the business needs to support a given value stream. This cross-mapping provides the context for defining which business capabilities are most critical to the business..." This directly supports the chosen answer.

2. The Open Group

TOGAF® Series Guide: Business Capabilities

2nd Edition (Document No. G211)

October 2021.

Section 4.3

"Using Business Capabilities with Other Business Architecture Disciplines

" Page 16: "Mapping business capabilities to value streams helps an organization understand what it needs to be able to do to deliver value to its stakeholders. This provides the basis for IT investment decisions by showing which business capabilities are most important."

3. The Open Group

The TOGAF® Standard

10th Edition

Content Framework

April 2022.

Section 30.3.2

"Business Architecture Catalog

Diagram

and Matrix Content

" Value Stream/Capability Matrix: The description of this matrix states its purpose is to show "the relationship between value streams and business capabilities" and is used to "determine the business capabilities required to support a value stream." This aligns with identifying critical capabilities for value delivery.

A business capability is officially defined as a particular ability or capacity that a business may possess or exchange to achieve a specific purpose or outcome. It represents what a business does at its core, abstracting away from the how (i.e., the specific processes, people, or IT systems). This definition focuses on the ability to perform an action to produce a result, which is precisely what option A describes. It is a stable, foundational building block for business architecture planning.

B. This describes a solution architecture or a design approach, which details how a capability might be realized, not the capability itself.

C. This is the definition of a business process or a value stream, which are the operational steps that execute or realize a capability.

D. This describes a business goal, objective, or principle. These are statements of intent that a capability helps to achieve, not the ability itself.

1. The Open Group. (2019). TOGAF® Series Guide: Business Capabilities (G189). Section 2.1

Page 3. "A business capability is a particular ability that a business may possess or exchange to achieve a specific purpose or outcome."

2. The Open Group. (2018). The TOGAF® Standard

Version 9.2 (C182). Part I

Chapter 3

Definitions. "Capability: An ability that an organization

person

or system possesses."

3. The Open Group. (2018). The TOGAF® Standard

Version 9.2 (C182). Part II

Section 8.3.2

Business Capabilities. "Business capabilities describe the abilities of an enterprise to do something."

A TOGAF Business Scenario is a formal technique used to identify, understand, and document a business problem, the environment in which it exists, and the desired outcomes. It serves as a critical tool to derive business requirements for the architecture by articulating the problem and its context in both business terms (e.g., processes, actors, objectives) and architectural terms (e.g., required capabilities, constraints). This ensures that the resulting architecture is directly aligned with solving the specific business problem.

A. This describes business modeling in general. A Business Scenario is a specific technique that uses models but is not the act of constructing them itself.

B. This describes business process management or performance assurance, which is a different discipline. A Business Scenario helps define what is required, not ensure its delivery.

D. This is the definition of a TOGAF Viewpoint. A Viewpoint defines the conventions for constructing a view, whereas a Business Scenario is a problem-elucidation technique.

1. The Open Group

"TOGAF® Standard

10th Edition

" Van Haren Publishing

2022. In Part III

Chapter 23.1

"Introduction

" it states: "A Business Scenario describes a business problem

the business and technology environment in which it occurs

and the desired outcome of a proper solution." This directly supports the chosen answer.

2. The Open Group

"TOGAF® Standard

10th Edition

" Van Haren Publishing

2022. In Part II

Chapter 5.4.2

"Business Scenarios

" it is described as a technique to "help identify and understand business needs

and thereby to derive the business requirements that the architecture development has to address

" reinforcing its role in describing a business problem.

3. The Open Group

"TOGAF® Standard

10th Edition

" Van Haren Publishing

2022. In Part IV

Chapter 32.2.23

"Viewpoint

" a viewpoint is defined as "A specification of the conventions for a particular kind of view

" which directly contradicts option D.

The question requires visual examination of a specific table where a technique is marked with the letter "W". Since the image link is not accessible, it's impossible to identify which business architecture decomposition technique corresponds to the "W" marking. All four options (Value Stream Mapping, Organization Mapping, Process Modeling, and Business Capability Mapping) are valid business architecture decomposition techniques according to TOGAF standards.

Without access to the image, I cannot determine which options are incorrect as all four are legitimate business architecture decomposition techniques.

d image

Explanation: The question requires visual examination of a specific table where a technique is marked with the letter "W". Since the image link is not accessible

it's impossible to identify which business architecture decomposition technique corresponds to the "W" marking. All four options (Value Stream Mapping

Organization Mapping

Process Modeling

and Business Capability Mapping) are valid business architecture decomposition techniques according to TOGAF standards.

Why Incorrect Options are Wrong:

Without access to the image

I cannot determine which options are incorrect as all four are legitimate business architecture decomposition techniques.

References:

- The Open Group TOGAF® Standard

Version 9.2

Part IV: Architecture Content Framework

Chapter 33: Architecture Artifacts

- The Open Group TOGAF® Series Guide: Business Architecture

Document Number: G169

Section 3: Business Architecture Techniques

- The Open Group ArchiMate® 3.1 Specification

Chapter 8: Business Layer

The detailed assessment of business capability gaps occurs in Phase B: Business Architecture. The primary objective of this phase is to develop the Target Business Architecture that shows how the enterprise will realize the Architecture Vision. A critical step within Phase B is to conduct a formal gap analysis between the Baseline and Target Business Architectures. This analysis identifies the specific business capabilities that need to be created, augmented, or retired to achieve the target state, thus forming the basis for subsequent architecture and implementation work.

A. Preliminary Phase: This phase focuses on establishing the architecture capability and tailoring the TOGAF framework; it does not involve detailed content-specific gap analysis.

B. Phase A: This phase, Architecture Vision, establishes the scope and high-level vision. While it may identify high-level business challenges, it does not perform a detailed capability gap assessment.

C. Phase C: This phase, Information Systems Architectures, conducts gap analysis for Data and Application architectures, not for business capabilities, which are an input from Phase B.

---

1. The Open Group. (2018). The TOGAF® Standard

Version 9.2. Van Haren Publishing.

Section 7.1

"Phase B: Business Architecture - Objectives": States an objective is to "develop Target Business Architectures... identifying candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures".

Section 7.5

"Phase B: Business Architecture - Steps": Step 6 is "Conduct formal gap analysis". This step explicitly details the process of comparing the Baseline and Target Business Architectures to identify gaps

which are foundational to defining the required business capabilities.

2. The Open Group. (2022). The TOGAF® Standard

10th Edition

ADM Guide.

Chapter 7

"Phase B: Business Architecture": Reaffirms the role of Phase B. Section 7.5

Step 6

"Conduct formal gap analysis"

describes using the gap analysis technique to compare the baseline and target states

with a focus on business-level items such as capabilities

processes

and roles. The output is a clear understanding of the capabilities to be addressed.

According to The Open Group's official documentation on value streams, each stage within a value stream is defined by several attributes. The "Exit Criteria" is the specific attribute that describes the set of conditions that must be fulfilled for the value stream stage to be considered complete. This end-state condition signifies that the value delivered by that stage has been achieved, allowing the process to move to the next stage or conclude.

B. Target state: This refers to the desired future state of an entire architecture or business capability, not the specific completion conditions for a single stage within a value stream.

C. End point: This is a generic term. While a stage has an end, "End point" is not the specific TOGAF terminology for the criteria defining that completion.

D. Completion stage: This is not a recognized term within the TOGAF framework for an element of a value stream stage; it is a distractor.

The Open Group

"TOGAF® Business Architecture: Value Streams" (Document No. C182)

January 2017. In Section 2.2

"Value Stream Stages"

the document lists the attributes of a value stream stage

stating: "Exit Criteria: The set of conditions that must be met for the value stream stage to be considered complete." (Page 5).

Business capabilities and value streams are modeled when identifying the business and technology environment. This phase involves documenting the current state architecture, including the organization's capabilities (what the business can do) and value streams (how value flows through the organization). These elements provide essential context for understanding the architectural landscape and form the baseline against which problems and solutions are evaluated.

A. When identifying and documenting desired outcomes

This phase focuses on future goals and objectives, not current capabilities and value streams.

C. When identifying the human actors

This phase identifies stakeholders and their concerns, not organizational capabilities or value flows.

D. When identifying, documenting and ranking the problem

This phase analyzes gaps and issues, not the modeling of existing capabilities and value streams.

1. The Open Group Architecture Framework (TOGAF) Version 9.2

Chapter 6: Architecture Development Method

Section 6.3.4 "Business Architecture"

pp. 89-91 - Details the documentation of business capabilities and value streams as part of environment analysis.

2. The Open Group Business Architecture Body of Knowledge (BIZBOK) Guide

Part II

Chapter 4 "Business Capability Mapping"

Section 4.2

pp. 67-69 - Describes capability modeling within environmental context establishment.

3. The Open Group ArchiMate 3.1 Specification

Chapter 8 "Business Layer"

Section 8.2 "Business Structure Concepts"

pp. 45-47 - Defines business capabilities and their role in environmental documentation.