►

Delivering Enterprise Architecture

with TOGAF® and ArchiMate®
Enterprise Architecture using open standards

Harmen van den Berg, BiZZdesign

► BiZZdesign in one slide…

Powerfull
Experienced
Tools
User friendly
Consultancy
Certified

Design tools for EA and BPM
Architecture, Business and IT

Monitoring tools for Governance
Project Management

Publication via InSite Portal
Design / modeling

Practical
Personal attention

Best practices
Open standards
Training
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 is TOGAF9 certified?

Who is TOGAF8 certified?

Who has ever attended a TOGAF training course?

Who is using ArchiMate?

Who has heard of ArchiMate before this seminar?

Who is a business or IT architect?

Who just discoverd he or she is in the wrong room?….
► What are we talking about?

Created with Wordle.net

► Proposed schedule

Introduction

Enterprise Architecture

ArchiMate

Core language

Extensions

TOGAF

ADM

TOGAF and ArchiMate

Case example

Conclusions
►

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 producing and using Enterprise Architecture

Flickr by neil nathanson
► What is Enterprise Architecture?

A discipline, with the objective of Information architecture

steering changes Process architecture

A product ?

A design that shows the coherence between Application architecture Technical architecture

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

View-
Process 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

A language for describing architectures

Covers business, application and technology
layers

With relations between these layers

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

See www.opengroup.org/archimate or
www.archimate.org
► 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 Summary
Business
Application
Technology

Information Behaviour Structure

► ArchiMate core and extensions

ArchiMate ‘core’
Implementation & migration extension
( = ArchiMate 1.0)
Programs and projects

Business
Periods

Applications
Motivation extension

Technology
Stakeholders, concerns and goals

Two extensions in
Principles
ArchiMate 2.0
Requirements

Motivation Implementation & Extension for

Extension Migration …
Extension

ArchiMate Core
►

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
Register claim
Assess claim Business
process
Register Acceptation Assessment
Application
Service Service service
service

Registration
systeem
Assessment
system
Application
component
Customer administration
system

Used-by Payment Acceptation Acceptation Application

system system Interface
Realization interface
Composition
► Infrastructure
Acceptation
system
Customer administration
system
Application
component
Claim Customer Infrastructure
Files Service File Service
service

NAS File
Mainframe Server
System CICS

software Unix Server Farm Node

Message LAN Unix Unix
Queing Server 1 Server 2 Device
Used-by Network
Realization
DBMS
Assignment Firewall
Profit
Composition
► 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
► Motivation extension
Concept Definition

An individual, team, or organization with an interest in the outcome

of the architecture

Something that creates, motivates, and fuels the change in an

organization (earlier called “concern”)

The outcome of the analysis of some concern, revealing the

strengths, weaknesses, opportunities, or threats that may trigger a
change to the enterprise architecture
Some end that a stakeholder wants to achieve

A general desired property that guides the design and evolution of

systems in a given context

A desired property that must be realized by a system

28
► ArchiMate Motivation Extension
► Motivation extension

Board Stakeholder Keep digital Support claim

records of claims registration

Customer
satisfaction Driver
Claim Registration
data service Website
Lack of insight Assessment
Registration
system
Increase insight
in portfolio
Goal

Improve overview
of current insurances
Support online
insurance mutations
Requirement

Better overview Support online

claim status claim handling
► Aggregation (Decomposition)
► Conflict and Contribution
► Implementation and migration extension

33
► ArchiMate Implementation & Migration Extension
► ArchiMate Implementation & Migration Extension
► ArchiMate and support

Low entrée level

Free format in Visio/OmniGraffle stencils

Archi

ArchiMate is commercially supported

By certified tool vendors

BiZZdesign: Architect

Casewise: Corporate Modeler

IDS Scheer: Aris ArchiMate Modeler

Telelogic: System Architect

Troux: Metis

By a large number of service providers like Atos
Origin, BiZZdesign, Capgemini, Getronics,
Logica, Sogeti, Ordina,…

Certification for individual architects and
training is in progress
► 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
► Refer detailed models to your 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
► 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
►

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

49
► 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

organisation

