Post on 03-Jan-2017
1
ArchiMate:
A Modeling Language for
Enterprise Architecture
From the book :
“Enterprise Architectureat Work – Modeling,Communication
and Analysis”
By Marc Lankhorst et. al
Telematica Instituut
The Netherlands
See www.archimate.com
+ artikkel: “Enterprise Modeling”
INF5120
F7 – part 2: March 5th, 2007
Overview
• Introduction
• Enterprise architecture & ArchiMate
• The ArchiMate modeling language
– Integration of business, applications, and
technology
– Service orientation
– Example
• Communicating architectures
• ArchiMate adoption in practice
2
Partners Telematica Instituut
Enterprise Architecture & ArchiMate
3
Context
• Business and ICT become closer
• Ever higher demands on ICT: complexity, flexibility
• Many changes, rapid time-to-market required
• Management & control difficult
• Architecture as a tool
– for communication
– for governance
– for innovation
Architecture
IEEE Std 1471:
Architecture = structure(s) of a system
in terms of
• components,
• their externally visible properties,
• their relations,
• and the underlying principles
“Structure with a vision”
4
Governance With Architecture
• Architecture is a strategic tool
– not just high-level design
– Architecture goes beyond ICT: enterprise
architecture
• Stability & flexibility
– Seem to be contradictory, but a good architecture
facilitates change!
• Communication with stakeholders
– architects, managers, customers, engineers, …
• Analysis
– impact-of-change
– cost & performance
Mission
Goals
Strategy
Actions
Vision
as is to be
enterprise architecture
domain/aspect
architectures
culture
people
leadership
Operations…
peopleprocesses ITproducts
Role of Enterprise Architecture
5
Enterprise Architecture: Describing Coherence
Process architecture
Application architecture Technical architecture
Information architecture Product architecture
?
?
?
?
?
Better Support for the Enterprise Architect
• Increasing need for precise documentation on the
enterprise architecture level
– Integrating various models in many languages
(UML, IDEF, BPMN, ARIS, ...)
• Communicating about architecture with others
• Tool interoperability
• Needed: well-founded and practical standard for
enterprise architecture modeling
6
Analysis
ArchiMate Focus
Integration
Visualization
What Has ArchiMate Delivered?
• A vision on enterprise architecture
– Focus on the relations between
business and IT
• A language for describing architectures
– models give precision and
make tool support possible
• Techniques for visualisation and analysis, aimed at
various stakeholders
• A basis and vision for tools
– Visio stencils
• Long term goal: vendor-independent standard for
architecture description
7
Integrated Modelling
Integration
• An architecture might encompass for example:
– products
– organisation
– business processes
– applications
– systems
This requires concepts for domains and relations,
linked with existing techniques
8
The ArchiMate Language
ArchiMate languageHigh-level modelingwithin a domain
Modeling relations between domains
Basis forvisualizations
Basis foranalyses
Layers, Aspects, and Domains
Technology
Application
Business
Environment
Information Behavior Structure
Processdomain
Informationdomain
Datadomain
Organizationdomain
Productdomain
Application domain
Technical infrastructure domain
9
Generic Structure at Each Layer
Internal
External
Information Behavior Structure
Business Functions and Actors
business function
Insurance
policies
flow
Contracting Claim
Handling
ArchiSurance
business actor
assignment
10
product
Travel Insurance
Policy
contract
Product and Services
SecurityCustomer
business rolevalue
Customerinformation
service
Insurance
application
service
Claimregistration
service
Claimregistration
service
Claimpaymentservice
business service
Business Process
Handle Claim
PayValuateAcceptRegisterDamageoccurred
event
Notification
access
business
object
Customer Information
service
Claimpaymentservice
business service
realisation
Claim registration
service
Customerbusiness actor
used by
Insurant business role
business process
11
Business Interactions
CustomerArchiSurancebusiness actor
business interaction
Register
Insurantbusiness role
Insurer
aggregationClaim registration
partners
business collaboration
assigment
Information
specialisation
Car insurance policy
Home insurance policy
Travel insurance policy
Liability insurance policy
Legal aid insurance policy
aggregation
Customer file
Customer
composition
Damage claimInsurance policyInsurance request
realisation
Claimform
representation
12
Business Layer Metamodel
Business
actor
Business
role
Business object
Value
Business
service
Event
Business
interface
Business
process /
function /
interaction
Contract
Product
RepresentationBusiness
collaboration
Meaning
Application Concepts
Policy
administration
Financial
administration
application component
Premium
collectionPolicy
creation application function
application interaction
Policy
creation
service
applicationservice application
interface
Customer
file
data
Policy
datadata object
13
Application Usage by BusinessProcesses
Handle claim
Registration PaymentValuationAcceptanceNotifi-
cation
Financialapplication
Policyadministration
administrationCustomer
service
Paymentservice
CRMsystem
Claim
serviceadministration
Notifi-
cation
data
Application Layer Metamodel
14
Technology Concepts
zSeries Mainframe Sun Blade
device
Database
tables
Fin.application
EJBs
artifact
Databaseaccessservice
MQmessaging
serviceInfrastructure service
DB2Database
iPlanetApp. server
system software
LAN
network
association
Deployment of Applications
Financialapplication
Policyadministration
CRMsystem
Notifi-
cation
data
zSeries Mainframe
DB2Database
Sun Blade
iPlanetApp. server
Databaseaccessservice
MQ messaging
service
Databasetables
Fin.application
EJBsLAN
15
Technology Layer Metamodel
Artifact
Infrastructure
interface
Infrastructure
service
Node
DeviceSystem
softwareNetwork
Communication
path
LayeredArchitecture
Infrastructure
External infrastructure services
Application components and services
Roles and actors
External application services
External business services
Damage claiming process
Client Insurant InsurerArchiSurance
Registration PaymentValuationAcceptance
Customer
informationservice
Claims
paymentservice
Customer
administration
service
Payment
service
CRM
system Financial
application
Customer
information
service
Claim
registrationservice
Claim
registrationservice
Claims
administration
service
Policy
administration
Claim
files
service
zSeries mainframe
DB2database
Financial
applicationEJBs
Customer
files
service
Sun Blade
iPlanetapp server
Claiminformation
service
Business layer
Application layer
Technology layer
16
Services as Binding Concept
External
business service
Internal
business service
Internal
infra. service
External
infra. service Technology
Application
Business
Customer
External
application service
Internal
application service
ArchiMate in Practice: Tax Administration - UWV
17
Service-Oriented Business Process Integration
Payroll tax return
Company/Agent
Submittax return
Tax and Customs Administration
UWV
Transfertax return
data Processpayroll tax
return UWV
Processpayroll taxreturn TCA Process
corrections
Process Refinement
Process payroll tax returnTCA
Payroll tax return
Correctionrequest
Receive tax return
Collectionsadministration
Levyingsadministration
Confirmation
Levy
Notificationrejection
Notificationerror
NotifyProcess
corrections
Relationsinformation
Submittax return
Tax and Customs Administration
Transfertax return
data
Sendnotification
Processcorrections
18
Detailed Process with Application Support
Receive tax return
Receive electronic PTR
Medium- independent processing
Nominativedata
FOS
MOS UKV
internal
messaging
AVANTi
Temporary
storage file
DCS
Notification
FOL
convertreceive and
check
handle
discards
make
available
notify receipt
BvR BBA WGA
Receive paper PTRReceive
PTR
document
Receive
PTR small
Receive
PTR large
Receive
PTR web
large:
0,17 %
Scan
document
decodesmall:
98,10%
web:
1,72 %
OB 2000
PTR
msg.
Paper
PTR
Electronic PTR
Legal archive
F = 22 000/
month
F = 638 000/
month
FOS
external
FOS
internal
Process – Detailed Applications
Medium- independent processing
FOS Internal
AVANTi
PTR processingStructural conversion
Convert Receive
and check
Handle
discards
Notify
receipt
PTR
file
Receive
message
Receive PTR
UKV internal
messaging
Send
PTR
Make
availableSend
nominative lines
XML-
message
conversion
& splitting
10%
Collective
partNominative
part
Nominative
lines
Collective
lines
Medium
independent
PTR
PTR
Data
Message
Conversion
Message
Reception
19
Applications – Infrastructure
MOS
MTA in P44 in
BAPI
unpack
MQ
dispatch PTR data
OB2000Sybase
access
Ch. MOS
->FOS
APMOSU7- MOS
production
SybaseDBMS
BS
App.
hosting
Execution
environment
QM
APFOSU 4- FOS
internal production
QM
FOS internal
Message
switch
Discards
administration
P44 discards-
handling
MQ
messaging
Total Infrastructure
DBtoegangCICS
APFOSU4-FOSintern productie,
APFOSU3Unix-cluster: UKV intern
BerichtenserverP-partitie-Mainframe (Exploitatie Particulieren
en Ondernemingen)
Ch. FOS ->Msg. Store
Ch. AVANTi->UKV
MQmessaging
QM
MQmessaging
QMQPE2
QMQPE1QM
XIB
App.hosting
Executie-omgeving
MQmessaging
MB
DB2UAVIDB01
CICSpoort
fabriek
Berichten-switch
MQ Poort cluster
MQmessaging
DBtoegang
MB
Unix Server -Message Store
Messagedatabase
QM
Ch.FOS->Avanti
Mesg.broker
Mesg.broker
APFOSU1-FOS extern productie,
APFOSU2
BS
FBXGateway
MQmessaging
Ch.Avanti->Msg. Store
OpvolgerOB2000
Sybasetoegang
APMOSU7-MOS productie
SybaseDBMS
BS
App.hosting
Executie-omgeving
Berichten-switch
Ch. MOS->FOS
MQmessaging
QM
Ch. DCS->FOS
Document Conversie Systeem
MQmessaging
QM
BS
Berichten-switch
App.hosting
Executie-omgeving
Ch. FOL->FOS
FOL -FormulierenOnline (2 of 3)
MQmessaging
QM
BS
Berichten-switch
App.hosting
Web Application
server
UKV intern bericht
Message store
FOSinternMOS AVANTi
FOS Extern
DCS
FOL
Uitval-Admin.
Messageadmin.
Admin.
20
Communicating Architectures
Views & Viewpoints
• A viewpoint describes the set of concerns of one or
more stakeholders. It defines how to build a view, e.g.
by means of a template.
• A view is a representation of a system from a
viewpoint. A view is what you see, looking from the
perspective of the stakeholder and his/her concerns.
21
Viewpoints Classification
architect,software
developer,business process
designer
Deciding
Designing Informing
Details
Coherence
Overview
product manager,
CIO, CEO
customer,employee,
others
Viewpoints for Designing
• Basic design viewpoints
– Organisation
– Business function
– Business process
– Information structure
– Application structure
– Application behaviour
– Infrastructure
• Resemble ‘diagrams’ of
e.g. UML
– Actor coordination
– Product
– Service realisation
– Business process
coordination
– Application usage
– Application coordination
– Implementation &
deployment
22
Application BehaviourApplication Behaviour
Home & Away Policy administration
Policy creation
Calculate
premium
Calculate
risk
Create
policy
Store
policy
Policy
creation
service
Customer fileInsurance policyInsurance request
Viewpoints for Deciding
• Give a high-level overview for e.g. business managers
• Can be used to identify problems or possible
improvements
• Example: Landscape map
– 2-D representation
– Possibly interactive
23
MaintainingCustomer &
IntermediaryRelations
ClaimHandling
Contracting
DocumentProcessing
LiabilityInsurance
CarInsurance
TravelInsurance
HomeInsurance
Legal AidInsurance
Web 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
FinancialHandling
Car insurance
application
Landscape map ArchiSurance
Viewpoints for Informing
• Process illustration
• Goal is communication
• Pictures aimed at
‘non-architects’Archief
$$Kluis
Bestand
bericht
document
24
Process Illustration (I)
Application components
Infrastructure
Roles
External Organisational services
BPM process
Douane
eenheidInning
Klant
behandelingadiministratie
Aangifte
betaling
Aangifte
adiministratie
RIN
Aangifte
behandeling
BPMclient
BPM server
(BCICT)
BPM
workstation
(Douane-eenheid)
RDWBCICTParticulier
Fiattering
RIN server
(Inning)WAN W AN
Vordering
Betaling
Administratie
Balie
Catalogus
Waarde
Aangiftebestand
BPM
server
Kluis Archief
inning
Inning
Geldaangifte
Process Illustration (II)
BPM
aangiftepunt
Douane eenheidBPM
17ex2
Inning
RDW
Administratie
BCICT
automatiserings
centrum
Balie
Behandeling
Archief
$$Kluis
Catalog.
waarde
Aangifte
Bestand
BPM
workstation
(Douane
eenheid)
BPM
server(BCICT)
RIN
server
(Inning)
BPM17
ex3
BPM17
ex1
Inningvordering
betaling
aangifte
betaling
betaling
acceptgiro
25
ArchiMate Adoption
ArchiMate and TOGAF
• TOGAF: The Open Group Architecture Framework
– Provides methodical support for architects
– Architecture Development Method (ADM) gives
you a process
• ArchiMate and TOGAF nicely complement each other:
– ArchiMate provides no architecture process
– TOGAF provides no architecture modelling
technique
• E.g. Atos Origin NL use ArchiMate and TOGAF
together
26
ArchiMate and Zachman
Scope(contextual)
Enterprise model(conceptual)
System model(logical)
Technology model(physical)
Detailed representations(out of context)
Planner
Owner
Designer
Builder
Sub-
contractor
Data Function Network People Time Motivation
What? How? Where? Who? When? Why?
Business
Application
Technology
Str
uctu
re
Beh
av
iou
r
Info
rmati
on
Att
rib
ute
s
Natu
ral
lan
gu
ag
e
ArchiMate and UML
• ArchiMate connects architectural domains
– It has a broader scope, but less detail than UML
– It acknowledges the need for specialized
languages for different architectural domains, such
as UML, BPMN and others
– Transformations to more detailed, specialized
models
• Several ArchiMate concepts derived from UML
(esp. for application and infrastructure)
• First version of a UML profile for ArchiMate available
27
ArchiMate and Model-Driven Architecture
ComputationIndependent Model
(CIM)
PlatformIndependent Model
(PIM)
PlatformSpecific Model
(PSM)
mappin
g
mappin
g
Business modelDomain modelBusiness requirements
e.g. UML model for a J2EEplatform
e.g. BPMN Model independentof workflow engine, orUML model independentof computing platform
mappin
g
mappin
g ArchiMate
ArchiMate may help
bridge the gap between
CIM and PIM
Results in Practice
• Applications at over 30 organizations
– e.g. Dutch Tax Administration and many other
companies and government institutes
• Tools
– BiZZdesign, Troux Metis (certified)
– IDS Scheer, Adaptive, Telelogic (implementing)
– MEGA, Casewise, ASG, IBM (interested)
• Education
– Used by several Dutch universities and other
educational institutes
• Rapidly growing international attention
28
ArchiMate Users
• User organizations– Dutch Tax Administration
– ABN AMRO
– ABP
– SVB
– UWV
– ABZ
– VGZ-IZA
– SNS Reaal
– Interpolis
– Zwitserleven
– Fortis
– Quion
– Stater
– NS
– TNT
– Philips
– Kluwer
– Vitens
– Dutch Police
– Autoriteit Financiële Markten
– Province of Groningen
– Province of Overijssel
– Province of Gelderland
– Ministry of the Interior
– Raad van State
– CFI
– CITO
– Leiden University
– Avans Hogeschool
– Hogeschool van Amsterdam
– Fontys Hogescholen
– NHTV
• ICT consultants
– Ordina
– Getronics PinkRoccade
– Sogeti
– Atos Origin
– CIBIT
– LogicaCMG
• Tool vendors
– BiZZdesign
– Troux
– IDS Scheer
– Adaptive
– Agilense
• Research & education
– Telematica Instituut
– Leiden University
– Radboud University
Nijmegen
– Centrum voor Wiskunde
& Informatica
– Hogeschool van
Amsterdam
– Avans Hogeschool
– CIBIT
– University of Twente
– Lisbon Technical
University
– Delft University of
Technology
– TU Eindhoven
ArchiMate Forum
• Open cooperation between ArchiMate users, vendors,
educators, and consultants
• Long term objective:
– An independent standard for describing
enterprise architectures
• Goals of the ArchiMate Forum:
– Creating critical mass
– Supporting organizations in applying ArchiMate
– Contributing to international standards
29
Members ArchiMate Forum