Iasa UK Archimate Overview

Delivering Enterprise Architecture

with TOGAF® and ArchiMate®

Enterprise Architecture using open standards

Harmen van den Berg, BiZZdesign

BiZZdesign in one slide…

Tools Consultancy

TrainingBest practices

� Design tools for EA and BPM

� Monitoring tools for Governance

� Publication via InSite Portal

� Architecture, Business and IT

� Project Management

� Design / modeling

� ArchiMate®

� TOGAFTM

� Reference models

� Foundation

� Practitioner

� Certification

� Accredited by The Open Group

� Powerfull

� User friendly

� Experienced

� Certified

� Practical

� Open standards

� Personal attention

� Practical focus

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)

Flickr by neil nathansonTOGAF is an instrument for producing and using Enterprise Architecture

What is Enterprise Architecture?

• A discipline, with the objective ofsteering changes

• A product

– A design that shows the coherence betweenproducts, processes, organisation, informationsupply and infrastructure, based on a vision andcertain explicit starting points, principles and preferences

• A process

– Way of working

– Aimed at the development and use of enterprisearchitectures within an enterprise

– With people and resources

Process architecture

Application architecture Technical architecture

Information architecture

?

Ingredients of an EA Approach

View-

pointsProcess Language

Enterprise Continuum, Repository, Reference Models

ArchiMateTOGAF

Question

How to cook an egg?

Number of stepsWay of describingStart of processEnd 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?

Process architecture

Application architecture Technical architecture

Information architecture Product architecture

?

?

?

?

?

The ArchiMate Language

ArchiMate languageHigh-level modelling

within a domain

modelling relations between domains

Basis forvisualisations

Basis foranalysesRelate to

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

Technology

Application

Business

Environment

Passive

“object”

Behaviour

“verb”

Active

“subject”

Processdomain

Informationdomain

Datadomain

Organizationdomain

Productdomain

Application domain

Technical infrastructure domain

ArchiMate core and extensions

• ArchiMate ‘core’

( = ArchiMate 1.0)

– Business

– Applications

– Technology

• Two extensions in ArchiMate

2.0

• Implementation & migration

extension

– Programs and projects

– Plateaus

• Motivation extension

– Stakeholders, drivers and

goals

– Principles

– Requirements

ArchiMate Core

Motivation

Extension

Implementation &

Migration

Extension

Extension for

…

Summary of ArchiMate 2.0 CoreB

usin

ess

Ap

plic

atio

nTe

ch

no

log

y

Passive structure Behavior Active structure

Some examples of the ArchiMate language for

“educational purposes”

Examples created using BiZZdesign Architect

Products and services

PremiumService

PaymentService

InsurancePolicy Damage insurance

PolicyService

Beinginsured

Policy mutationService

DeclarationService

Customer

Business services

Contract Product Value Role

Aggregation

Association

Processes and roles

Accept andRegister claim

Specialist Car damage

Assess claimDamagenotification

Pay claim

Taxateur Employee FinanceAdministrative employee

:-)customer

Event Process

Role

Event

Triggering

Assignment

Business functions

Product development

Risk management

Treasury

Asset management

Customer changes

Contract changes

Contracting

MarketingSystem development

Assessment

Acceptance

Claims handling

Collecting

Facturation

Financial handling

Customer relations

Composition

(by nesting)

Business Function

Business objects

Lifeinsurance

InsuranceInsurancerequest

Travel insurance Damage insurancePensioninsurance

Damagedata

Damageform

Business objectRepresentation

Aggregation

Specialization

Realization

Applications and application services

Assessmentservice

Acceptationsystem

AcceptationService

Registrationsysteem

Paymentsystem

RegisterService

AcceptationInterface

Customer administrationsystem

Assessmentsystem

Assess claimAccept andRegister claim

Applicationservice

Applicationcomponent

Applicationinterface

Business

process

Used-by

Realization

Composition

Infrastructure


ClaimFiles Service

CustomerFile Service

Acceptationsystem

DBMS

MessageQueing

CICS

MainframeNAS FileServer

LAN UnixServer 1

UnixServer 2

Unix Server Farm

FirewallProfit

Applicationcomponent

Infrastructureservice

Node

DeviceNetwork

System

software

Used-by

Realization

Assignment

Composition

Example: Layered view

PaymentService

Customer administrationservice

DeclarationService

Accept andRegister claim

AcceptationService

Pay claim

Assessmentservice

Damagenotification

:-)customer

Assess claim

Acceptationsystem

Assessmentsystem


Messagingservice

ClaimFiles Service

Paymentsystem

MessageQueing

DBMS CICS