Identitfy architecture principles

Select and tailor architecture framework Prelim .

Implement architecture tools A
H B

Reqs.
G C
Mgt.

F D
E
► Architecture Team and Organisation

Prelim .
H
A B

Reqs.
G C
Mgt.

F D
E
► Architecture Principles

Prelim .
H
A B

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
constraints
Prelim .

Develop Architecture Vision
A
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
► 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

Conduct formal stakeholder review Prelim .

A
H B
Reqs.
G C
Mgt.

F D
E
► Business Architecture
Prelim .
A
H B
Reqs.
G C
Mgt.

F D
E
► Realisation of Requirements
Prelim .
A
H B
Reqs.
G C
Mgt.

F D
E
► 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
► Information Structure View
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
► 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 Home & Away Car insurance Legal aid

back-office fin. application application back-office system
system

.
Claim Premium Claim Premium Claim Premium
data mgt. Risk collection data mgt. collection data mgt. collection
assess-
ment Call center Web

Call center Web

Policy
data mgt.
Claim
payment
Policy
data mgt.
Claim
payment
Policy
data mgt.
Claim
payment application portal Prelim
application portal

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

ArchiSurance Home & Away Car insurance Legal aid

A
back-office fin. application application back-office system ArchiSurance
system
Claim
data mgt. Risk
assess-
Premium
collection
Claim
data mgt.
Premium
collection
Claim
data mgt.
Premium
collection
back-office
system
Risk H B
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

Document
management
system
Document Reqs.
ArchiSurance Legal Aid management
G C
CRM
system
CRM system system
Mgt.

ArchiSurance
back-office
system
Risk
F D
Policy
data mgt.
Claim
data mgt.
assess-
ment
Premium
collection
Claim
payment E
Document
management
system
► Projects for the Transitions between Plateaus

Prelim .
A
H B

Reqs.
G C
Mgt.

F E
D
► 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
►Traceability
Customer
Board

Portfolio
Costs
management

Lack of insight Employee cost

in portfolio too high

Reduce workload
Improve portfolio employees
management

Assign personal Reduce interaction

Reduce manual work
assistant with customer

Personal
portfolio service
Facilitate More effective
self service customer interaction

Online portfolio
Assistant management service Provide online
information service

Portfolio Information
management service service

Portfolio
management Product information
application application
► 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!
► ADM and Extended ArchiMate Framework
► Content Metamodel
► TOGAF ACF and ArchiMate
► TOGAF ACF and ArchiMate

ArchiMate with extensions provides a well-defined language,

including graphical notation, covering most of the ACF

With ArchiMate, relations between different architectural
domains can also be modeled

ArchiMate models form a basis for views, visualizations, and
analysis

ArchiMate with extensions is very suitable to represent the
viewpoints that TOGAF defines, and thus supports the ADM

Some minor modifications or extensions to the metamodels
are recommended to complete the match
► ArchiMate: Adding Value to TOGAF

Integrated, consistent and coherent modelling in various phases

Specifically designed for enterprise architecture

Full support for viewpoints (predefined and user-defined)

Not just the ‘boxes’, but also their interrelationships

Explicit support for the service paradigm

Concrete, visible results for various stakeholders can be generated
from a repository

Analysis (e.g. impact-of-change and gap analysis)
made easy
►

Conclusions and benefits experienced

AND SOME TIPS….

► ArchiMate is more than drawing diagrams

Consistent and integrated

modelling…

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…

The Open Group

www.opengroup.org

ArchiMate
www.opengroup.org/archimate
www.archimate.org

TOGAF 9
http://www.opengroup.org/architecture/t
ogaf9-doc/arch/

ArchiMate 1.0
http://www.opengroup.org/archimate/d
oc/ts_archimate/

www.bizzdesign.com
► Want to know more?

ArchiMate

Participate in one of our ArchiMate training courses

Foundation or Practitioner

TOGAF

Participate in one of our TOGAF training courses

Level 1 and/or level 2

Come to our booth today!

►

Thank you!

Harmen van den Berg

BiZZdesign

[email protected]
+31651198282
http://www.bizzdesign.com