:

Comprehensive and Detailed in Depth

An Application Interface in ArchiMate represents a point of access where an Application Service is

exposed to users or other applications.

Application Interfaces define how users or other software components interact with an Application

Service. This is clearly defined in the ArchiMate 3.2 Specification, which states that an Application

Interface provides access to an Application Service.

Reference:

Archi User Guide

ArchiMate 3.2 Specification

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.

Reference: 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.

Reference: ArchiMate® 3.2 Specification, Chapter 8: Application Layer1; Application Layer in

ArchiMate Part 1 - Metamodel2.

The diagram uses the ArchiMate notation for a goal element and an aggregation relationship. A goal

element represents an end state that a stakeholder intends to achieve. An aggregation relationship

indicates that a whole is composed of parts. In this case, the goal ‘Reduce Expense Ratio from 13% to

11%’ is composed of three sub-goals that contribute to its achievement.

Reference: ArchiMate® 3.2 Specification, Chapter 10: Motivation Elements, Section 10.1 Goal;

Chapter 5: Relationships, Section 5.2 Aggregation.

Based on the ArchiMate 3 documents or objectives, an aggregation relationship indicates that an

element groups a number of other concepts. The aggregation relationship has been inspired by the

aggregation relationship in UML class diagrams. Unlike composition, aggregation does not imply an

existence dependency between the aggregating and aggregated concepts. The notation for an

aggregation relationship is a solid line with an empty diamond at the end that points to the whole

element. The diagram uses an aggregation relationship from the bottom elements to the top

element to indicate that the top element groups the bottom elements.

Reference: ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.1 Structural

Relationships 1; Structural Relationship: Part 3 - ArchiMate Resources for FREE 2.

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

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.

Reference: 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, the ArchiMate standard provides a set of entities and relationships for representing Architecture Description. Architecture Description is a work product used to express an architecture for a system-of-interest. The ArchiMate language is an open and independent modeling language for Enterprise Architecture that is supported by different tool vendors and consulting firms. Reference: The ArchiMate® Enterprise Architecture Modeling Language | The Open Group Website 1; ArchiMate® 3.2 Specification, Chapter 1 Introduction, Section 1.1 Objective 2.

According to the ArchiMate 3.2 Specification1, a driver represents an external or internal condition

that motivates an organization to define its goals and implement the changes necessary to achieve

them. Drivers that are associated with a stakeholder are often called “concerns” of that stakeholder.

A stakeholder represents the role of an individual, team, or organization (or classes thereof) that

represents their interests in the outcome of the architecture. A motivation element is an element

that represents the reasons for designing and implementing an architecture, such as stakeholders,

drivers, goals, principles, requirements, or value. A motivation element is denoted by a hexagonal

shape.

The diagram below shows a motivation element (driver) named Market Share that influences a

stakeholder named CMO. The influence relationship is denoted by a dashed line with an open

arrowhead.

The influence relationship means that the driver affects the stakeholder’s interests or concerns.

Therefore, the best interpretation of the diagram is that the CMO is motivated by the driver Market

Share.