Delivering Enterprise Architecture

with TOGAF® and ArchiMate®

Enterprise Architecture using open standards

Harmen van den Berg, BiZZdesign

 BiZZdesign in one slide…

Tools
Powerfull Consultancy
Experienced

User friendly
Certified

Design tools for EA and BPM
Architecture, Business and IT

Monitoring tools for Governance
Project Management

Publication via InSite Portal
Design / modeling

Practical Training
Personal attention

Best practices

Open standards
Practical focus

Foundation

ArchiMate®

Practitioner

TOGAFTM

Certification

Reference models

Accredited by The Open Group
Let’s get to know each other!

Raise your hand:

• Who has ever attended a TOGAF training course?

• Who is TOGAF9 certified?
• Who has not heared of ArchiMate before this seminar?
• Who is using ArchiMate?
• Who is ArchiMate certified?
• Who is a business or IT architect?
• Who just discoverd he or she is in the wrong room?….
Proposed schedule

• Introduction
• Enterprise Architecture
• ArchiMate
– Core language
– Extensions
• TOGAF
– The ADM
• TOGAF and ArchiMate
– Examples ArchiMate models
– Examples typical analysis with ArchiMate
• Conclusions
• Coffee!
 Enterprise Architecture

Remco Koolhaas - Seattle Public Library

 Why Enterprise Architecture?

• Managing change and complexity:

– Aligning business and IT
– Outsourcing
– Impact analysis
– Project support (project start
architectures)
– Portfolio management
– Communication with stakeholders
– …
• Obtaining insight in current
situation (as-is)

TOGAF is an instrument for producingFlickr by neilEnterprise

and using nathanson Architecture
What is Enterprise Architecture?
Information architecture

Process architecture

?
• A discipline, with the objective of
Application architecture

steering changes Technical architecture

• A product
– A design that shows the coherence between
products, processes, organisation, information
supply and infrastructure, based on a vision and
certain explicit starting points, principles and preferences
• A process
– Way of working
– Aimed at the development and use of enterprise
architectures within an enterprise
– With people and resources
 Ingredients of an EA Approach

TOGAF ArchiMate

Process View-
Language
points

Enterprise Continuum, Repository,

Reference Models
 Question

Number of steps
Way of describing
Start of process
How to cook an egg? End of process
The process of cooking an egg…
Why one process and language?

• Communication
• No ambiguity
• Coherence
• Consistency
• Visualization
• Analysis
• …
 ArchiMate®

The open standard for modeling

enterprise architecture
Do you recognize this?

Information architecture Product architecture

?

Process architecture

?
?
?
Application architecture Technical architecture

?
The ArchiMate Language

High-level ArchiMate language

modelling
within a
Basis for
domain
visualisations

modelling relations Basis for

Relate to analyses
between domains
standards
ArchiMate

• Language for describing enterprise architecture

• Covers business, application and technology
– With relations between these layers
• Extensions for
– Motivation
– Migration and implementation
• Graphical language with formal semantics, enabling analysis
and tool support
• Techniques for visualization and analysis, aimed at various
stakeholders
• Open standard maintained by The Open Group
Layers, Aspects, and Domains

Environment
Product
domain
Information Process Organization
Business domain domain domain

Data
Application Application domain
domain

Technology Technical infrastructure domain

Passive Behaviour Active

“object” “verb” “subject”
 ArchiMate core and extensions

• ArchiMate ‘core’ • Implementation & migration

( = ArchiMate 1.0) extension
– Business – Programs and projects
– Applications – Plateaus
– Technology • Motivation extension
• Two extensions in ArchiMate – Stakeholders, drivers and
2.0 goals
– Principles
– Requirements
Motivation Implementation & Extension for
Extension Migration …
Extension

ArchiMate Core
 Summary of ArchiMate 2.0 Core
Business
Application
Technology

Passive structure Behavior Active structure

Some examples of the ArchiMate language for
“educational purposes”

Examples created using BiZZdesign Architect

 Products and services

Contract Product Value Role

Insurance
Policy Being Customer
Damage insurance insured

Policy mutation Payment Policy Premium Declaration

Service Service Service Service Service

Business services
Aggregation
Association
 Processes and roles

Event Process Event

Damage Accept and Assess claim Pay claim :-)

notification Register claim customer

Administrative employee Taxateur Employee Finance

Specialist Car damage Role

Triggering
Assignment
 Business functions

System development Marketing Product development Customer relations

Financial handling Claims handling Asset management Contracting

