n131

ArchiMate

2.1

Copyright 2013 The Open Group. All Rights Reserved. N131 Reference Card: ArchiMate

2.1 ArchiMate

is a registered trademark of The Open Group.

AArrcchhiiMMaattee CCoorree

Active Structure Concepts Behavioral Concepts Passive Structure

Concepts

Bu

sin

es

s

Business

actor

Business

role

Business

process

Business

service

Business

object

Representation

Business

collaboration

Business

function

Business

event

Product

Meaning

Business

interaction

Contract

Value

Ap

plicati

on

Applicationcomponent

Application

collaboration

Application

function

Application

interaction

Data

object

Tech

no

log

y

Node

Device

Artifact

Network

System

software

Communication

path

Infrastructure

interface

Location

Infrastructure service

Application service

Business interface

Application interface

ArchiMate

2.1


2.1 ArchiMate


BBuussiinneessss LLaayyeerr Concept Description Notation Concept Description Notation

Business Actor

An organizational entity that is capable of performing behavior via a role.

Business

actor

Business Event

Something that happens (internally or externally) and influences behavior (business process, business function, business interaction).

Business

event

Business Role

The responsibility for performing specific behavior, to which an actor can be assigned.

Business

role

Business Service

A service that fulfils a business need for a customer (internal or external to the organization).

Business

service

Business Collaboration

An aggregate of two or more business roles that work together to perform collective behavior.

Business

collaboration

Business Object

A passive element that has relevance from a business perspective.

Business

object

Business Interface

A point of access where a business service is made available to the environment.

Representation A perceptible form of the information carried by a business object.

Representation

Location A conceptual point or extent in space.

Meaning The knowledge or expertise present in a business object or its representation, given a particular context.

Meaning

Business Process

A behavior element that groups behavior based on an ordering of activities. It is intended to produce a defined set of products or business services.

Business

process

Value The relative worth, utility, or importance of a business service or product.

Value

Business Function

A behavior element that groups behavior based on a chosen set of criteria (typically required business resources and/or competences).

Business

function

Product A coherent collection of services, accompanied by a contract/set of agreements, which is offered as a whole to (internal or external) customers.

Product

Business Interaction

A behavior element that describes the behavior of a business collaboration.

Business

interaction

Contract A formal or informal specification of agreement that specifies the rights and obligations associated with a product.

Contract

Business interface

ArchiMate

2.1


2.1 ArchiMate


EExxaammppllee BBuussiinneessss LLaayyeerr MMooddeell

ArchiMate

2.1


2.1 ArchiMate


AApppplliiccaattiioonn LLaayyeerr Concept Definition Notation

Application Component A modular, deployable, and replaceable part of a software system that encapsulates its behavior and data and exposes these through a set of interfaces.

Application

component

Application Collaboration An aggregate of two or more application components that work together to perform collective behavior. Application

collaboration

Application Interface A point of access where an application service is made available to a user or another application component. Application

interface

Application Function A behavior element that groups automated behavior that can be performed by an application component. Application

function

Application Interaction A behavior element that describes the behavior of an application collaboration. Application

interaction

Application Service A service that exposes automated behavior.

Data Object A passive element suitable for automated processing. Dataobject

Application service

ArchiMate

2.1


2.1 ArchiMate


EExxaammppllee AApppplliiccaattiioonn LLaayyeerr MMooddeell

ArchiMate

2.1


2.1 ArchiMate


TTeecchhnnoollooggyy LLaayyeerr Concept Definition Notation Concept Definition Notation

Node A computational resource upon which artifacts may be stored or deployed for execution.

Node

System Software

A software environment for specific types of components and objects that are deployed on it in the form of artifacts.

System

software

Device A hardware resource upon which artifacts may be stored or deployed for execution.

Device

Infrastructure Function

A behavior element that groups infrastructural behavior that can be performed by a node.

Network A communication medium between two or more devices.

Network

Infrastructure Service

An externally visible unit of functionality, provided by one or more nodes, exposed through well-defined interfaces, and meaningful to the environment.

Communication Path

A link between two or more nodes, through which these nodes can exchange data.

Communication

path

