enterprise architecture modelling, visualization and analysis with archimate and...

Post on 09-Mar-2018

224 Views

Category:

Documents

4 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Enterprise Architecture Modelling, Visualization and Analysis with ArchiMate and TOGAF

Henk Jonkers22nd Enterprise Architecture Practitioners Conference

London, April 28, 2009

� What is Enterprise Architecture?

� A process� Way of working

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

� With people and resources

� A product� A design that shows the coherence between products,

processes, organisation, information supply and infrastructure, based on a vision and certainexplicit starting points, principles and preferences

� With the objective of steering changes

Process architecture

Application architecture Technical architecture

Information architecture

??

??

??

??

??

� Ingredients of an EA Approach

View-pointsProcess Language

Enterprise Continuum, Repository, Reference Models

Enterprise Continuum, Repository, Reference Models

ArchiMateTOGAF

� Architecture according to ISO/IEC 42010

� TOGAF and ArchiMate both uses the architecture definition from Standard ISO/IEC 42010:2007:

� An architecture describes:� the fundamental organisation of a system, embodied in its

components, their relationships to each other and the environment;

� and the principles governing its design and evolution.

� Practically, an architecture is represented in architectural descriptions from the viewpoints corresponding to the concerns of the stakeholders.

� Viewpoints and views (ISO/IEC 42010)

Stakeholder

Concern

SystemArchitecture

Viewpoint

Archit.description

View

Model

� Views on a shared model

Repository

P1 P2

A1 A2

S1

O1

D1 E1 F1

M1

A3

S2

A1 A2

S1

A3

S2

D1 E1 F1 √√P2

√P1

A3A2A1

P2

A2

F1

S2

� The TOGAF Components

� The ADM and ArchiMate

Technologylayer

Applicationlayer

Businesslayer

Information Behaviour Structure

� ADM Guidelines and ArchiMatePrelim.

AArch.Vision

Reqs.Mgt.

EOpport.& Solut.

GImpl.

Gov’ce

CInf. Syst.

Arch.

BBusiness

Arch.

DTechnol.

Arch.

FMigr.

Plann.

HArch. Ch.

Mgt.

ArchitectureContect Iteration

ArchitectureContect Iteration

ArchitectureGovernance

Iteration

ArchitectureGovernance

Iteration

ArchitectureDefinitionIteration

TransactionPlanningIteration

TransactionPlanningIteration

Applying iteration to the ADM

A hierarchy ofADM processes

� ADM Guidelines and ArchiMate

TOGAF, ArchiMateand SOAs

Security architectureand the ADM

� ADM Techniques and ArchiMate

Stakeholder management

Architecture patterns

� ADM Techniques and ArchiMate

Business scenarios

Gap analysis

� The ACF and ArchiMate

� Deliverables and artifacts

Deliverable

Artifact

Catalog Matrix Diagram

CRMSystem

Home & Away Financial

Application

Home & Away Policy

Administration

Documentmanagement

system

Scanningservice

Customeradministration

service

Claimsadministration

servicePrintingservice

Paymentservice

Register PayValuateAccept

Handle Claim

� Content Metamodel

� Content Metamodel and ArchiMate

BusinessRole

BusinessActor

BusinessProcess

BusinessFunction

BusinessService

ApplicationService

InfrastructureService

ApplicationComponent

DataObject Node

BusinessObject

Artifact

Value

Device

� Content metamodel and ArchiMate+

BusinessRole

BusinessActor

BusinessProcess

BusinessFunction

BusinessService

ApplicationService

InfrastructureService

ApplicationComponent

DataObject Node

BusinessObject

Artifact

Value

Device

StakeholderPrinciple

ProjectProgramme DeliverableResult

Principle

Requirement

Goal

AssessmentConcernBusiness

rule

� Core Content Metamodel

BusinessRole

BusinessActor

ApplicationService

ApplicationComponent

DataObject Node Infrastructure

Service

BusinessProcess

BusinessFunction