Facturation Assessment Risk management Contract changes

Collecting Acceptance Treasury Customer changes

Business Function

Composition
(by nesting)
 Business objects

Insurance Insurance Damage

request data

Damage
Life Travel insurance Pension Damage insurance form
insurance insurance

Representation
Business object
Aggregation
Specialization
Realization
 Applications and application services

Accept and Assess claim Business

Register claim process

Application
Register Acceptation Assessment
Service Service service service

Registration Assessment Application

systeem system component

Customer administration
system

Used-by Application
Payment Acceptation Acceptation
Realization system system Interface interface
Composition
 Infrastructure

Acceptation Customer administration Application

system system
component

Infrastructure
Claim Customer
Files Service File Service service

NAS File
Mainframe Server
System CICS
software Node
Unix Server Farm
LAN
Message Unix Unix Device
Used-by Queing
Network
Server 1 Server 2

Realization
Assignment DBMS
Firewall
Composition Profit
Example: Layered view
Declaration Payment
Service Service

Accept and
Damage Register claim Assess claim Pay claim :-)
notification customer

Acceptation Assessment Customer administration

Service service service

Payment Acceptation Assessment Customer administration

system system system system

Messaging Claim Customer

service Files Service File Service

Mainframe
NAS File
Message DBMS CICS Server
Queing
The ArchiMate extensions

Motivation extension
Implementation and Migration extension
ArchiMate Motivation Extension

• Models stakeholders, drivers for change, business goals,

principles and requirements, and their relationships
• Mainly addresses the needs of the early TOGAF phases
and the Requirements Management process
• Inspired by standards and existing techniques such as
OMG’s Business Motivation Model, KAOS, i*
• Supports traceability between motivations and other
architectural components
ArchiMate Motivation Extension
Examples
Examples
Examples
Influence Relationship
Implementation & Migration Extension

• Models projects, programs, plateaus and gaps

• Mainly addresses the needs of the later phases of the
TOGAF ADM cycle
• Supports
– Management of individual projects and project portfolios
– Gap analysis
– Transition and migration planning
• Supports traceability between projects and other
architectural components
ArchiMate Implementation & Migration
Extension
Example Implementation & Migration

Plateaus
Example Implementation & Migration

Work packages / projects

Example Implementation & Migration
Example Implementation & Migration
More complex plateau / project view
Viewpoints and views

Stakeholder communication
Less is more…

“let’s ask the architect to leave out this rubbish, then we will get a
nice result!”
 Views on a shared model

P2
S1 S2

S2
A1 A2 A3

A1 A2 A2 A3
P1 √
D1 E1 F1
F1
P2 √ √

M1 P1 P2 O1

S1 S2

A1 A2 A3

Repository D1 E1 F1
Viewpoints and views (ISO/IEC 42010)
Typical stakeholders for EA

• Upper-level management
• Middle-level management
• End user
• Architect
• Operational manager
• Project manager
• System developer
• System administrator
• …
Stakeholder: not only a role!

• A stakeholder is a person, with personal interests

• Investigate your stakeholder
– Presentation or conversation?
– Words or pictures?
– Details or overview?
– Cartoons or UML-diagrams?
– PowerPoint, Word, or Excel?
– Golf, basketball, football ,or soccer?
– Cars or bicycles?
– …
• Find the stakeholders’ sweet spot!
 Classification viewpoints ArchiMate
product manager,
CIO, CEO

architect, Deciding
software

Goal
developer, customer,
business process employee,
designer Designing others
Informing

Contents
Details

Coherence

Overview
Viewpoint Goals

• Viewpoints for designing

– typically used by architects in the design process
– Examples: Application diagram, Process diagram
• Viewpoints for deciding
– intended to support managers in making decisions
– Examples: landscape map, cross-reference table, analysis
report
• Viewpoints for informing
– inform stakeholders about an architecture
– Examples: process illustration, animation, cartoon
Level of Detail

• Details
– small part of an architecture with high level of detail
– e.g. for a software engineer designing and implementing a
component, or process owner responsible for optimizing a process
• Coherence
– spans multiple aspects or layers and shows their relations
– e.g. for an operational manager responsible for IT support for a
number of business processes
• Overview
– abstract, comprehensive view of multiple aspects and layers
– for enterprise architects and upper-level managers
Inspiration: SQVID
Different ways to look at an apple(ication)
 Views vary on the SQVID-dimensions

• Think about these dimensions before creating views:

