enterprise architecture modelling with...
TRANSCRIPT
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”
Mission
Strategy
Actions
Vision
Goals as is to be
enterprise architecture
domain/aspect
architectures
culture
people
leadership
Operations
… people processes IT products
Role of Enterprise Architecture
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 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)
Analysis
ArchiMate Focus
Integration
Visualisation
Idea
Design
Use
Management
Formal models
Analysis
Napkin
Whiteboard
Powerpoint
Link with
implementation
Maintenance
Version control
Communication
with stakeholders
Visualisation
Architecture
process
ArchiMate Scope
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
External
business service
Internal
business service
Internal
infra. service
External
infra. service Technology
Application
Business
Customer
External
application service
Internal
application 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
ArchiMate language High-level
modelling
within a
domain
Modelling relations
between domains
Basis for
visualisations
Basis for
analyses Relate to
standards
Company-specific
concepts, standards,
e.g. UML, BPMN
Enterprise architecture
concepts
Generic concepts
more
generic
more
sp
ecific
Process Application
Object
Relation
Abstraction Levels
Layers and Aspects
Technology
Application
Business
Passive
structure
“object”
Behaviour
“verb”
Active
structure
“subject”
Processes Information
Data
Organisation
Products &
Services
Applications
Technical Infrastructure
Business
Functions
Generic Structure at Each Layer
Internal
External
Passive
structure
Behaviour Active
structure
Structure
element
Object
Service Interface
Behaviour
element
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 function
Insurance
policies
flow
Contracting Claim
Handling
ArchiSurance
business actor
assignment
product
Travel Insurance
Policy
contract
Product and Services
Security
value
Customer information
service
Insurance
application
service
Claim registration
service
Claim registration
service
Claim payment
service
business service
Customer business actor
Insurant
business role
assignment
Business Process
Handle Claim
Pay Valuate Accept Register Damage occurred
event
Customer business actor
used by
Insurant business role
business process triggering
Reject
junction
Notification
access
business
object
Claim registration
service
Customer Information
service
Claim payment service
business service
realisation
Interfaces & Services
Sell
product
Buy
product
Seller Buyer
Selling
business interface
business service
Interacties & Collaborations
Sell
product
Buy
product
Complete
transaction
Seller Buyer
business collaboration
business interaction
Information
specialisation
Car insurance policy
Home insurance policy
Travel insurance policy
Liability insurance policy
Legal aid insurance policy
aggregation
Customer file
Customer
composition
Damage claim Insurance policy Insurance request
realisation
Claim form
representation
application
interface
Application Concepts
Policy administration
application
component
Policy creation
application function
Financial administration
Premium collection
Customer
file data
Policy
data data object
Policy creation service
application service
Policy
access
service
Application Usage by Business
Processes
Handle claim
Register Pay Valuate Accept Notifi-
cation
Financial application
Policy administration
administration Customer
service
Payment service
CRM system
Claim
service administration
Notifi- cation data
Technology Concepts
IBM System z Sun Blade
device
Database access service
infrastructure service
DB2 Database
iPlanet App. server
system software
LAN
network
association
artifact
Database
tables
Fin. application
EJBs
Deployment
Financial application
CRM system
Customer
data
IBM System z
DB2 Database
Sun Blade
iPlanet App. server
Database access service
LAN
Fin. application
EJBs
Database
tables
Derived Relations
Client Insurant
Damage claiming process
Registration
Claim registration
service
administration Customer
service
CRM system
?
Weakest link determines composition:
association 1
access 2
use 3
realisation 4
assignment 5
aggregation 6
composition 7
Layered
Architecture
Business layer
Application layer
Technology layer
Internal processes, roles and actors
Infrastructure
External infrastructure services
Application components and services
External processes, roles and actors
External application services
External business services
Handle claim
CustomerInsurant
Registration PaymentValuationAcceptance
Customer
information
service
Claims
payment
service
Customer
administration
service
Payment
service
CRM
system
Financial
application
Customer
information
service
Claim
registration
service
Claims
administration
service
Policy
administration
Claim
files
service
IBM System z
DB2
Financial
application
EJBs
Customer
files
service
Blade
Application
server
Claim
information
service
Customer
data
ArchiSurance
Insurer
Customer
db-tables
LAN
Submit
claim
Overview of Core Concepts
Business
object
Data
object
ArtifactSystem
softwareDevice Network
Infrastructure
interface
Application
component
Business
role
Business
process
EventBusiness
service
Application
service
Application
function
Infrastructure
service
Application
interface
Business
interfaceBusiness
Application
Technology
Passive
structureBehaviour Active
structure
triggering
flow
aggregation
assignment
access
realization
association
composition
ValueMeaning
use
Business
actor
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
Example
ArchiSurance – Integrating an
Insurance Company after a Merger
Business Functions
Insurer
Maintaining
Intermediary
Relations
Contracting
Financial
Handling
Claims
Handling
Claims
Insurance
policies
Customer information
Money
Maintaining
Customer
Relations
Asset
Management
Contracts
Product
information
Customer
information
Claims
Insurance
information
Insurance
premiums
Claim
payments
Insurance
policies
Customer
information
Product
information
Claims
Money
Claim
information
Intermediary
Customer
Customer’s
Bank
Product
Travel Insurance
Claim
registration
service
Customer
information
service
Claims
payment
service
Travel insurance
policy
Insurance
application
service
Premium
payment
service
Customer
data mutation
service
"be insured"
(security)
Customer
Organisation
ArchiSurance
Back Office
Front Office
Home
&
Away
CarLegal
Aid
Customer
Relations
HRMProduct
DevelopmentFinance
Intermediary
Relations
Document
Processing
SSC
Organisation & Business Functions
Finance
Home
&
Away
Car Legal
Aid
Customer RelationsIntermediary Relations
Maintaining
Intermediary
Relations
Contracting
Financial
Handling
Claims Handling
Maintaining
Customer
Relations
Asset
Management
Applications Front office
Legal Aid
CarHome & Away
Home & Away
Policy
administration
Home & Away
Financial
application
Car Insurance
application
Legal Aid
backoffice
system
Web
portal
Call center
application
CRM application Legal Aid
CRM
Maintaining
Customer &
Intermediary
Relations
Claim
Handling
Contracting
Document
Processing
Liability
Insurance
Car
Insurance
Travel
Insurance
Home
Insurance
Legal Aid
Insurance
Web portal
Call center application
Customer relationship management system
Home & Away
Policy administration
Legal Aid
back
office
system
Legal Aid CRM
Document management system
Home & Away
Financial application
Business
Functions
Products
Financial
Handling
Car insurance
application
Landscape map
Business Processes & Services
Claim
registration
service
Customer
information
service
Claims
payment
service
Customer
Handle ClaimClose Contract Collect PremiumInform Customer
Insurance
application
service
Premium
payment
service
Application Usage
Handle Claim
Register PayValuateAccept
Home & Away
Policy
administration
CRM
application
Home & Away
Financial
application
Customer
administration
service
Claims
administration
service
Payment
service
Printing
service
Scanning
service
Document
management
system
Application Structure
Home & Away Policy administration
Risk
Assessment
Policy data
management
Customer
data access
Damage claim data Customer file dataInsurance policy
data
Claim data
management
Insurance request
data
Infrastructure
ArchiSurance
Unix server farm
Mainframe
Intermediary
Admin
serverLAN
NAS
File server
LANTCP/IP
NetworkFirewall Firewall
Unix
server
Unix
server
DBMS
Message
Queing
CICS
Deployment
Unix server farm
Home & Away
Policy
administration
CRM
application
Home & Away
Financial
application
Document
management
system
Mainframe
NAS
File serverLAN
Firewall
Network
Call center
applicationWeb portal
Car Insurance
application
Legal Aid
backoffice
system
Relation to Other Developments
Boundaries
Metadata
Method
Change
Principles
Realisation
Semantics
Strategy
Location
Business
domains
Physical
resources
Time
ArchiMate
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
Scope
= Planner’s view
Enterprise Model
= Owner’s view
System Model
= Designer’s view
Technology Model
= Builder’s view
Detailed representation
= Subcontractor’s view
Functioning Enterprise
= User's view
Why Who When Where What How
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Business
Application
Technology
Str
uc
ture
Be
ha
vio
ur
Info
rma
tio
n
Att
rib
ute
s
Na
tura
l
lan
gu
ag
e
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: ITAC
• Delivery method: TOGAF
• Description language: ArchiMate
TOGAF and ArchiMate
Preliminary
D Technology
Architecture
Requirements
Management
A Architecture
Vision
B Business
Architecture
C Information
Systems
Architectures
H Architecture
Change
Management
G Implementation
Governance
F Migration
Planning E Opportunities
and
Solutions
Business
Application
Technology
TOGAF ADM ArchiMate
Business
Architecture
Application
Architecture
Data
Architecture
Technology
Architecture
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 [email protected]
053-4850456