The Open Group OGEA-101 - TOGAF Enterprise Architecture Part 1 Exam (English)

Comprehensive and Detailed Explanation

When defining the scope of an architecture, TOGAF identifies four dimensions that need to be considered:

Breadth – This dimension addresses the extent of the enterprise that will be impacted by the architecture. It answers the question: How much of the enterprise is covered? For example, does the scope include the entire enterprise, a business unit, a division, or just a single organizational function?

Depth – This refers to the level of detail to be covered. For instance, will the architecture describe high-level capabilities, or will it go into detailed system design?

Time Period – This defines the planning horizon of the architecture. It could be short-term (tactical), medium-term, or long-term (strategic).

Architecture Domains – This refers to which domains are covered: Business, Data, Application, and Technology. The scope may include all or just a subset of these domains.

Project Scope (sometimes discussed separately) – Focuses on which specific programs, portfolios, or projects will be impacted.

Among these, the dimension that specifically relates to the extent of the enterprise is Breadth.

Why the other options are incorrect

A. Architecture Domains: Refers to the domains covered (Business, Data, Application, Technology), not the extent of the enterprise.

B. Depth: Refers to the level of detail, not the enterprise extent.

C. Project: Refers to the program or initiative focus, not enterprise coverage.

References

The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — Preliminary Phase (scope considerations).

The Open Group, TOGAF® 9 Certified Study Guide — discussion of the dimensions of architecture scope (Breadth, Depth, Time Period, Architecture Domains).

The objective of the ADM Implementation Governance Phase is to provide an architectural oversight of the implementation and to ensure conformance for the target architecture. This phase involves establishing procedures and processes to monitor and control the implementation projects and to verify that they comply with the defined architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.7 Phase G: Implementation Governance.

These domains provide a consistent way to describe and understand the architecture from different perspectives, such as business, information, and technology12. Each domain has its own set of concepts, models, views, and artifacts that define the structure and behavior of the architecture within that domain12.

The other options are incorrect because:

•Logical and Physical are not architecture domains, but rather levels of abstraction that can be applied to any domain. Logical architecture describes the functionality and behavior of the system, while physical architecture describes the implementation and deployment of the system3.

•Information and Data are not distinct architecture domains, but rather aspects of the same domain. Information architecture describes the meaning and context of the data, while data architecture describes the structure and format of the data4.

•Capability and Segment are not architecture domains, but rather levels of granularity that can be applied to any domain. Capability architecture describes the current and desired states of a specific business capability, while segment architecture describes a subdivision of the enterprise that has a clear business focus5.

According to the TOGAF Standard, 10th Edition, a transformation readiness assessment is a technique that evaluates the preparedness of the organization to undergo a change, and identifies the actions needed to increase the likelihood of a successful outcome. A transformation readiness assessment can be conducted in Phase E: Opportunities and Solutions, and the actions resulting from it can be dealt with in Phase F: Migration Planning 1. In Phase E, the transformation readiness assessment can help to identify the major implementation challenges and risks, and to define the critical success factors and key performance indicators for the architecture project. In Phase F, the actions resulting from the transformation readiness assessment can help to develop a detailed and realistic migration plan, and to address the gaps, issues, and dependencies that may affect the transition to the target architecture 1. References: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 29: Business Transformation Readiness Assessment.

The ability to develop, use, and sustain the architecture of a particular enterprise using architecture to govern change is an EA Capability. An EA Capability is a set of skills, processes, roles, responsibilities, tools, and techniques that enable an enterprise to successfully develop and maintain its Enterprise Architecture and achieve its desired outcomes. An EA Capability is part of an enterprise’s overall capability portfolio and should be aligned with its strategy and objectives. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.

The planning horizon, depth, and breadth of an Architecture Project, along with the contents of the EA Repository, are typically framed by Strategy, Portfolio, Segment, and End-to-end Target Architecture. The ' Segment ' refers to a part of the organization, typically addressed in a Segment Architecture, while ' End-to-end Target Architecture ' encompasses the complete view of the planned architecture across the entire organization.

An Architecture Contract is a deliverable that specifies the responsibilities and obligations of the parties involved in the implementation and governance of an architecture. It ensures a system of continuous monitoring to check integrity changes decision-making and audit of all architecture-related activities. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.4 Architecture Contracts.

When considering agile development, Architecture to Support Portfolio will identify the necessary products for the enterprise, define their boundaries, and outline the constraints for a product owner. This process directly relates to defining the enterprise ' s backlog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.