– What does your stakeholder need?
– Support his concerns, not your own!
Summary ArchiMate

• Language for describing enterprise architecture

• Covers business, application and technology
– With relations between these layers
• Extensions for
– Motivation
– Migration and implementation
• Graphical language with formal semantics, enabling analysis
and tool support
• Techniques for visualization and analysis, aimed at various
stakeholders
• Open standard maintained by The Open Group
ArchiMate and other languages

• ArchiMate: perfect starting point for MDA and software

development
– ArchiMate incorporates the service paradigm
– ArchiMate has implementation relationships to process
modelling languages (BPNM, BPEL)
– ArchiMate has implementation relationships to software
engineering design languages (UML)
• ArchiMate connects architectural domains
– It has a broader scope, but less detail than UML and BPMN
– It does not replace specialized languages for different
architectural domains, such as UML, BPMN and others
 Link detailed models to ArchiMate models

Take out insurance

Request
insurance Receive Process Collect
request request premium

Activity diagram
Component Invoice
Request
Transaction Bill
diagram entry creation Class
diagram

Financial Application

Detailled models in UML, BPMN, also pay attention to the relation to less formal
modelling in Powerpoint and Visio
Why not dive straight into UML?

• Business people just don’t understand

it!
• Not designed for enterprise
architecture
• Lack of integration of business,
application and technical
infrastructure aspects
• Too many details
• No explicit service paradigm
• Many diagrams = many models
– ArchiMate works with views on one
model
ArchiMate certification

Overview certification program

Certification

• People certification
– To ensure that people are knowledgeable about ArchiMate
– Results in becoming ArchiMate certified @ The Open Group
– Requires training course from an accredited training provider
• Successfully complete a practical exercise during the training
• Successfully complete a multiple choice exam during the training
• Examination is only available of part of an accredited ArchiMate
training course
• Training accreditation
– Only accredited training providers can provide certification
• Tool certification
– To guarantee that tools support the ArchiMate language
ArchiMate Tool Certification

• Minimal requirements for ArchiMate tools:

• Concept Coverage
– All concepts from Core and Extensions
• Relationship Coverage
– Alle relationships from Core and Extensions
• Language notation
– Notation, syntax and semantics
– Nesting as alternative for relations
• Viewpoint support
– All viewpoints supported
– Reuse objects and relations on different views
– Different grafical notations on different views
• Language extension mechanism
– Adding attributes and specialisations of concepts and relations

59
ArchiMate Tool Certification

• Recommanded capabilities of ArchiMate tools:

• Concept Coverage
– Predefined specialisations
– Additional concepts (outside ArchiMate)
• Relationship Coverage
– Predefined specialisations
– Additional relationships (outside ArchiMate)
• Language notation
– Alternative notations
• Other capabilities

60
TOGAF
What is TOGAF?

• TOGAF is an architecture framework

• A framework that structures EA descriptions by
– Describing the process leading to the architecture.
– Discerning relevant viewpoints and modelling techniques;
– Indicating which elements should be part of an architecture
model (this part is limited in TOGAF)
What else is TOGAF?

• A vendor- and technology-independent framework

• Best practices and knowledge gathered from experienced experts
worldwide
• The result of almost 15 years of development
• The description of a systematic series of steps and processes for
the creation and description of IT architectures
• A collection of checklists at different levels – from business
requirements to infrastructure components
• Information freely available through the web site of The Open
Group
• Free use within your own organisation
• For commercial use, a “commercial license” is required (included in
the membership of the Architecture Forum of The Open Group)
Why TOGAF as an architecture framework?

• A common process for developing and using architecture

• Represents best practice in architecture development
• By using TOGAF, architectures are developed that:
– Are consistent
– Reflect the needs of stakeholders
– Employ best practice
– Give consideration both to current requirements and to likely
future needs of the business
• Combines well with ArchiMate
• Developed through a collaborative effort of >300
Architecture Forum members
The Structure
of TOGAF
The TOGAF Components
 ArchiSurance

A case for applying the ADM

ArchiSurance

ArchiSurance Home &

Travel insurances
Structure of the New Company

Home & Away back-office

Car back-office
Front-office

Legal Aid back-office

Fragmented IT Landscape

Products
Business Home Travel Liability Car Legal Aid
Insurance Insurance Insurance Insurance Insurance
Functions
Web portal
Maintaining
Customer & Call center application
Intermediary Legal Aid
Relations Customer relationship management system CRM