� TOGAF ACF and ArchiMate

� The ACF provides a global structure for architecture building blocks: it identifies the concepts needed in the different ADM phases.

� ArchiMate provides a well-defined language, including graphical notation, covering the core of the ACF.

� With ArchiMate, relations between different architectural domains can also be modelled

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

� Some concepts from the ACF are still missing in ArchiMate �potential future extensions of the language

� The Enterprise Continuum and ArchiMate

ClientInsurant

External Roles and Actors

ClaimRegistration

Service

CustomerInformation

Service

ClaimsPaymentService

External Business Services

Register Accept Valuate Pay

Handle Claim

Insurer Archisurance

Business processen and internal actors / roles

PremiumPaymentService

Customerdata mutation

Service

InsuranceApplication

Service

External Application Services

Policy DataManagement

CRMSystem

FinancialApplicationCIS

ClaimInfoServ

Application Components and Services

ClaimFiles Service

CustomerFile Service

External infrastructure services

NAS FileServer

CICS

DBMS

MessageQueing

Mainframe

UnixServer

UnixServer

Unix Server Farm

Infrastructure

� Architecture Continuum and ArchiMate

Infrastructureapplications

Businessapplications

Application programming interface

Communication infrastructure

Communiction infrastructure interface

Network services

Operating system services

System & networkmgt. services

Softwareeng. services

Securityservices

Transactionproc. services

Location &directory services

Internationaloper. services

User inter-face services

Data interch.services

Data mgt.services

Graphics &img. services

Application platform services

Qualities

ClientInsurant

External Roles and Actors

ClaimRegistration

Service

CustomerInformation

Service

ClaimsPaymentService

External Business Services

Register Accept Valuate Pay

Handle Claim

Insurer Archisurance

Business processen and internal actors / roles

PremiumPaymentService

Customerdata mutation

Service

InsuranceApplication

Service

External Application Services

Policy DataManagement

CRMSystem

FinancialApplicationCIS

ClaimInfoServ

Application Components and Services

ClaimFiles Service

CustomerFile Service

External infrastructure services

NAS FileServer

CICS

DBMS

MessageQueing

Mainframe

UnixServer

UnixServer

Unix Server Farm

Infrastructure

� TOGAF Reference Models and ArchiMate

Infrastructureapplications

Businessapplications

Application programming interface

Communication infrastructure

Communiction infrastructure interface

Network services

Operating system services

System & networkmgt. services

Softwareeng. services

Securityservices

Transactionproc. services

Location &directory services

Internationaloper. services

User inter-face services

Data interch.services

Data mgt.services

Graphics &img. services

Application platform services

Qualities

� TOGAF TRM in ArchiMate notation

Infrastructureapplications

Businessapplications

Application programming interface

Communication infrastructure

Communiction infrastructure interface

Network services

Operating system services

System & networkmgt. services

Softwareeng. services

Securityservices

Transactionproc. services

Location &directory services

Internationaloper. services

User inter-face services

Data interch.services

Data mgt.services

Graphics &img. services

Application platform services

Qualities

� Case study: Models throughout the ADM

CFO

Costeffectiveness

Reusable IT services

User

Ease ofuse

Uniform user interface

Flexibility

Servicedepartment

AcceptRegister PayValuate

Handle Claim

DamageOccured

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

Premiumcollection

Claimpayment

ArchiSurance back-office system

Document management system

ArchiSuranceCustomer Relations Management system

Call centerapplication

Web portal

Claim Form

Customer File

Damage ClaimInsurance Policy

Customer

InsuranceRequest

Legal aid Insurance Policy

Liability Insurance Policy

Travel Insurance Policy

Car Insurance Policy HomeInsurance Policy

Customer FileData

Damage ClaimData

Insurance PolicyData

Insurance RequestData

ArchiSurancebackoffice

back-up server

ArchiSurancebackoffice

server

ArchiSurancebackofficeapplication

Web server

Webportal

Genericapplication server

DMSapplication

