OGEA-10B Exam Results

• The illustration shows an architecture development cycle based on the TOGAF ADM (Architecture Development Method), which is a method for developing and managing an enterprise architecture1.
• The ADM consists of nine phases, each with a specific purpose and output. The phases are1:
• In addition to these phases, there is a central process called Requirements Management, which is labeled as item 1 in the illustration. This process operates throughout the ADM cycle, and its purpose is to manage the architecture requirements throughout the architecture development, ensuring that they are aligned with the business requirements and the stakeholder concerns2.
• Therefore, the description that matches the phase of the ADM labeled as item 1 is C. Operates the process of managing architecture requirements.

References:

• 1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
• 2: The TOGAF Standard, Version 9.2, Chapter 17: Requirements Management

 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 Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.

The other sections of the TOGAF template for Architecture Principles are1:

•Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.

•Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.

•Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.

References: 2: The TOGAF Standard, Version 9.2 - Architecture Principles 3: TOGAF 8.1.1 Online - Architecture Principles 1: Architecture Principles Template

• A-Architecture Repository: This is a part of the Architecture Metamodel that contains artifacts structured according to the metamodel. It includes the Architecture Landscape which is adopted by the enterprise and governed by certain standards and practices.
• B-Governing Board: The Governing Board ensures visibility and escalation, meaning it oversees and manages the capability of the architecture landscape. It plays a crucial role in governance.
• C-Enterprise Capability: This refers to how well an enterprise can execute its mission, meet business objectives or satisfy its stakeholders’ needs and expectations. It’s influenced by both internal factors (like resources, processes) and external ones (like market trends).

References: TOGAF Version 9.1, Chapter 34: 1