Contracting
Home & Away
Policy administration
Legal Aid
Claim
Car insurance back
Handling application office
system
Home & Away
Financial application
Financial
Handling

Document Document management system

Processing
 Proposed Change

• Migrate to a single back-office system for the three back-

offices.
• This system will replace:
– The Policy administration system and Financial application of the
Home & Away back-office
– The Car insurance application of the Car back-office
– The Legal aid back-office system
• Migrate to a shared CRM system
Products Products
Business Home Travel Liability Car Legal Aid Business Home Travel Liability Car Legal Aid
Insurance Insurance Insurance Insurance Insurance Insurance Insurance Insurance Insurance Insurance
Functions Web portal Functions Web portal
Maintaining Maintaining
Call center application Call center application
Customer & Legal Aid Customer & Legal Aid
Intermediary Customer relationship management system Intermediary Customer relationship management system
Relations
CRM
Relations ArchiSurance CRM systemCRM
Contracting Home & Away Contracting Home & Away
Policy administration Legal Aid Policy administration Legal Aid

Claim
Car insurance
application
back
office Claim
ArchiSurance Car insurance
application
back
office
Handling Handling
Home & Away
Financial application
system
back-office system
Home & Away
Financial application
system

Financial Financial
Handling Handling

Document Document management system Document Document management system

Processing Processing
The ADM
 Summary of the ADM process

1. “Getting the organisation

committed & involved”

4. “Keep the
process
running

2. “Getting the
architecture
3. “Making the right”
architecture
work”
Preliminary Phase

Activities in the Preliminary Phase include:

• Scope the enterprise
• Define enterprise architecture team and organization
• Identify architecture principles
• Select and tailor architecture framework Prelim .
• Implement architecture tools A B
H

Reqs.
G C
Mgt.

F D
E
Architecture Team and Organization

Prelim .

A B
H

Reqs.
G C
Mgt.

F D
E
Architecture Principles

Prelim .

A B
H

Reqs.
G C
Mgt.

F D
E
Phase A: Architecture Vision

Activities in the Preliminary Phase include:

• Establish the architecture project / define scope
• Identify stakeholders, concerns, and business
requirements
• Confirm/elaborate business goals, drivers and
Prelim .
constraints
A
• Develop Architecture Vision H B

Reqs.
G C
Mgt.

F D
E
Stakeholder Analysis

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
Business Goals and Initial Requirements

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
Current and future goals
Architecture Vision

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
Phases B, C, D: “Getting the Architecture
Right”

Activities in Phases B, C and D include:

• Select reference models, viewpoints and tools
• Develop Baseline Architecture
• Develop Target Architecture
• Perform gap analysis Prelim .
• Conduct formal stakeholder review A
H B
Reqs.
G C
Mgt.

F D
E
Business Architecture

Prelim .

A
H B
Reqs.
G C
Mgt.

F D
E
Realization of Requirements

Prelim .

A
H B
Reqs.
G C
Mgt.

F D
E
Business functions
Realization of requirements in processes
Baseline Application Architecture

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
Target Application Architecture

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
Application Architecture Gap Analysis

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
Application Communication Diagram

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
Process-Application Support

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
Processes and applications in time
Information Structure View

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
 Information: business objects in time

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
Data Dissemination Diagram

Prelim .

A
H B

Reqs.
G
Mgt. C

F D
E
Baseline Technology Architecture

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
Target Application Architecture

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
Technology Architecture Gap Analysis
Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E

Unintentional
omission
Platform Decomposition Diagram

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
Application/Technology Support Map

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
Application lifecycle management
Alternative view on ALM
Cost heatmap application landscate
Alternative views and animations
Phases E, F, G: “Making the Architecture
Work”

Activities in Phases E, F and G include:

• Review/consolidate gap analysis results
• Formulate implementation & migration strategy
• Identify/group/prioritise main projects/work packages
• Identify Transition Architectures
• Generate Architecture Implementation Roadmap Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
 Transition Architectures

Call center Web

application portal

ArchiSurance
CRM
system

ArchiSurance
back-office
system
Claim
data mgt. Risk
assess-
Home & Away
fin. application
Premium
collection
Car insurance

Claim
application

data mgt.
Premium
collection
Legal aid
back-office system
Claim
data mgt.
Premium
collection
Prelim .
ment Call center Web
Policy Claim Policy Claim Policy Claim
data mgt. payment data mgt. payment data mgt. payment application portal
Call center Web
application portal

Document
ArchiSurance
CRM
Legal Aid
CRM system
management
system
ArchiSurance
CRM
system
A
system

