Download as pdf or txt
Download as pdf or txt
You are on page 1of 19

Introduction to

Architecture
Modeling Using
Archimate® 3
ArchiMate
● A modeling language for
Enterprise Architecture.
– Open
– Independent
– Supported by different tool
vendors and consulting firms

● Role is to provide graphical


language for the
representation of EA over
time (including
transformation and
migration planning).

Slide 2
Introduction | Brief History
ArchiMate was created in the period 2002-2004 in the Netherlands by the
Telematica Instituut in cooperation with the government, industry, and
academia, including:
• Ordina
• Radboud Universiteit Nijmegen
• Leiden Institute for Advanced Computer Science (LIACS)
• Centrum Wiskunde & Informatica (CWI)

The development included tests in organisations such as ABN AMRO, the


Dutch Tax and Customs Administration, and the Stichting Pensioenfonds ABP.

In 2008 the ownership and stewardship of ArchiMate was transferred from


the ArchiMate Foundation to The Open Group. It is now managed by The
Open Group ArchiMate Forum.

Slide 3
Introduction | Archimate Releases

ArchiMate 2.1
ArchiMate 1.0 - February 2009 •A maintenance update addressing feedback and
•The Open Group published ArchiMate 1.0 as an Open comments raised since the introduction of ArchiMate
Group standard 2.0

Jan. 2012 Aug. 2017

2009 Dec. 2013

ArchiMate 3.0
ArchiMate 2.0
•Current release
•A major release adding new features as well as •Addresses the two main developments in the
addressing feedback and comments raised An industry
upwards-compatible evolution 1) the use of architecture in strategy execution
•ArchiMate 2.0 now supports modeling throughout (digital transformation)
the TOGAF Architecture Development Method 2) the physical and IT world coming together in
trends such as the Internet of Things and Industry
4.0.
Slide 4
Relationships
Relationships | Classification
Model how elements are used
to support other elements Model behavioral dependencies
Serving between elements
Access Dependency
Influence
Triggering
Composition Dynamic Flow

Aggregation
Structural
Assignment

Realization Specialization
Others Association
Model the static construction or
Junction
composition of concepts of the
same or different types
All others which do not fall into one of
the three above categories.

Slide 15
Relationships
Structural Dependency
Relationship Definition Notation Relationship Definition Notation
Indicates that an
Composition element consists of Models that an
one or more other
concepts.
Serving
element provides
its functionality to
>
another element.
indicates that an
element groups a
Aggregation Models the ability
number of other
concepts. of behavior and
active structure
Expresses the
allocation of
Access elements to >
Assignment responsibility,
observe or act
upon passive
< >
performance of
structure elements.
behavior, or
execution. Models that an
element affects the
Links a logical implementation or
Influence +/ -
entity with a more achievement of
Realization
concrete entity that some motivation
realizes it. element.

Slide 16
Relationships
Dynamic Other
Relationship Definition Notation Relationship Definition Notation

Indicates that an
element is a
Describes a Specialization
particular kind of
temporal or
another element.
causal
Triggering
relationship Models an
between unspecified
elements relationship,
or one that is not
Association
represented by
another
ArchiMate
relationship
Transfer from one
Flow element to
Used to connect
another.
Junction relationships of
the same type.

Slide 17
Technology Layer
Technology Layer | Metamodel
This layer describes the structure and interaction of the platform
services, and logical and physical technology components.

Slide 56
Technology Layer | Active Structure Elements
● Used to model structural entities in a layer.
● Node – main active structure element
● Technology Interface
– The logical location where the technology services offered by a node
can be accessed by other nodes or by application components from
the Application Layer.
● Path
– Inter-relationships of components are mainly formed by the
communication infrastructure.
– Models the relation between two or more nodes, through which
these nodes can exchange information
● Communication Network
– Models the physical realization of a path.
– A physical communication medium between two or more devices (or
other networks)

Slide 57
Technology Layer | Active Structure Elements
● The Node element has two specializations:
– Device
models a physical computational resource, upon
which artifacts may be deployed for execution.
– System software
an infrastructural software component running on a
device.

Slide 58
Technology Layer | Active Structure Elements
Concept Definition Notation
A computational or physical resource that hosts,
Node manipulates, or interacts with other computational
or physical resources.

A physical IT resource upon which system software


Device
and artifacts may be stored or deployed for execution.

A software environment for specific types of


System Software components and objects that are deployed on it
in the form of artifacts.
Technology An aggregate of two or more nodes that work
Collaboration together to perform collective technology behavior.
Technology A point of access where technology services offered
Interface by a node can be accessed.
A link between two or more nodes, through which
Path
these nodes can exchange data or material.
A set of structures that connects computer systems or
Communication other electronic devices for transmission, routing, and
Network reception of data or data-based communications such
as voice and video.

Slide 59
Technology Layer | Example Model

Slide 60
Technology Layer | Behavior Elements
● Described in a similar way to the behavior elements of the
first two layers.

● A distinction can be made between behavior of nodes in


terms of:
– Technology Services (external)
exposes the functionality of a node to its environment
– Technology Functions (internal)
describes the internal behavior of a node

Slide 61
Technology Layer | Behavior Elements
Concept Description Notation
Represents a collection of technology
Technology Function behavior that can be performed by a
node.
Represents a sequence of technology
Technology Process behaviors that achieves a specific
outcome.

A technology interaction represents a


unit of collective technology behavior
Technology Interaction
performed by (a collaboration of) two
or more nodes.

A technology behavior element that


Technology Event
denotes a state change.

Represents an explicitly defined


Technology Service
exposed technology behavior.

Slide 62
Technology Layer | Example Model

Slide 63
Technology Layer | Passive Structure Elements
In this layer Artifact is the representation, for example, of a file,
data object, or an application component, and can be deployed
on a node.

Concept Description Notation


Artifact An artifact represents a piece of data
that is used or produced in a software
development process, or by deployment
and operation of an IT system.

Slide 64
Technology Layer | Example Model

Slide 65

You might also like