The Architecture Requirements Repository stores all the requirements that are output of the

architecture development cycle, as well as the requirements that are input to the architecture

development cycle1. The Architecture Requirements Repository includes the following types of

requirements1:

•

Stakeholder Requirements: These are the high-level requirements and expectations of the

stakeholders, derived from the business drivers, goals, and objectives. They are captured and refined

in the Architecture Vision phase and the Requirements Management phase.

•

Architecture Requirements: These are the detailed requirements that specify what the

architecture must do or deliver to meet the stakeholder requirements. They are derived and refined

in the Business, Information Systems, and Technology Architecture phases.

•

Implementation and Migration Requirements: These are the detailed requirements that

specify what the implementation and migration projects must do or deliver to realize the

architecture. They are derived and refined in the Opportunities and Solutions and Migration Planning

phases.

The Architecture Requirements Repository is used to manage the architecture requirements

throughout the architecture lifecycle, ensuring their traceability, consistency, and compliance1. The

Architecture Board is the authority that reviews and approves the architecture requirements, as well

as the architecture deliverables and artifacts, as part of the architecture governance process2.

Reference: 1: Architecture Requirements Repository 2: Architecture Board

Building blocks are reusable components of business, IT, or architectural capability that can be

combined to deliver architectures and solutions. Building blocks can be defined at various levels of

detail, depending on the stage of architecture development. In the earlier phases of the ADM cycle

(A to D), building blocks are defined in generic terms, such as logical or physical, to provide a high-

level view of the architecture. In Phase E: Opportunities and Solutions, building blocks become

implementation-specific, meaning that they are linked to specific products, standards, technologies,

and vendors that are available in the market. This phase also identifies the delivery vehicles, such as

projects, programs, or portfolios, that will realize the building blocks12 Reference: 1: The TOGAF

Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E:

Opportunities and Solutions 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content

Framework, Chapter 36: Building Blocks

According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system

from the perspective of a related set of concerns1. It consists of one or more architecture models

that demonstrate how the system addresses the stakeholder concerns1.

An architecture viewpoint is a specification of the conventions for constructing and using an

architecture view to address specific stakeholder concerns1. It defines the perspective, scope,

notation, and techniques for creating an architecture view of a system1.

Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas,

principles, and requirements that could impact the final Target Architecture, because23:

Architecture views and viewpoints help to communicate and visualize the architecture in a way that

is meaningful and relevant to different stakeholders, addressing their specific interests and needs.

Architecture views and viewpoints help to elicit and validate the stakeholder concerns and

requirements, ensuring that they are aligned with the business goals and objectives, and that they

are consistent and feasible within the architecture context.

Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs

among the stakeholder concerns and requirements, ensuring that they are balanced and prioritized

in the architecture design and decision-making.

Architecture views and viewpoints help to demonstrate and verify the value and benefits of the

architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture

outcome and governance.

Reference:

1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders

2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an

Architecture Framework?

3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section 31.1: Basic Concepts

In the ADM documents which are under development and have not undergone any formal review

and approval process are called “draft”. This indicates that they are subject to change and refinement

as the architecture development progresses. Reference: The TOGAF® Standard | The Open Group

Website, Section 4.2.5 Architecture Deliverables.

The TOGAF standard covers the development of four architecture domains: Business, Data,

Technology and Application. These domains represent different aspects of an enterprise’s

architecture and provide a consistent way of describing, analyzing, and designing them. Reference:

The TOGAF® Standard | The Open Group Website, Section 2.2 Architecture Development Method

(ADM).

A Stakeholder Map is a technique that can be used to identify and classify the stakeholders of the

architecture work, and to document their key interests, requirements, and concerns. A stakeholder is

any person, group, or organization that has a stake in the outcome of the architecture work, such as

the sponsor, the client, the users, the suppliers, the regulators, or the competitors. A Stakeholder

Map can help to understand the needs and expectations of the stakeholders, and to communicate

and engage with them effectively1

The steps for creating a Stakeholder Map are:

Identify the stakeholders of the architecture work, using various sources and methods, such as

interviews, surveys, workshops, or existing documents.

Classify the stakeholders according to their roles, responsibilities, and relationships, using various

criteria and dimensions, such as power, influence, interest, attitude, or impact.

Define the concerns and relevant views for each stakeholder group, using various techniques, such as

business scenarios, use cases, or value propositions. A concern is a key interest or issue that is

relevant to the stakeholder, such as a goal, a problem, a need, or a risk. A view is a representation of

the system of interest from the perspective of one or more stakeholders and their concerns.

Record the stakeholders and their concerns in a Stakeholder Map, which shows the mapping

between the stakeholder groups, the concerns, and the views. The Stakeholder Map also shows the

dependencies, assumptions, and issues related to each stakeholder and concern.

Therefore, the best answer is B, because it recommends the approach that would enable the