H B
ArchiSurance Home & Away Car insurance Legal aid
back-office fin. application application back-office system ArchiSurance
system back-office
Claim Premium Claim Premium Claim Premium
Risk
data mgt.
assess-
collection data mgt. collection data mgt. collection system
Risk
Policy
ment
Claim Policy Claim Policy Claim
Call center Web Policy Claim
assess-
Premium Claim
data mgt. data mgt. collection payment
data mgt. payment data mgt. payment data mgt. payment application portal ment
Reqs.
Document G C
management
system
Document
Mgt.
ArchiSurance Legal Aid management
CRM CRM system system
system

F D
ArchiSurance
back-office
system
Risk
E
Policy Claim Premium Claim
assess-
data mgt. data mgt. collection payment
ment

Document
management
system
Projects for the Transitions between Plateaus

Prelim .

A
H B

Reqs.
G C
Mgt.

F E
D
Application roadmap
Transition Application landscape

2012

2016
Roadmap and projects
Added value of projects
Project scores
900
Project P1 High-revenue mutual fund
800 using integrated asset management
700 Project P2 High-revenue mutual fund
600
Added value

Project P3 Set-up integrated asset

500 management
400 Project P4 Integrate asset management
300
200 Project P5a Enable internet as a channel

100
Project P5b Add internet as a channel
0
0 50000 100000 150000
Project P6 Integration of local ordering
Costs
services
Project P7 Integration of local reporting
services
Project P8 Real-time asset reporting

Project P9 Real-time asset monitoring

Compare scenario’s

Scenario scores
400
1a-2a-3a
350
1a-2a-3b
300
1a-2b-3a
Added value
250
200 1a-2b-3b

150 1b-2a-3a
100 1b-2a-3b
50 1b-2b-3a
0
1b-2b-3b
200000 250000 300000
Costs 350000 400000

Scenario Added value Costs Completion (month) Risk

1a-2a-3a 201,9864 285000 12 high
1a-2a-3b 276,0936 370000 12 high
1a-2b-3a 223,3208 285000 12 medium
1a-2b-3b 297,428 370000 13 medium
1b-2a-3a 236,4264 220000 10 high
1b-2a-3b 310,5336 305000 10 high
1b-2b-3a 257,7608 220000 10 low
1b-2b-3b 331,868 305000 13 low
Phases H & RM: “Keep the process
running”

Activities in Phase H and the RM process:

• Baseline requirements and monitor them
• Identify changed requirements
• Assess impact of changed requirements

Prelim .

A
H B

Reqs.
G C
Mgt.

F D
E
ArchiMate provides traceability
 Summary of the ADM process

1. “Getting the organisation

committed & involved”

4. “Keep the
process
running

2. “Getting the
architecture
3. “Making the right”
architecture
work”
Key points of the ADM

• The ADM is iterative:

– Over the whole process
– Between phases
– Within each phase

• The ADM is a generic method

– Intended to be used in a wide variety of enterprises in different
sectors
– The process can be adapted for specific situations, e.g., a
specific sector
ArchiMate and TOGAF

A strong combination!
 TOGAF ADM and ArchiMate 2.0

Preliminary

Phase A:
ArchiMate 1.0
Architecture Information Behavior Structure Motivation
Vision
Phase H: Phase B:
Architecture Business
Change
Management
Architecture
Business layer

Phase C:
Phase G: Information
Implementation
Governance
Requirements
Management
Systems Application layer
Architectures

Phase F:
Migration
Phase D:
Technology
Technology layer
Planning Architecture
Phase E:
Opportunities
& Solutions
Implementation & Migration
Examples ArchiMate use

From various companies:

City of Enschede
TATA Steel
SNS Reaal
Example: Enschede

Vaststelling huisnummers Staatnaamgeving Product

(Basisregistratie Vastgoed) (Basisregistratie Vastgoed)

ADR4all

Registreren Registreren Application

adressen/straten gebieden

Wijzigen Wijzigen
with functions
adressen/straten gebieden

Afmelden Afmelden
straten/adressen gebieden

Straat Stadsdeel

Application
Huisnummer +
Adres Gebied Buurt data objects
letter + toevoeging

Wijk
Postcode

ADR4all
database
Database
Example: Enschede
Bodemsanering (Uitvoering Milieu) Bodemonderzoek (Uitvoering Milieu) Wet-bodembescherming Controle bodem (Handhaving milieu)
Bestand (Uitvoering Milieu)
uitvoerder
bodemonderzoek

