Case presentation TOGAF and ArchiMate for Successful...

Post on 25-Mar-2018

223 views 5 download

transcript

Case presentationTOGAF ® and ArchiMate® for

Successful Enterprise ArchitectureSuccessful Enterprise Architecture

April, 2012

Henry Franken - BiZZdesign

► Henry Franken

� 45 years old, M.Sc. & Ph.D. (cum laude)

� Happy in life ☺

� Co-founder & manager of BiZZdesign

� Chair of the ArchiMate Forum at The Open Group

� At BiZZdesign, is responsible for research and

innovation. Alignment with and contribution to open

standards are key

► Who is BiZZdesign

� BiZZdesign offers complete and integrated solutions (tools,

methods, consultancy and training) to design and improve

organizations.

� Business Model Innovation, Enterprise Architecture, Business Requirements Management and Business Process Analysis and Management are important ingredients in the solutions.

� Contributed to and edited the ArchiMate 2 specification.

� Involved in the work group working towards the next version of

TOGAF® and its alignment with ArchiMate®.

� BiZZdesign offers native tooling, consultancy and certified

training courses for TOGAF and ArchiMate.

► Agenda

� ArchiSurance case study

� Ingredients of an Enterprise Architecture approach

� The ArchiMate 2.0 language

� ArchiMate Core

� Extensions� Extensions

� Models throughout the ADM – some examples

� Benefits & Conclusions

� We have 35 minutes so it will be

an introduction - slides available!

► Agenda

� ArchiSurance case study

� Ingredients of an Enterprise Architecture approach

� The ArchiMate 2.0 language

� ArchiMate Core

� Extensions� Extensions

� Models throughout the ADM – some examples

� Benefits & Conclusions

� We have 35 minutes so it will be

an introduction - slides available!

► ArchiSurance

► The merger company: ArchiSurance

Home & AwayHomeowner’s and Travel

insurance

PRO-FIT AutoPRO-FIT Autoinsurance

LegallyYours Legal Expense insurance

► Structure of the New Company

Homeowner’s & Travel back office

Auto back officeShared

Home & Away headquarters PRO-FIT

headquarters

Front office

Auto back office

Legal Expense back office

SharedServiceCenter

► Merger creates fragmented IT Landscape…

MaintainingCustomer &

IntermediaryRelations

Contracting

LiabilityInsurance

CarInsurance

TravelInsurance

HomeInsurance

Legal AidInsurance

Web portal

Call center application

Customer relationship management system

Home & Away

Policy administration

Legal AidCRM

Business

Functions

Products

Legal Expense

CRM

Legal Expense

insurance

Homeowner’s

insurance

Travel

insurance

Liability

insurance

Auto

insurance

Products

ClaimHandling

DocumentProcessing

Policy administrationLegal Aid

backofficesystem

Document management system

Home & Away

Financial applicationFinancialHandling

Car insurance

application

Legal

Expense

BO

system

Auto Insurance

application

► Change Scenario

� Migrate to a single back-office suite for the three back-offices.

� This system will replace:

� The Policy administration system and Financial application of the Home & Away back-office

� The Auto insurance application

� The Legal Expense back-office system

� Migrate to a shared CRM 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

Call center application

Customer relationship management system

Home & Away

Policy administration Legal Aid

back

office

system

Legal AidCRM

Document management system

Home & Away

Financial application

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

Call center application

Customer relationship management system

Home & Away

Policy administration Legal Aid

back

office

system

Legal AidCRM

Document management system

Home & Away

Financial application

Business

Functions

Products

Financial

Handling

Car insurance

applicationArchiSurance

back-office system

ArchiSurance CRM system

► Agenda

� ArchiSurance case study

� Ingredients of an Enterprise Architecture approach

� The ArchiMate 2.0 language

� ArchiMate Core

� Extensions� Extensions

� Models throughout the ADM – some examples

� Benefits & Conclusions

� We have 35 minutes so it will be

an introduction - slides available!

► How about Enterprise Architecture!

