The ArchiMate 3 Part 1 Examination (OGA-031)

This is because a grouping is a composite element that aggregates or groups other elements based on some common characteristic or purpose. A course of action is a motivation element that represents an approach or plan for achieving some goal. An aggregation is a structural relationship that models the whole-part hierarchy between elements. A contract is a passive structure element that represents a formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product or service.

ased on the ArchiMate 3 documents or objectives, a grouping is a composite element that consists of other concepts, from one or more aspects or layers of the ArchiMate language. A grouping can be used to model a logical or physical grouping of elements that belong together based on some criteria. A grouping can itself aggregate or compose other groupings, leading to a hierarchy of these elements.

References: ArchiMate® 3.2 Specification, Chapter 4 Generic Metamodel, Section 4.1 Behavior and Structure Elements, Subsection 4.1.5 Composite Elements  1 ; Composite Elements | Enterprise Architect User Guide  2 .

According to the ArchiMate 3.2 Specification 1 , a capability is an ability that an active structure element, such as an organization, person, or system, possesses. A requirement is a statement of need that must be realized by a system. Capabilities and requirements are both motivation elements that represent the reasons for designing and implementing an architecture.

The ArchiMate language defines two relationships that are permitted between capabilities and requirements:

Assigned to: This relationship links a requirement to a core element (such as a business actor, a business service, a business process, an application service, an application component, etc.) that is responsible for realizing it. The core element may be assigned to a capability that enables it to realize the requirement.

Realizes: This relationship links a capability to a requirement that is fully or partially realized by that capability.

Based on the ArchiMate 3 documents or objectives, a capability represents an ability that an active structure element, such as an organization, person, or system, possesses. An outcome represents an end result that has been achieved. A realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity. The diagram uses a realization relationship from the Digital customer management capability to the Excellent online customer interaction outcome to indicate that the capability realizes the outcome.

References: ArchiMate® 3.2 Specification, Chapter 7 Strategy Elements, Section 7.2 Structure Elements  1 ; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.1 Structural Relationships  1 ; Capability Map: Artifact of Vision Phase - Visual Paradigm Guides  2 .

According to the ArchiMate® 3.2 Specification 1 , a capability represents an ability that an active structure element, such as an organization, person, or system, possesses.  Capabilities are typically aimed at achieving some goal or delivering value by realizing an outcome 1 . Therefore, the correct answer is D. To represent the ability that an active structure element possesses.

Comprehensive and Detailed in Depth Explanation: Architecture Viewpoints are predefined perspectives or templates that define how specific stakeholders view an architecture . They provide guidelines for structuring models to communicate effectively with different stakeholders .

The ArchiMate 3.2 Specification describes Architecture Viewpoints as tools for filtering and structuring architectural representations to address stakeholder concerns .

References:

Archi User Guide ​

ArchiMate 3.2 Specification

Comprehensive and Detailed In-Depth Explanation:

The diagram presents Principles and Goals , which are core elements in ArchiMate’s Motivation Layer . In ArchiMate 3.2 , principles represent fundamental guidelines or constraints that influence architecture , while goals represent intended outcomes of an enterprise transformation.

Understanding the Diagram:

Improve Data Consistency and Reduction of Maintenance Costs are goals —they describe desirable future states of the enterprise.

Single System of Record for each Data Element and Common Use of Applications are principles —they guide decision-making and architecture choices to help achieve the goals.

The relationships between these elements indicate that the principles contribute to realizing the goals .

Analysis of Answer Choices:

✅ A. Principles and the goals they realize. → ✅ Correct Answer

Principles define fundamental rules that guide decision-making (e.g., Single System of Record for each Data Element ).

Goals represent desired business outcomes (e.g., Improve Data Consistency ).

ArchiMate 3.2 Specification, Section 6.2.2 , defines how principles guide enterprise architecture to realize goals.

✅ B. Requirements and the meanings assigned. → ❌ Incorrect

Requirements describe what needs to be implemented , whereas this diagram represents high-level principles and goals , not specific implementation needs.

ArchiMate 3.2 Specification, Section 6.2.3 , differentiates requirements from principles and goals .

✅ C. Goals and the assigned values. → ❌ Incorrect

While the diagram includes goals , the lower elements are not values but principles that help achieve the goals.

Values in ArchiMate typically represent high-level business benefits rather than architectural guidelines.

✅ D. Drivers and the associated outcomes. → ❌ Incorrect

Drivers represent external forces or motivations (e.g., market trends, customer demands).

This diagram does not include external drivers ; it focuses on principles guiding internal changes.

Final Answer: ✅ A. Principles and the goals they realize.

References:

ArchiMate 3.2 Specification: Sections 6.2.2 (Principles) and 6.2.1 (Goals).

Archi User Guide: Understanding the relationship between principles and goals in enterprise architecture.

Comprehensive and Detailed in Depth Explanation: The Course of Action element represents what an enterprise has decided to do in order to achieve a strategic objective. It defines high-level actions and strategies that guide business capabilities and activities .

The ArchiMate 3.2 Specification states that Courses of Action define the high-level choices and strategic actions taken by an organization .

References:

Archi User Guide ​

ArchiMate 3.2 Specification

Based on the ArchiMate 3 documents or objectives, the diagram uses a composition relationship to indicate that the financial processing function consists of three sub-functions A, B, and C. A composition relationship is a type of structural relationship that represents a whole-part hierarchy between elements. The notation for a composition relationship is a solid line with a filled diamond at the end that points to the whole element.

References: ArchiMate® 3.2 Specification, Chapter 4 Generic Metamodel, Section 4.1 Behavior and Structure Elements, Subsection 4.1.2 Structural Relationships  1 .

According to the ArchiMate® 3.2 Specification 1 , an application function describes the internal behavior of an application component, and an application component may be assigned to an application function, which means that the application component performs the application function. Therefore, the correct answer is A. Assignment.  This relationship indicates that an instance of a technology function performs (part of) the behavior of an instance of an application function 1 .