Mainframe

CustomerFile Service

NAS FileServer

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


Work packages / projects



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!”

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

Views on a shared model

A1 A2 A3

P1 √

P2 √ √

Repository

P1 P2

A1 A2

S1

O1

D1 E1 F1

M1

A3

S2

A1 A2

S1

A3

S2

D1 E1 F1

P2

A2

F1

S2

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

architect,

software

developer,

business process

designer

Deciding

Designing Informing

Details

Coherence

Overview

product manager,

CIO, CEO

customer,

employee,

others

Goal

Goal

Conte

nts

Conte

nts

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

Transactionentry

Bill

creation

Financial ApplicationFinancial Application

Take out insurance

Receiverequest

Processrequest

Collectpremium

Requestinsurance

RequestInvoice

Class

diagram

Component

diagram

Activity diagram

Link detailed models to ArchiMate models

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

Front-office

Home & Away back-office

Car back-office

Legal Aid back-office

Fragmented IT Landscape

MaintainingCustomer &

IntermediaryRelations

ClaimHandling

Contracting

DocumentProcessing

LiabilityInsurance

CarInsurance

TravelInsurance

HomeInsurance

Legal AidInsurance

Web portal

Call center application

Customer relationship management system

Home & Away

Policy administrationLegal Aid

backofficesystem

Legal AidCRM

Document management system

Home & Away

Financial application

Business

Functions

Products

FinancialHandling

Car insurance

application

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

Maintaining

Customer &

Intermediary

Relations

Claim

Handling

Contracting

Document

Processing

Liability

Insurance

Car

Insurance

Travel

Insurance

Home

Insurance

Legal Aid

InsuranceWeb portal



Home & Away

Policy administration Legal Aid

back

office

system

Legal AidCRM


Home & Away


Business

Functions

Products

Financial

Handling

Car insurance

application

Maintaining

Customer &

Intermediary

Relations

Claim

Handling

Contracting

Document

Processing

Liability

Insurance

Car

Insurance

Travel

Insurance

Home

Insurance

Legal Aid

InsuranceWeb portal



Home & Away

Policy administration Legal Aid

back

office

system

Legal AidCRM


Home & Away


Business

Functions

Products

Financial

Handling

Car insurance

applicationArchiSurance

back-office system

ArchiSurance CRM system

The ADM

Summary of the ADM process

2. “Getting the

architecture

right”3. “Making the

architecture

work”

4. “Keep the

process

running

1. “Getting the organisation

committed & involved”

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

• Implement architecture tools

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Architecture Team and Organization

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Architecture Principles

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

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

• Develop Architecture Vision

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Stakeholder Analysis

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Business Goals and Initial Requirements

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Current and future goals

Architecture Vision

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

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

Reqs.

Mgt.

E

G C

B

DF

H

Business Architecture

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Realization of Requirements

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Business functions

Realization of requirements in processes

Baseline Application Architecture

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Target Application Architecture

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Application Architecture Gap Analysis

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Application Communication Diagram

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Process-Application Support

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Processes and applications in time

Information Structure View

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Information: business objects in time

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Data Dissemination Diagram

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Baseline Technology Architecture

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Target Application Architecture

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Technology Architecture Gap AnalysisPrelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Unintentional

omission

Platform Decomposition Diagram

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Application/Technology Support Map

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

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

Reqs.

Mgt.

E

G C

B

DF

H

Transition Architectures

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

ArchiSuranceback-office

systemPremiumcollection

Claimpayment

Home & Awayfin. application

Claimdata mgt.

Policydata mgt.

Claimpayment

Premiumcollection

Car insuranceapplication

Claimdata mgt.

Policydata mgt.

Premiumcollection

Claimpayment

Legal aidback-office system

Documentmanagement

system

ArchiSuranceCRM

system

Call centerapplication

Webportal


Webportal

ArchiSuranceCRM

system

Documentmanagement

system

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

Premiumcollection

Claimpayment


system

Legal AidCRM system

Claimdata mgt.

Policydata mgt.

Riskassess-

ment


systemPremiumcollection

Claimpayment

Home & Awayfin. application

Claimdata mgt.

Policydata mgt.

Claimpayment

Premiumcollection

Car insuranceapplication

Claimdata mgt.

Policydata mgt.

Premiumcollection

Claimpayment

Legal aidback-office system

Documentmanagement

system

ArchiSuranceCRM

system


Legal AidCRM system

Webportal

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

Premiumcollection

Claimpayment


system

Documentmanagement

system

ArchiSuranceCRM

system


Webportal

Projects for the Transitions between Plateaus

Prelim.

