OGEA-101: TOGAF Enterprise Architecture Part 1 ExamDemo

TOGAF divides the Architecture Landscape into Strategic, Segment, and Capability Architectures. Strategic Architecture is the enterprise-wide, long-term level, while Segment Architecture is the intermediate level for an area of the enterprise. Thus, C is Enterprise Strategic Architecture and B is Segment Architecture.

Requirements Management is a continuous ADM process that identifies, stores, manages, and feeds architecture requirements into and out of the relevant ADM phases throughout the ADM cycle.

TOGAF ADM iteration can occur across multiple architecture projects: each project may conduct its own ADM cycle at the same time while coordinating dependencies and relationships with other projects.

A Content Metamodel defines architectural content types and the relationships among them, giving architecture information a consistent structure that can be processed and presented to address stakeholder needs.

The Architecture Landscape provides a view of the enterprise architecture and its deployed or planned assets, including the applications in use throughout the enterprise.

The Implementation and Migration Plan consolidates the implementation, migration, and organizational-readiness actions needed to execute the architecture change. It is developed across ADM Phases E and F and incorporates actions arising from the Business Transformation Readiness Assessment.

Gap Analysis compares baseline and target architectures to identify capabilities, functions, or services that are missing and must be added or changed to achieve the target state.

In the ADM, a document that is still being developed and has not completed formal review and approval is classified as a draft.

In the TOGAF ADM, Phase F (Migration Planning) establishes stakeholder understanding of the business value and cost of work packages and Transition Architectures. Phase G (Implementation Governance) governs solution implementation and handles implementation-driven architecture change requests. Phase H (Architecture Change Management) maintains the architecture development cycle and ensures that the Enterprise Architecture Capability continues to meet current requirements.

Phase A, Architecture Vision, identifies stakeholders and their concerns while establishing the architecture initiative’s scope, vision, and approval basis.

Business principles, business goals, and business drivers establish the business context for architecture work by expressing how the enterprise operates, what it aims to achieve, and the forces motivating architectural change.

The Architecture Requirements Specification sets out the statements of requirement that an implementation project must satisfy in order to comply with the architecture.

The Statement expresses the architecture principle itself as a clear, unambiguous fundamental rule. The rationale explains why it is needed, implications describe its consequences, and the name is only a memorable identifier.

Risk Management is applied across all phases of the TOGAF Architecture Development Method (ADM). Risks are identified, assessed or classified, and mitigated so that the transformation effort can be governed and executed with known exposures addressed.

In TOGAF ADM Phase A, Architecture Vision, the earliest building-block definitions are relatively abstract. They are refined during the subsequent architecture-development phases.

Discipline in Architecture Governance requires all parties to commit to following established procedures and processes.

A Capability Assessment evaluates the enterprise’s baseline capability and the target capability it needs to achieve. It is produced in ADM Phase A and updated in Phase E to support planning the transition from the baseline to the target state.

In the TOGAF Architecture Repository, the Architecture Landscape holds enterprise architecture assets and is governed; the Architecture Requirements Repository holds authorized architecture requirements that drive the enterprise; and the Solutions Landscape contains solution building blocks that support the Architecture Landscape and realize business outcomes.

The TOGAF Implementation Governance Model defines the project-specific governance processes, organization, roles, responsibilities, checkpoints, and success or failure criteria for implementation. It provides the handoff into Architecture Governance for ADM Phase G.

Risk management includes classifying risks, identifying them, and performing an initial assessment before mitigation, residual-risk assessment, and ongoing monitoring.

TOGAF ADM Phase A recommends Business Scenarios as a technique for identifying business requirements and communicating the business context that shapes the Architecture Vision.

In TOGAF, initial risks are identified during Phase A (Architecture Vision) as part of the Business Transformation Readiness Assessment, which evaluates readiness factors (vision, desire, need, capacity, capability, funding, sponsorship, etc.) and derives the associated risks for each. These risks are then classified and carried forward to be mitigated in the Implementation and Migration Plan (Phases E and F). Business Scenarios are a technique for eliciting and articulating requirements, not for formally identifying transformation risks, so option D is wrong. Gap analysis (option A) identifies architecture gaps rather than being the risk-identification vehicle.

A business scenario defines a business problem or opportunity together with the outcome the business wants to achieve.

Within the ADM, documents not yet subjected to formal review and approval are designated draft, while documents that have completed those governance steps are designated approved.