Mission

Strategy

Vision

Actions

Goalsas is to be

enterprise architecture

domain/aspectarchitectures

culture

people

leadership

Operations…

peopleprocesses ITproducts

[Lankhorst et al., 2005 - Fig. 1.4. Enterprise architecture as a management instrument]

► Ingredients of a Successful EA Practice

View-

ArchiMateTOGAF

View-points

Repository, Reference Models

Process Language

► Summary of the TOGAF ADM Process

4. “Keep theprocessrunning

1. “Getting the organisationcommitted & involved”Preliminary

Phase A:

Architecture

Vision

Requirements

Management

Phase E:

Opportunities.

& Solutions

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

Planning

Phase H:

Architecture

Change

Management

Phase B:

Business

Architecture

Preliminary

Phase A:

Architecture

Vision

Requirements

Management

Phase E:

Opportunities.

& Solutions

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

Planning

Phase H:

Architecture

Change

Management

Phase B:

Business

Architecture

PreliminaryPreliminary

Preliminary

Phase A:

Architecture

Vision

Requirements

Management

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase H:

Architecture

Change

Management

Phase B:

Business

Architecture

Preliminary

Phase A:

Architecture

Vision

Requirements

Management

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase H:

Architecture

Change

Management

Phase B:

Business

Architecture

Preliminary

Phase A:

Architecture

VisionPhase H:

Architecture

Phase B:

Business

Preliminary

Phase A:

Architecture

VisionPhase H:

Architecture

Phase B:

Business

2. “Getting thearchitectureright”3. “Making the

architecturework”

& Solutions& Solutions Preliminary

Phase A:

Architecture

Vision

Requirements

Management

Phase E:

Opportunities.

& Solutions

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

Planning

Phase H:

Architecture

Change

Management

Phase B:

Business

Architecture

Preliminary

Phase A:

Architecture

Vision

Requirements

Management

Phase E:

Opportunities.

& Solutions

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

Planning

Phase H:

Architecture

Change

Management

Phase B:

Business

Architecture

Phase E:

Opportunities.

& Solutions

Governance Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

Planning Phase E:

Opportunities.

& Solutions

Governance Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

PlanningRequirements

Management

Phase E:

Opportunities.

& Solutions

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

Planning

Architecture

Change

Management

Business

Architecture

Requirements

Management

Phase E:

Opportunities.

& Solutions

Phase G:

Implementation

Governance

Phase C:

Information

Systems

Architecture

Phase D:

Technology

Architecture

Phase F:

Migration

Planning

Architecture

Change

Management

Business

Architecture

► The ArchiMate language

ArchiMate languageHigh-level modelling

within a domain

Basis forvisualisations

modelling relationships between domains

Basis foranalysisRelate to

standards

► ADM and the ArchiMate 2.0 Framework

ArchiMate core

► ArchiMate Core Summary

Bu

sin

ess

Ap

plic

atio

nA

pp

lica

tio

nTe

ch

no

log

y

Information Behaviour Structure

► ArchiMate Motivation Extension

► ArchiMate Implementation & Migration Extension

► Agenda

� ArchiSurance case study

� Ingredients of an Enterprise Architecture approach

� The ArchiMate 2.0 language

� ArchiMate Core

� Extensions� Extensions

� Some models throughout the ADM – let’s dive into it!

� Benefits & Conclusions

� We have 35 minutes so it will be

an introduction - slides available!

► Preliminary Phase

Activities in the Preliminary Phase include:

� Scope the enterprise

� Define enterprise architecture team and organisation

Identify architecture principles� Identify architecture principles

� Select and tailor architecture framework

� Implement architecture tools

P

A

RM

E

G C

B

DF

H

► Architecture Team and Organisation

P

A

RM

E

G C

B

DF

H

Architecture Principles

P

A

RM

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 � Confirm/elaborate business goals, drivers and constraints

� Develop Architecture VisionP

A

RM

E

G C

B

DF

H

► Stakeholder Analysis

P

A

