Effective Study Techniques for the The Open Group OGA-031 Exam

According to the ArchiMate® 3.2 Specification1, external active structure elements are also called interfaces. An interface represents a point of access where one or more services are offered by an active structure element to its environment1. Therefore, the correct answer is B. Interfaces.

The correct answer is D. Business event Claim Filed triggers a business process Accept Claim which in turn triggers an Assign Claim process. This is because the diagram shows a business event (Claim Filed) that initiates a business process (Accept Claim) which is performed by a business role (Customer Service Representative). The business process then triggers another business process (Assign Claim) which is also performed by the same business role. The diagram does not show any information flow or assignment relationships between the elements.

The diagram shows a work package, which is a grouping of behavior and/or structure elements that can be assigned to one or more performers. A work package can be used to model a project or a program, and it can contain deliverables, which are outcomes of the work package. The four elements (A, B, C, and D) are all deliverables that are part of the work package.

References: ArchiMate® 3.2 Specification, Chapter 10: Motivation Elements, Section 10.4 Work Package1; Chapter 11: Strategy Elements, Section 11.5 Deliverable2.

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 application layer metamodel, the passive counterpart of the application component is the data object, which represents data structured for automated processing. A data object can be accessed or manipulated by an application component or an application function.

References: ArchiMate® 3.2 Specification, Chapter 8: Application Layer1; Application Layer in ArchiMate Part 1 - Metamodel2.

According to the ISO/IEC 42010 standard1, an architecture viewpoint is a specification of the conventions for constructing and using a view. A view is a representation of a whole system from the perspective of a related set of concerns. An architecture view on an Enterprise Architecture is a representation of a part or whole of an Enterprise Architecture from the perspective of one or more stakeholders and their concerns.

The ArchiMate language provides a flexible approach in which architects and other stakeholders can use their own views on the Enterprise Architecture. In this approach, architecture views are specified by architecture viewpoints. Architecture viewpoints define abstractions on the set of models representing the Enterprise Architecture, each aimed at a particular type of stakeholder and addressing a particular set of concerns2.

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.

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.