SIKB tool BIS4all SUB4all

(voor BIS4all)

Import XML Registreren Registreren Registreren

bodemonderzoeksdata bodemonderzoeken locaties onderzoek bodemverontreininging

Export naar XML Registreren Managementrapportages ArcView

potentieel vervuilde
locatie

Analyseresultaten

Peilbuisgegevens

Boorgegevens

Status

Bodeminformatie Geografische
contouren

Soort

Kosten

Vergunning /
besluit Adres Kadastrale Geografische Subject
gegevens informatie

BIS4all database ADR4all KAD4all database GDS SUB4all database

database voor BIS
 Example: Enschede

Applicaties

Aan- en verkoopboek Verwervingsysteem VR-Beheer Beheersysteem Speeltoestel BIS4all PIV4all ADR4all Rioolkaarten RBS DHV Basisbeheer DHV Rioolbeheer DHV Wegbeheer BWT4all Plan32 Melddesk
onroerend goed

G4net

Gegevensobjecten die met adressen / locaties te ameken hebben

Verblijfplaats
Adres
Straat Locatie

Huisnummer Adreshistorie

Postcode

Huisnummer +
letter + toevoeging

Onderliggende databases

G4net database Speeltoestel Verwervingssyteem RBS database ADR4all VR-Beheer database PIV4all database Beheersysteem Aan- en verkoopboek Database Plan32 database Melddesk database DHV
database database database database database rioolkaarten database

Which data is used by which application, and stored in which database

TATA Supply Chain Transformation
In Scope of SCT
SCT Level 0 process flow
Capturing mapping to application landscape (fragment)
SCT Level 0 Process flow and mapping to
application landscape
High level App. Landscape / data flows
Core data flows
HTML report – Navigate through all views and documentation
SNS Reaal: Context and process models
Application and infrastructure models

132
Additional
properties for
applications
Application landscape with ALM advice
Conversion roadmap
Detailed decommissioning roadmap
Transition Application landscape

2012

2016
What about cost development?

2012 2014 2016

Cost development
Adding cost related information

Contract Planning Infrastructure

administration administration costs

Architecture
repository
Breakdown costs per application

∆€ ∆€ ∆€ ∆€

∑€

∆€ ∆€
Example Application costs
Infrastructure costs
Cost heatmap

143
Conclusions and benefits experienced

AND SOME TIPS….

ArchiMate is more than drawing diagrams

• Consistent and integrated modeling…

– Is a kind of knowledge management
– helps to integrate various (types of) models
– enables stakeholder specific view generation
– enables analyses
• Insight in the various domains and the relations
between these
• Easy to use, low complexity, step-by-step growth
in advanced use

Position ArchiMate as an umbrella language for integrated high level

modelling and analyses over various domains
ArchiMate is a start - not an endpoint

• Open Standard is a “save choice”

• Think big, start small
– There are many possible
concepts and relations;
– Select and learn;
• Training is required to fully benefit
– 2 day training is a suitable start
• Implementing ArchiMate means
a change in how architects work.
– Takes time
– Communication
Consider the implementation of ArchiMate as a project…
Include change management aspects
Modelling efforts should be integrated

• With the EA process

– TOGAF ADM or any other
• With EA governance
– Validate the models
• With other modelling efforts
– Process modelling
– Software modelling
– …
When embedding EA (and ArchiMate) in the organization, work from the
perspective of products and deliverables!
ArchiMate is useful to...

• Bridge the gap between

“free-format” strategy
models and detailed
solutions architecture models
• Enhance communication
• Makes models analyzable
• Have a common basis for
more detailed modelling
• Well supported by tools and
service-providers
Relate your ArchiMate models to your operating model or
business model when communicating to C-level
More information?

• ArchiMate: www.opengroup.org/archimate
– Information on the ArchiMate language
– Free download of the ArchiMate specification (html or pdf)
– Information on certification
• Van Haren publishers: www.vanharen.net
– Pocket guide ArchiMate
– ArchiMate 2.0 specification (hard copy or ePub)
• BiZZdesign: www.bizzdesign.nl / www.bizzdesign.com
– Information on our training offerings
– Information on the tool Architect
– Information on our consultancy offerings
Thanks!

• Thank you for attending this event!

• Feel free to contact me if you have any questions or

remarks

– h.vandenberg@bizzdesign.nl
– +31 53 4878 151
– +31 6 5119 8282