OGEA-10B Exam Questions & Answers

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

The purpose of the Architecture Roadmap is to provide a high-level view of how the Baseline Architecture will transition to the Target Architecture over time. It lists work packages on a timeline showing progress towards the Target Architecture, as well as dependencies, risks, and benefits. The Architecture Roadmap forms part of the Implementation and Migration Plan and guides the execution of the architecture projects. Reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html

The scope of an architecture is the extent and level of detail of the architecture work. The scope of an architecture can be defined along four dimensions: project, breadth, depth, and architecture domains. The project dimension considers the boundaries and objectives of the architecture project, such as the time frame, budget, resources, and deliverables. The breadth dimension considers the coverage and completeness of the architecture across the enterprise, such as the organizational units, business functions, processes, and locations. The depth dimension considers the level of detail and specificity of the architecture, such as the granularity, abstraction, and precision of the architectural elements and relationships. The architecture domains dimension considers the aspects or segments of the architecture, such as the business, data, application, and technology domains.

Therefore, the depth dimension is the one that considers to what level of detail the architecting effort should go.

The Business Transformation Readiness Assessment technique is used to evaluate the readiness of the organization to undergo change and to identify the actions needed to increase the likelihood of a successful business transformation. These actions should be incorporated in the Implementation and Migration Plan, which is the detailed plan to transition from the Baseline Architecture to the Target Architecture.The Implementation and Migration Plan also includes the Transition Architectures, the Architecture Building Blocks, the Work Packages, the Implementation Governance Model, and the Architecture Contract12Reference:1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 27: Business Transformation Readiness Assessment2: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning

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.