RM

E

G C

B

DF

H

► Business Goals and Initial Requirements

P

A

RM

E

G C

B

DF

H

► Architecture Vision P

A

RM

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 P

A

RM

E

G C

B

DF

H

► Business Architecture

P

A

RM

E

G C

B

DF

H

► Realization of Requirements P

A

RM

E

G C

B

DF

H

► Baseline Application Architecture

P

A

RM.

E

G C

B

DF

H

► Target Application Architecture

P

A

RM.

E

G C

B

DF

H

► Application Architecture Gap Analysis

P

A

RM.

E

G C

B

DF

H

► Process-Application Support

P

A

RM.

E

G C

B

DF

H

► Information Structure View

P

A

RM.

E

G C

B

DF

H

► Data Dissemination DiagramP

A

RM.

E

G C

B

DF

H

Baseline Technology Architecture

P

A

RM

E

G C

B

DF

H

Target Technology Architecture

P

A

RM

E

G C

B

DF

H

Technology Architecture Gap AnalysisP

A

RM

E

G C

B

DF

H

► Platform Decomposition DiagramP

A

RM

E

G C

B

DF

H

► Application/Technology Support Map

P

A

RM

E

G C

B

DF

H

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

A

RM.

E

G C

B

DF

H

► Transition Architectures

P

A

RM

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

Call centerapplication

Webportal

ArchiSuranceCRM

system

Documentmanagement

system

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

Premiumcollection

Claimpayment

ArchiSuranceback-office

system

Legal AidCRM system

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

Legal AidCRM system

Webportal

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

Premiumcollection

Claimpayment

ArchiSuranceback-office

system

Documentmanagement

system

ArchiSuranceCRM

system

Call centerapplication

Webportal

► Projects for the Transitions between Plateaus

P

A

RM

E

G C

B

DF

H

► 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

P

A

RM

E

G C

B

DF

H

►Traceability

Employee costtoo high

Portfoliomanagement

Customer

Improve portfoliomanagement

Reduce workloademployees

Lack of insightin portfolio

Assign personalassistant

Reduce manual workReduce interaction

with customer

Board

Costs

Online portfoliomanagement service

Facilitateself service

More effectivecustomer interaction

Personalportfolio service

Assistant

Portfoliomanagement service

Provide onlineinformation service

Portfoliomanagementapplication

Informationservice

Product informationapplication

► Agenda

� ArchiSurance case study

� Ingredients of an Enterprise Architecture approach

� The ArchiMate 2.0 language

� ArchiMate Core

� Extensions� Extensions

� Models throughout the ADM – some examples

� Benefits & Conclusions

� We have 45 minutes so it will be

an introduction - slides available!

Tutorial ArchiMate: Wednesday 9.00

► Benefits of ArchiMate Experienced in Practice

� ArchiMate closes the gap between ‘free-format’ strategy

models and detailed solutions architecture models

� Consistent and integrated modelling:

� It is a tool for knowledge management

� It helps to integrate various (types of) models

� It enables stakeholder-specific view generation

� It enables analysisis (gap, what-if, comparison etc). � It enables analysisis (gap, what-if, comparison etc).

� Insight in the various domains, but also their interrelationships

� It is a widely accepted open standard, i.e., no vendor lock-in

� ArchiMate makes it easier to communicate with architects across

organisational boundaries, domain boundaries and between architect and designer

� Easy to use, low complexity, step-by-step increase in advanced use

► TOGAF & ArchiMate

Form a perfect basis for a tool supported

Enterprise Architecture practice!

� Specifically designed for enterprise architecture� Specifically designed for enterprise architecture

� integrated, consistent and coherent modelling in various phases

� Supports generation of compelling views for various stakeholders from a central repository

� Eases impact, gap and other types of analysis

� Eases sharing and reuse of models

► Do you want to know more?

� www.BiZZdesign.com: whitepapers, brochures and tool demo, etc.

In your bags please find: Or contact me at:

Brochure H.Franken@BiZZdesign.com