Archimate 2.

HP / 25 November 2016
 Overview
 What is Archimate?
 Why is Archimate important?
 How does Archimate relate to
TOGAF?
 How should I proceed to learn?

7/10/2019 EA 08 2
 Archimate 2.0
 A modelling language for
Enterprise Architecture
--The Open Group

 A graphical language for

representation architecture over
time (including tranformation and
migration planning) as well as their
motivation and rationale

7/10/2019 EA 08 3
 TOGAF vs Archimate
 TOGAF content meta model defines a
sufficient meta model for enteprise
architecture

 TOGAF meta model does not defines a

modelling language

 If we wish to model capability, solution

or technology architectures, TOGAF
meta model does not provide enough
concept
7/10/2019 EA 08 4
 Archimate vs TOGAF
 Archimate does define sufficient
concept for solution
architecture:
Capability  Bussiness, Application, Data,
Architecture
Technology
 Active structure, Behaviour, Passive
Solution structure
Architecture

 Archimate defines a rich set of

relationships between concepts

7/10/2019 EA 08 5
 Layer and Aspects

Products &
Services Business
Functions Organisation
Business
Information Processes

Application Data Applications

Technology Technical Infrastructure

Passive Active
structure Behaviour structure
“object” “verb” “subject”

7/10/2019 EA 08 6
 TOGAF & Archimate
Preliminary

A
Architecture
H Vision
Architecture B
Business
Change Business Business
Management Architecture Architecture

C
G Information
Requirements Data Application
Implementation
Management
Systems
Architectures Architecture Application
Architecture
Governance

F D
Technology
Migration Technology Technology
Planning E Architecture Architecture
Opportunities
and
Solutions

TOGAF ADM ArchiMate

7/10/2019 EA 08 7
 Archimate
with Extension

7/10/2019 EA 08 8
 Archimate & TOGAF
 TOGAF:
 Architecture Development Method (ADM) provides a
way of working
 Methodical support, but no description technique
 ArchiMate:
 a description language
 but no prescribed way of working

A perfect match!
 People: ITAC
 Delivery method: TOGAF
 Description language: ArchiMate

7/10/2019 EA 08 9
 Zachman & Archimate
What How Where Who When Why

Scope
Contextual
= Planner’s view

Enterprise Model Business Conceptual

= Owner’s view

Information

Attributes

language
Behaviour

Structure

Natural
System Model
= Designer’s view Application Logical

Technology Model
Physical
= Builder’s view Technology
Detailed representation
As Built
= Subcontractor’s view

Functioning Enterprise
Functioning
= User's view

7/10/2019 EA 08 10
 Architecture Community
 People and the roles that need to
talk to each other communicating
about enterprise architecture

Need
A Common
Language

7/10/2019 EA 08 11
 Benefit
 Lean and mean language:
 just enough concepts, not bloated to include
everything possible
 Well-founded concepts & models give precision
 clear communication about architectures
 get away from the ‘fuzzy pictures’ image
 Links to existing approaches
 UML, BPMN, TOGAF
 International vendor-independent standard
 The Open Group
 Tool support
 several tools available
7/10/2019 EA 08 12
 Vendor Support
 Archimate plug-in have already
been implemented by architecture
repository vendors and partners

7/10/2019 EA 08 13
 Enterprise Architecture Language

ARCHIMATE CONCEPT

7/10/2019 EA 08 14
 Layers
 A layered view provides a natural way to look at service-
oriented models. The higher layers use services that are
provided by the lower layers.
 ArchiMate distinguishes three main layers:
 The Business layer offers products and services to
external customers, which are realized in the
organization by business processes performed by
business actors and roles.
 The Application layer supports the business layer
with application services which are realized by
(software) application components.
 The Technology layer offers infrastructural services
(e.g., processing, storage and communication services)
needed to run applications, realized by computer and
communication hardware and system software.

7/10/2019 EA 08 15
 Generic Structure

External Service Interface

Object Behaviour Structure

Internal
element element

Passive Behaviour Active

structure structure

Similar concepts at each layer make the language

easier to learn and more consistent in use.

7/10/2019 EA 08 16
 Notation
 Most concepts have two notations:
 Icon
 Box with icon
 Sharp corners = structure
 Rounded corners = behaviour

 Notation resembles UML and BPMN

 to stay close to what architects already know

 Relations (arrows etc.) are also mostly taken

from existing languages, with a few exceptions

7/10/2019 EA 08 17
 Bussiness Layer

7/10/2019 EA 08 18
 Basic Element
 Business Role: Yang bertanggung jawab utk
melakukan suatu perilaku (noun)
 Business Interface: Pintu akses di mana
sebuah servis dapat disediakan ke
lingkungannya (noun)
 Business Function: Perilaku yang berdasarkan
pada suatu kriteria (sumber daya/kompetensi)
 Business Service: Layanan yang menjadi
kebutuhan bisnis bagi pelanggan
 Business Object: Elemen pasif yang relevan
dalam bisnis

7/10/2019 EA 08 19
 Sample Case
 Mahasiswa mendaftar Matakuliah

7/10/2019 EA 08 20
 Relation
 Role Mahasiswa memiliki Interface
Mahasiswa
 Role Mahasiswa melakukan Function
Mendaftar
 Interface Mahasiswa melakukan
Service Mendaftar
 Function Mendaftar merealisasikan
Service Mendaftar
 Function Mendaftar mengakses
Information Matakuliah

7/10/2019 EA 08 21
 Other Sample
 Mahasiswa mendaftar Matakuliah

7/10/2019 EA 08 22
 Other Sample

7/10/2019 EA 08 23