The Open Group OGEA-10B Exam Questions

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.

An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2. The Preliminary Phase involves the following activities1:

* Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture

* Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools

* Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise

* Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work

* Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools

* Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization

* Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization

The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.

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.

The Architecture Requirements Specification is one of the TOGAF deliverables that provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture12. It is a companion to the Architecture Definition Document, which provides a qualitative view of the solution and aims to communicate the intent of the architect. The Architecture Requirements Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture3. It typically forms a major component of an implementation contract or contract for more detailed Architecture Definition4. Reference:

* Deliverable: Architecture Requirements Specification - The Open Group

* Architecture Requirements Specification - Visual Paradigm Community Circle

* The TOGAF Standard, Version 9.2 - Definitions - The Open Group

* The TOGAF Standard, Version 9.2 - Architecture Requirements Specification - The Open Group

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.