A

Reqs.

Mgt.

E

G C

B

DF

H

Application roadmap

Transition Application landscape

2012

2016

Roadmap and projects

Added value of projects

0

100

200

300

400

500

600

700

800

900

0 50000 100000 150000

Ad

de

d v

alu

e

Costs

Project scores

Project P1 High-revenue mutual fund

using integrated asset management

Project P2 High-revenue mutual fund

Project P3 Set-up integrated asset

management

Project P4 Integrate asset management

Project P5a Enable internet as a channel

Project P5b Add internet as a channel

Project P6 Integration of local ordering

services

Project P7 Integration of local reporting

services

Project P8 Real-time asset reporting

Project P9 Real-time asset monitoring

Compare scenario’s

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

0

50

100

150

200

250

300

350

400

200000 250000 300000 350000 400000

Ad

de

d v

alu

e

Costs

Scenario scores

1a-2a-3a

1a-2a-3b

1a-2b-3a

1a-2b-3b

1b-2a-3a

1b-2a-3b

1b-2b-3a

1b-2b-3b

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

Reqs.

Mgt.

E

G C

B

DF

H

ArchiMate provides traceability

Summary of the ADM process

2. “Getting the

architecture

right”3. “Making the

architecture

work”

4. “Keep the

process

running

1. “Getting the organisation

committed & involved”

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

Implementation & Migration

Business layer

Application layer

Technology layer

Information Behavior Structure MotivationPhase A:

ArchitectureVision

Preliminary

RequirementsManagement

Phase H:Architecture

ChangeManagement

Phase E:Opportunities& Solutions

Phase F:MigrationPlanning

Phase G:Implementation

Governance

Phase B:Business

Architecture

Phase C:Information

SystemsArchitectures

Phase D:TechnologyArchitecture

ArchiMate 1.0

Examples ArchiMate use

From various companies:

City of Enschede

TATA Steel

SNS Reaal

Example: Enschede

Registrerenadressen/straten

Wijzigenadressen/straten

Afmeldenstraten/adressen

Registrerengebieden

Wijzigen gebieden

Afmeldengebieden

ADR4all

ADR4all database

Adres

Straat

Huisnummer +letter + toevoeging

PostcodeWijk

Stadsdeel

BuurtGebied

Staatnaamgeving (Basisregistratie Vastgoed)

Vaststelling huisnummers (Basisregistratie Vastgoed)

Product

Application with functions

Application

data objects

Database

Example: Enschede

Registrerenbodemonderzoeken

Registrerenbodemverontreininging

Registrerenlocaties onderzoek

Registrerenpotentieel vervuilde

locatie

Managementrapportages

BIS4all

BIS4all database

SUB4all (voor BIS4all)

Kadastrale gegevens

Adres

Analyseresultaten

Boorgegevens

Peilbuisgegevens

Kosten

Soort

Status

Subject

Bodeminformatie

Geografischeinformatie

Vergunning /besluit

ADR4all database

GDSKAD4all database

Geografischecontouren

SUB4all database voor BIS

ArcView

Bestanduitvoerder

bodemonderzoek

Import XMLbodemonderzoeksdata

Export naar XML

SIKB tool

Wet-bodembescherming (Uitvoering Milieu)

Bodemsanering (Uitvoering Milieu) Bodemonderzoek (Uitvoering Milieu) Controle bodem (Handhaving milieu)

Example: Enschede

BIS4allAan- en verkoopboek DHV RioolbeheerADR4all BWT4all MelddeskBeheersysteem onroerend goed

VR-BeheerVerwervingsysteem Plan32RBSRioolkaartenSpeeltoestel DHV WegbeheerPIV4all DHV Basisbeheer

G4net

Applicaties

Verblijfplaats

Postcode

Locatie

Huisnummer +letter + toevoeging

Huisnummer Adreshistorie

Adres

Straat

Gegevensobjecten die met adressen / locaties te ameken hebben

Melddesk databaseADR4all database

VR-Beheer database Beheersysteem database

Speeltoesteldatabase

Databaserioolkaarten

Plan32 database DHVdatabase

PIV4all database Aan- en verkoopboek database

RBS databaseVerwervingssyteem database

G4net database

Onderliggende databases

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?

Cost development

2012 2014 2016

Infrastructurecosts

Architecturerepository

Contract administration

Planningadministration

Adding cost related information

Breakdown costs per application

∆€ ∆€ ∆€ ∆€

∆€ ∆€

∑€

Example Application costs

Infrastructure costs

143

Cost heatmap

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

– [email protected]

– +31 53 4878 151

– +31 6 5119 8282