CRMapplication

Callcenter

application

ArchiSuranceLAN

Transition Architecture A:

Single CRM system,multiple backoffice systems

Transition Architecture B:

Multiple CRM systems,single backoffice system

BaselineArchitecture

TargetArchitecture

Primacy ofprinciples

Maximize benefitto the enterprise

Information managementis everybody's business

Businesscontinuity

Common use ofapplications

Compliancewith law

IT responsibility

Protection ofintellectual property

Business principlesData is an

asset

Data isshared

Data isaccessible

Datatrustee

Common vocabularyand data definition

Datasecurity

Data principles

Technologyindependence

Ease ofuse

Application principles

Requirements-basedchange

Responsive changemanagement

Control technicaldiversity

Interoperability

Technology principles

Primacy ofprinciples

Maximize benefitto the enterprise

Information managementis everybody's business

Businesscontinuity

Common use ofapplications

Compliancewith law

IT responsibility

Protection ofintellectual property

Business principlesData is an

asset

Data isshared

Data isaccessible

Datatrustee

Common vocabularyand data definition

Datasecurity

Data principles

Technologyindependence

Ease ofuse

Application principles

Requirements-basedchange

Responsive changemanagement

Control technicaldiversity

Interoperability

Technology principles

Project A

Integration ofCRM systems

TransitionArchitecture A

BaselineArchitecture

� Case study introduction: ArchiSurance

� ArchiSurance: a 3-company merger

ArchiSurance Home &Travel insurances

PRO-FIT Carinsurances

LegallyYours LegalAid insurances

The “new”ArchiSurance

� Structure of the new company

Front-office

Home & Away back-office

Car back-office

Legal Aid back-office

� Main IT systems of ArchiSurance

MaintainingCustomer &

IntermediaryRelations

ClaimHandling

Contracting

DocumentProcessing

LiabilityInsurance

CarInsurance

TravelInsurance

HomeInsurance

Legal AidInsurance

Web portal

Call center application

Customer relationship management system

Home & AwayPolicy administration

Legal Aidbackofficesystem

Legal AidCRM

Document management system

Home & AwayFinancial application

BusinessFunctions

Products

FinancialHandling

Car insurance application

� Proposed change

� Develop a single back-office system (for policy administration and financial handling) to be used by the three back-offices.

� This system will eventually 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

� The separate CRM system of Legal Aid will also disappear

MaintainingCustomer &

IntermediaryRelations

ClaimHandling

Contracting

DocumentProcessing

LiabilityInsurance

CarInsurance

TravelInsurance

HomeInsurance

Legal AidInsuranceWeb portal

Call center applicationCustomer relationship management system

Home & AwayPolicy administration Legal Aid

backofficesystem

Legal AidCRM

Document management system

Home & AwayFinancial application

BusinessFunctions

Products

FinancialHandling

Car insurance application

MaintainingCustomer &

IntermediaryRelations

ClaimHandling

Contracting

DocumentProcessing

LiabilityInsurance

CarInsurance

TravelInsurance

HomeInsurance

Legal AidInsuranceWeb portal

Call center applicationCustomer relationship management system

Home & AwayPolicy administration Legal Aid

backofficesystem

Legal AidCRM

Document management system

Home & AwayFinancial application

BusinessFunctions

Products

FinancialHandling

Car insurance application

ArchiSuranceback-office system

ArchiSurance CRM system

� Architecture principles

Primacy ofprinciples

Maximize benefitto the enterprise

Information managementis everybody's business

Businesscontinuity

Common use ofapplications

Compliancewith law

IT responsibility

Protection ofintellectual property

Business principlesData is an

asset

Data isshared

Data isaccessible

Datatrustee

Common vocabularyand data definition

Datasecurity

Data principles

Technologyindependence

Ease ofuse

Application principles

Requirements-basedchange

Responsive changemanagement

Control technicaldiversity

Interoperability

Technology principles

Primacy ofprinciples

Maximize benefitto the enterprise