Artifact A physical piece of data that is used or produced in a software development process, or by deployment and operation of a system.

Artifact

Infrastructure Interface

A point of access where infrastructure services offered by a node can be accessed by other nodes and application components.

Infrastructure

interface

Infrastructure service

ArchiMate

2.1


2.1 ArchiMate


EExxaammppllee TTeecchhnnoollooggyy LLaayyeerr MMooddeell

Note: In ArchiMate models, there are no formal semantics assigned to colors. However, they can be used freely to stress certain aspects in models. For instance, in the example models presented in the standard, colors are often used to distinguish between the layers of the ArchiMate framework: yellow for the business layer, blue for the application layer, and green for the technology layer.

ArchiMate

2.1


2.1 ArchiMate


RReellaattiioonnsshhiippss Structural Relationships Notation

Association Association models a relationship between objects that is not covered by another, more specific relationship.

Access The access relationship models the access of behavioral concepts to business or data objects.

Used by The used by relationship models the use of services by processes, functions, or interactions and the access to interfaces by roles, components, or collaborations.

Realization The realization relationship links a logical entity with a more concrete entity that realizes it.

Assignment The assignment relationship links units of behavior with active elements (e.g., roles, components) that perform them, or roles with actors that fulfill them.

Aggregation The aggregation relationship indicates that an object groups a number of other objects.

Composition The composition relationship indicates that an object is composed of one or more other objects.

Dynamic Relationships Notation

Flow The flow relationship describes the exchange or transfer of, for example, information or value between processes, function, interactions, and events.

Triggering The triggering relationship describes the temporal or causal relationships between processes, functions, interactions, and events.

Other Relationships Notation

Grouping The grouping relationship indicates that objects, of the same type or different types, belong together based on some common characteristic.

Junction A junction is used to connect relationships of the same type.

Specialization The specialization relationship indicates that an object is a specialization of another object.

ArchiMate

2.1


2.1 ArchiMate


EExxaammppllee RReellaattiioonnsshhiippss

ArchiMate

2.1


2.1 ArchiMate


EExxtteennssiioonnss

Motivation Extension

Implementation and Migration Extension

The Motivation Extension adds concepts such as goal, principle, and requirement. It addresses the way the enterprise architecture is aligned to its context, as described by motivational elements.

The Implementation and Migration Extension adds concepts to support the later ADM phases, related to the implementation and migration of architectures.

ArchiMate

2.1


2.1 ArchiMate


MMoottiivvaattiioonn EExxtteennssiioonn Concept Definition Notation

Stakeholder The role of an individual, team, or organization (or classes thereof) that represents their interests in, or concerns relative to, the outcome of the architecture.

Driver Something that creates, motivates, and fuels the change in an organization.

Assessment The outcome of some analysis of some driver.

Goal An end state that a stakeholder intends to achieve.

Requirement A statement of need that must be realized by a system.

Constraint A restriction on the way in which a system is realized.

Principle A normative property of all systems in a given context, or the way in which they are realized.

Intentional Relationships Notation

Association Assocation models that some intention is related to the source of that intention

Aggregation Aggregation models that some intentional element is divided into multiple intentional elements.

Realization Realization models that some end is realized by some means.

Influence Influence models that some motivational element has a positive or negative influence on the realization of another motivational element.

ArchiMate

2.1


2.1 ArchiMate


EExxaammppllee MMoottiivvaattiioonn EExxtteennssiioonn MMooddeell

ArchiMate

2.1


2.1 ArchiMate


IImmpplleemmeennttaattiioonn aanndd MMiiggrraattiioonn EExxtteennssiioonn Concept Definition Notation

Work Package A series of actions designed to accomplish a unique goal within a specified time.

Deliverable A precisely-defined outcome of a work package.

Plateau A relatively stable state of the architecture that exists during a limited period of time.

Gap An outcome of a gap analysis between two plateaus.

ArchiMate

2.1


2.1 ArchiMate


EExxaammppllee IImmpplleemmeennttaattiioonn && MMiiggrraattiioonn EExxtteennssiioonn MMooddeell

n131

Documents

business services

business function

business need

business roles

business perspective

behavior element

open group

groups behavior