Enterprise Architecture
Modelling with ArchiMate
Marc Lankhorst
Principal Researcher Enterprise Architecture
Utrecht University, January 11, 2010
Overview
• Introduction
• Enterprise architecture
• The ArchiMate modelling language
• Integration of business, applications, and technology
• Role of service orientation
• Example: ArchiSurance, merger of an insurance company
• Relation with other developments
• UML, BPMN
• Zachman Framework
• TOGAF
Novay
• Independent, non-profit research institute
• Founded & funded by companies, the Dutch government,
and universities
• To create impact with ICT innovation
• In projects together with industry and academia
Enterprise Architecture
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”
Role of Enterprise Architecture
Mission
Vision
Strategy
Goals
as is
enterprise architecture
Actions
to be
culture
leadership
domain/aspect
architectures
products
processes
people
Operations
…
people
IT
Enterprise Architecture: Describing
Coherence
Information architecture
Product architecture
?
Process architecture
?
?
?
Application architecture
Technical architecture
?
Better Support for the Enterprise
Architect
• Increasing need for precise documentation on the
enterprise architecture level
• Integrating various aspect models in many languages (UML,
IDEF, BPMN, ARIS, ...)
• Communicating about architecture with others
• Get away from the “fuzzy pictures” image
• Analysis of architectures before their implementation
• Needed: well-founded, practical, and vendor-independent
standard for enterprise architecture modelling
The ArchiMate Research Project
•
•
•
•
2½ years, July 2002 - December 2004
approx. 35 man-years, 4 million euro
Consortium of companies and knowledge institutes
Directed by Novay (then still Telematica Instituut)
ArchiMate Focus
Visualisation
Analysis
Integration
ArchiMate Scope
Formal models
Analysis
Communication
with stakeholders
Visualisation
Design
Napkin
Whiteboard
Powerpoint
Idea
Architecture
process
Use
Link with
implementation
Management
Maintenance
Version control
Main Benefits of ArchiMate
• Lean and mean language:
• just enough concepts, not bloated to include everything
possible
• Well-founded concepts & models give precision
• clear communication about architectures
• get away from the ‘fuzzy pictures’ image
• Links to existing approaches
• UML, BPMN, TOGAF
• International vendor-independent standard
• The Open Group
• Tool support
• several tools available
Service Orientation
Design Paradigms
Increased focus on the ‘outside’:
• Structured programming
• Object orientation
• Component-based development
• Service-oriented architecture (SOA)
• (Event-driven architecture?)
Service Orientation
Service
• Unit of externally available functionality
• Offered via clear interfaces
• Relevant for the environment
Web services as a prominent technological example
Service-Oriented Architecture
Is
• A way of thinking
• A bridge between business and IT
Is not
• Web services
• Asynchronous communication
• A software artefact (an ESB)
Services are Central to ArchiMate
Customer
External
business service
Business
Internal
business service
External
application service
Application
Internal
application service
External
infra. service
Technology
Internal
infra. service
Integrated Modelling
Integration
An architecture might encompass for example:
• products & services
• organisation
• processes
• information
• applications
• systems
• networks
This requires concepts for domains and relations,
linked with existing techniques
The ArchiMate Language
High-level
modelling
within a
domain
ArchiMate language
Modelling relations
between domains
Basis for
visualisations
Relate to
standards
Basis for
analyses
Abstraction Levels
Generic concepts
more specific
more generic
Object
Relation
Application
Process
Enterprise architecture
concepts
Company-specific
concepts, standards,
e.g. UML, BPMN
Layers and Aspects
Products &
Services
Business
Application
Information
Processes
Business
Functions Organisation
Applications
Data
Technical Infrastructure
Technology
Passive
structure
“object”
Behaviour
“verb”
Active
structure
“subject”
Generic Structure at Each Layer
Service
Interface
Object
Behaviour
element
Structure
element
Passive
structure
Behaviour
External
Internal
Active
structure
Similar concepts at each layer make the language
easier to learn and more consistent in use
(cf. Fred Brooks’ “conceptual integrity”)
Notation
• Most concepts have two notations:
• Icon
• Box with icon
• Sharp corners = structure
• Rounded corners = behaviour
• Notation resembles UML and BPMN
• to stay close to what architects already know
• Relations (arrows etc.) are also mostly taken from existing
languages, with a few exceptions
Business Functions and Actors
business actor
ArchiSurance
assignment
business function
Contracting
Insurance
policies
flow
Claim
Handling
Product and Services
business actor
Customer
assignment
business role
value
Insurant
Security
product
Travel Insurance
Insurance
application
service
Claim
registration
service
Customer
information
service
business service
Claim
payment
service
Policy
contract
Business Process
Customer
Insurant
business actor
business role
business service
used by
Claim
registration
service
Customer
Information
service
realisation
Claim
payment
service
access
Handle Claim
Damage
occurred
business
object
Notification
Register
Accept
Valuate
Pay
Reject
event
business process
triggering
junction
Interfaces & Services
business service
Sell
product
Seller
Selling
Buy
product
Buyer
business interface
Interacties & Collaborations
business interaction
Complete
transaction
Sell
product
Buy
product
Seller
Buyer
business collaboration
Information
Customer
aggregation
Customer file
composition
realisation
representation
Insurance request
Insurance policy
Damage claim
Claim
form
specialisation
Travel insurance
policy
Car insurance
policy
Home insurance
policy
Liability
insurance policy
Legal aid
insurance policy
Application Concepts
application
service
application
component
Policy
creation
service
application
interface
Policy
administration
Policy
creation
application
function
data object
Policy
data
Financial
administration
Policy
access
service
Premium
collection
Customer
file
data
Application Usage by Business
Processes
Handle claim
Register
Customer
administration
service
CRM
system
Accept
Claim
administration
service
Policy
administration
Valuate
Pay
Notification
Payment
service
Financial
application
Notification
data
Technology Concepts
infrastructure service
artifact
Database
access
service
Database
tables
IBM System z
DB2
Database
Sun Blade
LAN
iPlanet
App. server
network
system software
association
device
Fin.
application
EJBs
Deployment
CRM
system
Customer
data
Financial
application
Database
access
service
Database
tables
IBM System z
DB2
Database
Sun Blade
LAN
iPlanet
App. server
Fin.
application
EJBs
Derived Relations
Client
Insurant
Claim
registration
service
Damage claiming process
?
Registration
Customer
administration
service
CRM
system
Weakest link
determines
composition:
association
1
access
2
use
3
realisation
4
assignment
5
aggregation
6
composition
7
External processes, roles and actors
Submit
claim
Layered
Architecture
Customer
Insurant
External business services
Claim
registration
service
Customer
information
service
Claims
payment
service
Internal processes, roles and actors
Business layer
Handle claim
ArchiSurance
Registration
Acceptance
Valuation
Payment
Insurer
External application services
Customer
administration
service
Claims
administration
service
Payment
service
Application components and services
Claim
information
service
Customer
information
service
Application layer
CRM
system
Customer
data
Policy
administration
Customer
db-tables
Blade
Financial
application
External infrastructure services
Claim
files
service
Customer
files
service
Infrastructure
Technology layer
IBM System z
Application
server
DB2
LAN
Financial
application
EJBs
Overview of Core Concepts
Value
Meaning
association
Business
service
Event
Business
Business
object
Business
process
assignment
Business
interface
Business
role
triggering
Application
service
aggregation
Data
object
Application
access
Application
function
flow
composition
realization
Technology
Artifact
Passive
structure
Application
interface
Business
actor
Application
component
use
Infrastructure
service
System
software
Behaviour
Infrastructure
interface
Device
Active
structure
Network
Services as Binding Concept
Customer
External
business service
Business
Internal
business service
External
application service
Application
Internal
application service
External
infra. service
Technology
Internal
infra. service
Example
ArchiSurance – Integrating an
Insurance Company after a Merger
Business Functions
Customer
information
Product
information
Insurer
Product
information
Customer
information
Maintaining
Intermediary
Relations
Maintaining
Customer
Relations
Customer information
Insurance
information
Customer
Claims
Claims
Intermediary
Contracts
Contracting
Asset
Management
Insurance
policies
Claims
Handling
Insurance
policies
Claims
Money
Money
Financial
Handling
Claim
information
Claim
payments
Insurance
premiums
Customer’s
Bank
Product
Customer
"be insured"
(security)
Travel Insurance
Insurance
application
service
Premium
payment
service
Customer
data mutation
service
Claim
registration
service
Customer
information
service
Claims
payment
service
Travel insurance
policy
Organisation
ArchiSurance
Intermediary
Relations
Customer
Relations
Front Office
Home
&
Away
Legal
Aid
Car
Back Office
Document
Processing
SSC
Finance
Product
Development
HRM
Organisation & Business Functions
Intermediary Relations
Customer Relations
Maintaining
Intermediary
Relations
Maintaining
Customer
Relations
Home
&
Away
Car
Legal
Aid
Contracting
Claims Handling
Finance
Asset
Management
Financial
Handling
Applications
Front office
Call center
application
Web
portal
Legal Aid
Legal Aid
CRM
CRM application
Home & Away
Home & Away
Policy
administration
Home & Away
Financial
application
Car
Car Insurance
application
Legal Aid
backoffice
system
Landscape map
Products
Business
Functions
Maintaining
Customer &
Intermediary
Relations
Contracting
Home
Insurance
Travel
Insurance
Liability
Insurance
Document
Processing
Legal Aid
Insurance
Web portal
Call center application
Customer relationship management system
Legal Aid
CRM
Home & Away
Policy administration
Car insurance
application
Claim
Handling
Financial
Handling
Car
Insurance
Home & Away
Financial application
Document management system
Legal Aid
back
office
system
Business Processes & Services
Customer
Insurance
application
service
Close Contract
Claim
registration
service
Handle Claim
Claims
payment
service
Customer
information
service
Inform Customer
Premium
payment
service
Collect Premium
Application Usage
Handle Claim
Register
Scanning
service
Document
management
system
Customer
administration
service
CRM
application
Accept
Claims
administration
service
Home & Away
Policy
administration
Valuate
Printing
service
Pay
Payment
service
Home & Away
Financial
application
Application Structure
Home & Away Policy administration
Risk
Assessment
Insurance request
data
Claim data
management
Damage claim data
Policy data
management
Insurance policy
data
Customer
data access
Customer file data
Infrastructure
ArchiSurance
NAS
File server
Intermediary
Mainframe
Firewall
LAN
Message
Queing
DBMS
CICS
Unix server farm
Unix
server
Unix
server
TCP/IP
Network
Firewall
LAN
Admin
server
Deployment
Web portal
Call center
application
CRM
application
Home & Away
Policy
administration
Home & Away
Financial
application
Document
management
system
Legal Aid
backoffice
system
Unix server farm
NAS
File server
Car Insurance
application
Mainframe
LAN
Firewall
Network
Relation to Other Developments
Boundaries
Strategy
Change
Principles
Business
domains
Time
Realisation
ArchiMate
Method
Location
Physical
resources
Metadata
Semantics
ArchiMate and UML/BPMN/…
• ArchiMate connects architectural domains
• Broader scope, but less detail than e.g. UML (software),
BPMN (processes)
• No replacement for these, but an ‘umbrella’ on top
• Several ArchiMate concepts derived from BPMN (esp.
business processes) and UML (esp. for application and
infrastructure)
• Easy to link to e.g. UML descriptions of detailed design or
BPMN process models
ArchiMate and Zachman
What
How
Where
Who
When
Why
Scope
= Planner’s view
Technology
Natural
language
Attributes
Application
Structure
Technology Model
= Builder’s view
Business
Behaviour
System Model
= Designer’s view
Information
Enterprise Model
= Owner’s view
Contextual
Conceptual
Logical
Physical
Detailed representation
= Subcontractor’s view
As Built
Functioning Enterprise
= User's view
Functioning
ArchiMate and The Open Group
ArchiMate and The Open Group
• ArchiMate now under the aegis of The Open Group
• Official ArchiMate 1.0 standard
• Original goal, a vendor-independent standard for
enterprise architecture modelling, is now a reality!
• ArchiMate Forum within The Open Group
• responsible for standardisation, further development of the
language, PR, etc.
ArchiMate and TOGAF
• TOGAF: The Open Group Architecture Framework
• Architecture Development Method (ADM) provides a way of
working
• Methodical support, but no description technique
• ArchiMate:
• a description language
• but no prescribed way of working
•
•
•
•
A perfect match!
People:
Delivery method:
Description language:
ITAC
TOGAF
ArchiMate
TOGAF and ArchiMate
Preliminary
A
H
Architecture
Vision
B
Architecture
Change
Management
Business
Business
Business
Architecture
Architecture
C
G
Information
Systems
Architectures
Requirements
Management
Implementation
Governance
F
D
Migration
Planning
Technology
Architecture
E
Data
Architecture
Application
Application
Architecture
Technology
Technology
Architecture
Opportunities
and
Solutions
TOGAF ADM
ArchiMate
ArchiMate Usage in Practice
ArchiMate in Practice
• Applications at many organisations
• Banks, insurance companies,
government, etc.
• Consultants
• Ordina, Logica, Capgemini, Sogeti, Getronics, etc.
• Tools
• 5 certified tools, and some others
• Education
• Used by several universities and other educational institutes
• Active user group
• ArchiMate Forum of The Open Group
Tool Support for ArchiMate
•
•
•
Toolvendors:
• BiZZdesign:
Architect
• IDS Scheer:
ARIS ArchiMate Modeler
• Casewise:
Corporate Modeler
• Telelogic (IBM):
System Architect
• Troux:
Metis
• (Agilense: EA Web Modeler)
• (Avolution:
Abacus)
• (Promis:
EVA Netmodeler)
Microsoft Visio, Omnigraffle templates
• downloadable from www.archimate.org
• suitable for a first try, but no substitute for a ‘real’ tool
Open source
• Bolton University: http://archi.cetis.ac.uk/ (work in progress)
?
More Information?
Most ArchiMate results are available through the website:
www.archimate.org
See also The Open Group’s ArchiMate Forum:
www.opengroup.org/archimate
Marc Lankhorst
Novay
P.O. Box 589
7500 AN Enschede
The Netherlands
Marc Lankhorst@telin.nl
053-4850456