Information managementis everybody's business

Businesscontinuity

Common use ofapplications

Compliancewith law

IT responsibility

Protection ofintellectual property

Business principlesData is an

asset

Data isshared

Data isaccessible

Datatrustee

Common vocabularyand data definition

Datasecurity

Data principles

Technologyindependence

Ease ofuse

Application principles

Requirements-basedchange

Responsive changemanagement

Control technicaldiversity

Interoperability

Technology principles

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

++

�Stakeholders, concerns and business goals

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

++

CFO

Cost-effectiveness

ReusableIT services

User

Ease ofuse

Uniformuser interface

Flexibility

Servicedepartment

� Architecture Vision

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

�Baseline & target Business Architecture: Business Roles & Functions

Customer

Customer's Bank

AssetManagement

ClaimsHandling

Contracting

FinancialHandling

MaintainingCustomerRelations

MaintainingIntermediary

Relationscustomer

informationcontract

info

money

contractinfo.

assetinfo

Insurer

Intermediary

ProductInformationCustomerInformation

cust.info

productinfo.

claims

insuranceinfo

claiminfo

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

�Baseline & target Business Architecture: Business Processes

AcceptRegister PayValuate

Handle Claim

DamageOccured

CreateContract

FormaliseRequest

Check and Sign Contract

Close Contract

Request forInsurance

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Baseline application architecture

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

Home & Awaypolicy administration

Premiumcollection

Claimpayment

Home & Awayfinancial application

Claimdata mgt.

Policydata mgt.

Claimpayment

Premiumcollection

Car insuranceapplication

Claimdata mgt.

Policydata mgt.

Premiumcollection

Claimpayment

Legal aidback-office system

Document management system

Customer Relations Management system

Call centerapplication

Legal Aid CRM system

Web portal

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

Premiumcollection

Claimpayment

ArchiSurance back-office system

Document management system

ArchiSuranceCustomer Relations Management system

Call centerapplication

Web portal

Target application architecture

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Gap analysis application architecture

Claimdata mgt.

Policydata mgt.

Riskassess-

ment

ArchiSuranceback-office system

Premiumcollection

Claimpayment

Home & Awayfin. application

Claimdata mgt.

Policydata mgt.

Claimpayment

Premiumcollection

Car insuranceapplication

Claimdata mgt.

Policydata mgt.

Premiumcollection

Claimpayment

Legal aidback-office system

Document management system

ArchiSuranceCustomer Relations Management system

Call centerapplication

Legal Aid CRM system

Web portal

both in Baseline and Target application architectureonly in Baseline application architectureother parent

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Business-application alignment

DamageOccured AcceptRegister PayValuate

Handle Claim

ArchiSuranceback-office

system

Call centerapplication

Documentmanagement

system

Acceptcall

Storedocument

Registerclaim

Enterassessment

Calculateamount Pay

(Fragment, for the target architecture)

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Baseline & target data architecture

Claim Form

Customer File

Damage ClaimInsurance Policy

Customer

InsuranceRequest

Legal aid Insurance Policy

Liability Insurance Policy

Travel Insurance Policy

Car Insurance Policy HomeInsurance Policy

Customer FileData

Damage ClaimData

Insurance PolicyData

Insurance RequestData

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Baseline technology architecture

Home & Awayapplication server

Carapplication server

Legal aidapplication server

Legal aidbackofficeapplication

Legal aidCRM

application

Home & Awaypolicy admin.

Home & Awayfinancial app.

Carinsuranceapplication

Web server

Webportal

Genericapplication server

DMSapplication

CRMapplication

Callcenter

application

ArchiSuranceLAN

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Target technology architecture

ArchiSurancebackoffice

back-up server

ArchiSurancebackoffice

server

ArchiSurancebackofficeapplication

Web server

Webportal

Genericapplication server

DMSapplication

CRMapplication

Callcenter

application

ArchiSuranceLAN

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Gap analysis technology architecture

Home & Awayapplication server

