OGA-031 Sample Questions Answers

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 conceptual model of architecture description from ISO/IEC 42010, an architecture view is a representation of a system from the perspective of a set of concerns. An architecture viewpoint is a specification of the conventions and rules for constructing and using an architecture view. A and B in the diagram correspond to these concepts respectively.

References: ISO/IEC/IEEE 42010: Conceptual Model1; ISO/IEC/IEEE 42010:2011 - Systems and software engineering — Architecture description2.

According to the ArchiMate 3.2 Specification1, 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.

According to the ArchiMate® 3.2 Specification1, 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 outcome1. Therefore, the correct answer is D. To represent the ability that an active structure element possesses.

 This is because the diagram shows the three main categories of relationships in ArchiMate: structural relationships, which model the static construction or composition of concepts; dependency relationships, which model how elements depend on or use other elements; and dynamic relationships, which model the temporal or causal connections between elements.

Based on the ArchiMate 3 documents or objectives, an application component represents a modular, deployable, and replaceable part of a software system that encapsulates its behavior and data. An application service represents an explicitly defined exposed application behavior. A data object represents data structured for automated processing. A realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity. An access relationship models the ability of behavior and active structure elements to observe or act upon passive structure elements. The diagram uses a realization relationship from the MEDINFO application component to the Medical Information service to indicate that the application component realizes the service. The diagram also uses an access relationship from the MEDINFO application component to the MEDBASE data object to indicate that the application component accesses the data object.

References: ArchiMate® 3.2 Specification, Chapter 10 Application Layer, Section 10.1 Active Structure Elements 1; ArchiMate® 3.2 Specification, Chapter 10 Application Layer, Section 10.3 Behavior Elements 1; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.1 Structural Relationships 1; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.3 Access Relationships 1; ArchiMate Example: Application Components - Visual Paradigm 2.

According to the standard notation conventions, a structure element is denoted by a rectangle with rounded corners. A structure element represents an entity that has a state and exhibits some behavior. Examples of structure elements are actors, roles, components, nodes, and objects.

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.