development of an architecture that addresses the concerns of the CIO and the partners, using the

Stakeholder Map technique. The answer covers the following aspects:

An analysis of the stakeholders is undertaken, which involves identifying, classifying, and defining

the stakeholders and their concerns.

The stakeholders and their concerns are documented in a Stakeholder Map, which provides a clear

and comprehensive picture of the stakeholder landscape and their interests.

The concerns and relevant views are recorded in the Architecture Vision document, which is the

output of Phase A: Architecture Vision of the Architecture Development Method (ADM), which is the

core process of the TOGAF standard that guides the development and management of the enterprise

architecture. The Architecture Vision defines the scope and approach of the architecture work, and

establishes the business goals and drivers that motivate the architecture work. The Architecture

Vision also involves obtaining the approval and commitment of the sponsors and other key

stakeholders, and initiating the Architecture Governance process2

The requirements include risk mitigation through regular assessments, which involves identifying,

analyzing, and evaluating the risks that may affect the architecture, and determining the appropriate

measures or actions to prevent, reduce, or mitigate the risks. Risk mitigation can also involve

monitoring and reviewing the risk situation, and communicating and reporting the risk status and

actions3

This approach also allows a supervised agile implementation of the continuous Machine Learning,

which involves applying agile principles and practices to the architecture development and

implementation, such as iterative and incremental delivery, frequent feedback, collaboration, and

adaptation. A supervised agile implementation can help to ensure the quality, value, and alignment

of the architecture, and to respond to the changing needs and expectations of the stakeholders.

Reference: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 24:

Stakeholder Management 2: The TOGAF Standard, Version 9.2, Part II: Architecture Development

Method (ADM), Chapter 18: Phase A: Architecture Vision 3: The TOGAF Standard, Version 9.2, Part III:

ADM Guidelines and Techniques, Chapter 32: Risk Management : The TOGAF Standard, Version 9.2,

Part III: ADM Guidelines and Techniques, Chapter 29: Applying Iteration to the ADM

Business principles business goals, and business drivers provide context for architecture work, by

describing the needs and ways of working employed by the enterprise. They define what the

enterprise wants to achieve, how it wants to operate, and what factors influence its decisions and

actions. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.

According to the TOGAF Standard, 10th Edition, an architecture contract is “a formal agreement

between a service provider and a service consumer that defines the mutual commitments and

expectations for the delivery of an architecture” 1. An architecture contract is a governed approach

of a particular deliverable that will ensure adherence to the principles, standards, and requirements

of the existing or developing architectures, as it specifies the roles, responsibilities, deliverables,

quality criteria, and acceptance criteria for the architecture work 1. The other options are not

correct, as they are not governed approaches of a particular deliverable, but rather different types of

deliverables within the architecture development process. An architecture vision is “a high-level,

aspirational view of the target architecture” 1. A statement of architecture work is “a document that

defines the scope and approach that will be used to complete an architecture project” 1. An

architecture definition document is “a document that describes the baseline and target architectures

for one or more domains” 1. Reference: 1: TOGAF Standard, 10th Edition, Part I: Introduction,

Chapter 3: Definitions.

The statement "Projects may cycle between ADM phases, in planned cycles covering multiple

phases" illustrates the concept of iteration, which is the process of repeating the ADM phases or

steps within a phase to refine the architecture outputs and address the changing requirements and

stakeholder concerns. Iteration can occur at different levels of granularity and scope, such as within a

single phase, across multiple phases, or across the entire ADM cycle. Iteration can also be applied to

different architecture domains, such as business, data, application, and technology. Iteration is a key

feature of the ADM that enables the development of architectures that are fit for purpose,

adaptable, and responsive to change. Reference: : The TOGAF Standard, Version 9.2, Part III: ADM

Guidelines and Techniques, Chapter 24: Applying Iteration to the ADM

According to the TOGAF Standard, 10th Edition, the rationale section of the architecture principles

template should highlight the business benefits of adhering to the principle, as well as the business

risks of not adhering to it 1. The rationale section should explain the reasoning behind the principle,

and provide evidence or arguments to support it. The rationale section should also link the principle

to the business drivers, goals, and objectives of the enterprise, and show how the principle

contributes to the value and success of the enterprise. The other options are not correct, as they

have different purposes in the architecture principles template. The name section should provide a

short and memorable name for the principle, such as “Information is an Asset” or “Business

Continuity” 1. The statement section should provide a concise and formal statement of the principle,

such as “The enterprise’s information is recognized as a core asset, and is managed accordingly” or

“The enterprise’s ability to provide critical services and products must be maintained in the event of

a disaster” 1. The implications section should identify the impact of the principle on the enterprise,

such as the changes, costs, benefits, and risks that may result from applying or violating the principle

1. Reference: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 23:

Architecture Principles, Section 23.3 Developing Architecture Principles.