Getting OGEA-103 Certification Made Easy!

A Request for Architecture Work is a document that describes the scope, approach, and expected outcomes of an architecture project. A Request for Architecture Work is usually initiated by the sponsor or client of the architecture work, and approved by the Architecture Board, which is a governance body that oversees the architecture work and ensures compliance with the architecture principles, standards, and goals. A Request for Architecture Work triggers a new cycle of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture12

An Architecture Vision is a high-level description of the desired outcomes and benefits of the proposed architecture. An Architecture Vision is the output of Phase A: Architecture Vision of the ADM cycle, which is the first phase of the architecture development. An Architecture Vision defines the scope and approach of the architecture work, and establishes the business goals and drivers that motivate the architecture work. An Architecture Vision also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process3

A trade-off analysis is a technique that can be used to evaluate and compare different architecture alternatives and select the most suitable one. A trade-off analysis involves identifying the criteria and factors that are relevant to the decision, such as costs, benefits, risks, and opportunities, and assessing the strengths and weaknesses of each alternative. A trade-off analysis also involves balancing and reconciling the multiple, often conflicting, requirements and concerns of the stakeholders, and ensuring alignment with the Architecture Vision and the Architecture Principles.

Therefore, the best answer is D, because it proposes the best approach for architecture development to realize the CEO’s change in direction for the company. The answer covers the Request for Architecture Work, the Architecture Vision, and the trade-off analysis techniques that are relevant to the scenario.

References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance 3: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Trade-Off Analysis

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.

References: 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

Ensuring compliance with internal and external standards and regulatory obligations is one of the activities included as part of Architecture Governance. Architecture Governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It involves establishing processes, roles, responsibilities, policies, and standards to ensure that architectures are aligned with the enterprise’s strategy and objectives, and meet the quality and performance requirements. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.6 Architecture Governance.

This statement best supports the need to govern Enterprise Architecture. Best practice governance enables the organization to control value realization by ensuring that architectures are aligned with the enterprise’s strategy and objectives, meet the quality and performance requirements, and deliver the expected benefits and outcomes. The Architecture Project does not mandate the governance of the target architecture, but rather follows the governance framework established by the enterprise. The TOGAF standard can be used without executive governance, but it is recommended that executive sponsorship and support are obtained for successful architecture development and transition. The Stakeholders preferences may go beyond the architecture project scope and need control, but this is not the primary reason for governing Enterprise Architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.6 Architecture Governance.