ArchiSurancebackoffice

server

ArchiSurancebackofficeapplication

Legal aidCRM

application

Home & Awaypolicy admin.

Home & Awayfinancial app.

Carinsuranceapplication

Web server

Webportal

Genericapplication server

DMSapplication

CRMapplication

Callcenter

application

ArchiSuranceLAN

Carapplication server

ArchiSurancebackoffice

back-up server

both in Baseline and Target application architectureonly in Baseline application architectureonly in Target application architecture

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Application-technology alignment

ArchiSurancebackofficeapplication

Webportal

DMSapplication

CRMapplication

Callcenter

application

ArchiSuranceback-office

system

Documentmanagement

system

ArchiSuranceCRM

system

Call centerapplication

Webportal

(For the target architecture)

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

� Transition architectures

Transition Architecture A:

Single CRM system,multiple backoffice systems

Transition Architecture B:

Multiple CRM systems,single backoffice system

BaselineArchitecture

TargetArchitecture

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

++

� Transition architectures

Transition Architecture A:

Single CRM system,multiple backoffice systems

Transition Architecture B:

Multiple CRM systems,single backoffice system

BaselineArchitecture

TargetArchitecture

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

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

Project A

Integration ofCRM systems

Project B

Integration ofback-office systems

TransitionArchitecture A

BaselineArchitecture

TargetArchitecture

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

++

� Requirements modelling

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

++

On-line portfolio management

Enableclaim handling

Enable buyinginsurances Enable premium

payments

Provide on-lineinformation

Buyinsurance

Apply forinsurance

Handleapplication

Receivecontract

Createcontract

<<include>><<include>>

� Requirements traceability

Decrease of personnelbudget

IntroduceSOA paradigm

Leavingcustomers

Lack ofinsight

Profit Customersatisfaction

Service & ITdepartment

Innovation

Senior management

Droppedsales

On-line portfolio management

Increase sales Increase

customersatisfaction

Increaseinsight

Bad portfoliomanagement

Improveportfolio

management

Enableclaim handling

Enable buyinginsurances Enable premium

payments

Lack of SOAknowledge

Acquire SOAKnowledge

Use on-lineservices

Budget

Provide on-lineinformation

Buyinsurance

Buy insuranceservice

Buy insuranceprocessApply for

insurance

Handleapplication

Contract creationservice

Receivecontract

Createcontract

Application assessmentservice

<<include>><<include>>

Decrease of personnelbudget

IntroduceSOA paradigm

Leavingcustomers

Lack ofinsight

Profit Customersatisfaction

Service & ITdepartment

Innovation

Senior management

Droppedsales

On-line portfolio management

Increase sales Increase

customersatisfaction

Increaseinsight

Bad portfoliomanagement

Improveportfolio

management

Enableclaim handling

Enable buyinginsurances Enable premium

payments

Lack of SOAknowledge

Acquire SOAKnowledge

Use on-lineservices

Budget

Provide on-lineinformation

Buyinsurance

Buy insuranceservice

Buy insuranceprocessApply for

insurance

Handleapplication

Contract creationservice

Receivecontract

Createcontract

Application assessmentservice

<<include>><<include>>

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

++

� Gap analysis TOGAF and ArchiMate

� Supported by ArchiMate:� Business architecture� Application architecture� Data architecture� Technology architecture� Transition architectures

� Possible extensions:� Architecture principles� Stakeholders, concerns and

business goals� Projects and deliverables� Requirements

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

Prelim.

A

Reqs.Mgt.

E

G C

B

DF

H

++

� Summary: ArchiMate en TOGAF

� Share the same definition of (Enterprise) Architecture

� Viewpoints as a central concept

� Use of the service concept� Both managed by The Open

Group� Complement each other� Use of both is growing rapidly� Gaps between ArchiMate and

TOGAF will be closed

� Conclusion: TOGAF OR NOT TO GAF…

… that shouldn’tbe a question…

… togetherwith ArchiMate…

A perfect match!

top related