OG0-093: TOGAF 9 Combined Part 1 and Part 2 ExamDemo

In the TOGAF Architecture Content Framework, a catalog is an artifact that lists things. Matrices depict relationships between things, while diagrams are graphical representations.

ADM Phase E, Opportunities and Solutions, identifies and organizes implementation projects and work packages into an initial implementation and migration approach. Its purpose includes defining the initial implementation plans.

Architecture Governance establishes oversight that ensures architecture work and resulting solutions comply with internal standards, policies, and applicable external regulatory obligations.

The TOGAF Architecture Landscape uses Strategic, Segment, and Capability Architectures as its three levels of granularity. Capability Architecture provides the detailed view of how the enterprise supports a particular capability.

An Industry Architecture provides reusable architectural assets, such as shared data models and standards, that address requirements common to organizations in a particular industry. A model created by an association of companies for inventory and pricing information is therefore an industry-specific asset.

ADM Phase D addresses the Technology Architecture, so relevant architecture resources include generic technology models applicable to the organization’s industry sector.

TOGAF defines four primary architecture domains: Business, Data, Application, and Technology. Technology Architecture covers the technology capabilities and infrastructure that support the other domains.

Architecture Contracts establish implementation obligations, including objectives, effectiveness measures, acceptance criteria, and risk management. Scheduled architecture compliance reviews provide governance checkpoints that help ensure consistent, acceptable deployment quality. Contracts with third parties should be legally enforceable, and the Architecture Board must review any deviation before deciding whether a dispensation for a local customization is appropriate.

In the TOGAF ADM version-numbering convention, version 0.1 denotes that a high-level outline of the architecture is in place. A formally reviewed, detailed architecture is denoted by version 1.0.

An EA Capability is the organizational ability to carry out enterprise architecture work effectively. It encompasses the people, roles, responsibilities, skills, governance, and processes needed to operate the architecture practice; an EA framework and repository are supporting elements rather than the complete capability.

TOGAF Phase G governs implementation through signed Architecture Contracts and Architecture Compliance Reviews. Consistency across locations is supported by reviewing each contract’s objectives, effectiveness measures, acceptance criteria, and risks; conducting compliance reviews at key implementation points; and referring deviations to the Architecture Board. The Board may grant a dispensation when justified, rather than allowing local customization by default. An externally issued Architecture Contract should be legally enforceable.

In TOGAF ADM Phase G, the Architecture Contract formalizes the agreement between the architecture function and the implementation organization, providing the basis for implementation governance and conformance to the architecture.

In TOGAF, the Architecture Landscape has three levels of granularity: Strategic Architectures, Segment Architectures, and Capability Architectures.

In TOGAF, architecture is the structure of components, their inter-relationships, and the principles that guide their design and evolution over time.

TOGAF organizes the Architecture Landscape into Strategic Architectures, Segment Architectures, and Capability Architectures. Capability Architectures provide the detailed, capability-focused level of the landscape.

The conceptual structure of the TOGAF Architecture Governance Framework includes context, process, content, repository, and process flow control. An Architecture Vision belongs to TOGAF architecture-development work rather than to this governance-framework structure.

TOGAF is an Enterprise Architecture methodology and framework that provides a development process, established practices, and supporting resources for creating, using, and maintaining enterprise architectures. The TOGAF Architecture Development Method supplies the process for development and governance.

Requirements management controls requirements throughout their lifecycle, including managing their flow as they are communicated, changed, traced, and maintained.

TOGAF ADM Phase F, Migration Planning, develops the Implementation and Migration Plan and coordinates it with portfolio and project management to prioritize and sequence implementation projects.

Architecture Building Blocks define the functionality required by the architecture, while Solution Building Blocks specify how that functionality is implemented through particular products, systems, or components.

TOGAF ADM begins each of Phases B, C, and D by selecting the applicable reference models, viewpoints, and tools. Those selections guide development of the baseline and target architecture descriptions; gap analysis, roadmap definition, formal review, and the Architecture Definition Document follow later.

The ADM should be adapted so that it fits the enterprise’s specific needs, context, architecture capability, governance, and operating practices.

TOGAF ADM Phase B follows the definition of candidate roadmap components by resolving the resulting impacts across the Architecture Landscape, ensuring that related architecture domains and existing architectures are considered before stakeholder review and final documentation.

The Enterprise Continuum and Tools provide taxonomies for classifying and relating architecture and solution artifacts created by architecture activity.