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
as is Goals to be
enterprise architecture culture Actions leadership domain/aspect architectures people
Operations products processes 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 Design Visualisation
Napkin Architecture Whiteboard Idea Use Powerpoint process 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 ArchiMate language modelling within a Basis for domain visualisations
Modelling relations Basis for Relate to between domains analyses standards Abstraction Levels
Object Generic concepts
Relation
Enterprise architecture
Application Process concepts
more generic more more specific more
Company-specific concepts, standards, e.g. UML, BPMN Layers and Aspects
Products & Services Business Functions Organisation Business Information Processes
Application Data Applications
Technology Technical Infrastructure
Passive Behaviour Active structure structure “object” “verb” “subject” Generic Structure at Each Layer
External Service Interface
Object Internal Behaviour Structure element element
Passive Behaviour Active structure 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
Insurance Claim Contracting policies Handling
flow Product and Services
business actor Customer assignment business role value Insurant Security product
Travel Insurance
Insurance Claim Customer Claim Policy application registration information payment service service service service
business service contract Business Process
Customer business actor
Insurant business role business service used by Claim Customer Claim registration Information payment service service service business realisation object access Handle Claim Notification Damage occurred Register Accept Valuate Pay
event Reject
business process triggering junction Interfaces & Services
business service
Sell Buy Selling product product
Seller Buyer
business interface Interacties & Collaborations
business interaction Complete transaction Sell Buy product product
Seller Buyer
business collaboration Information
Customer
aggregation Customer file
composition realisation representation Insurance request Insurance policy Damage claim Claim form specialisation
Travel insurance Car insurance Home insurance Liability Legal aid policy policy policy insurance policy insurance policy Application Concepts
Policy application creation application service service interface
application Policy Financial component administration administration
Policy Policy Premium creation access collection application service function
data object Policy Customer data file data Application Usage by Business Processes
Handle claim Notifi- Register Accept Valuate Pay cation
Customer Claim Payment administration administration service service service
Notifi- CRM Policy Financial cation system administration application data Technology Concepts
infrastructure service artifact
Database access service Database tables
IBM System z Sun Blade Fin. LAN DB2 iPlanet application Database App. server EJBs
network system software association device Deployment
CRM Customer Financial system data application
Database access service
Database tables
IBM System z Sun Blade Fin. DB2 LAN iPlanet application Database App. server EJBs Derived Relations Weakest link determines Client Insurant composition: association 1 Claim registration access 2 service use 3 Damage claiming process realisation 4 ? Registration assignment 5 aggregation 6 Customer composition 7 administration service
CRM system External processes, roles and actors
Submit claim Insurant Customer
Layered External business services Claim Customer Claims registration information payment Architecture service service service
Internal processes, roles and actors
Business layer Handle claim ArchiSurance
Registration Acceptance Valuation Payment Insurer
External application services
Customer Claims Payment administration administration service service service
Application components and services
Customer Claim information information service service Application layer CRM Customer Policy Financial system data administration application
External infrastructure services
Claim Customer files files service service
Infrastructure
Customer IBM System z db-tables Blade Technology layer Financial Application DB2 application server EJBs LAN Overview of Core Concepts
Meaning Value
association Business Business Event service interface Business assignment
Business object Business Business process role
triggering Business Application Application actor aggregation service interface
Data access Application object Application Application function component
flow use
composition Infrastructure Infrastructure realization service interface
Technology System Artifact Device Network software
Passive Behaviour Active structure structure 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 Insurance information Maintaining Maintaining information Intermediary Customer Customer Customer Relations Relations Claims information
Customer information Claims Intermediary
Contracts Insurance Claims Claim Contracting policies Handling information
Insurance Claims policies
Claim Money payments Asset Financial Customer’s Management Handling Insurance Bank Money premiums Product
Customer
"be insured" (security)
Travel Insurance
Insurance Premium Customer Travel insurance application payment data mutation policy service service service
Claim Customer Claims registration information payment service service service Organisation
ArchiSurance
Customer Intermediary Relations Relations
Front Office
Home Legal & Car Aid Away
Back Office
Document Product Processing Finance HRM Development SSC Organisation & Business Functions
Intermediary Relations Customer Relations
Maintaining Maintaining Intermediary Customer Relations Relations
Home Car Legal & Aid Away
Contracting
Claims Handling
Finance
Asset Financial Management Handling Applications
Front office
Call center Web application portal Legal Aid
CRM application Legal Aid CRM
Home & Away Car
Home & Away Legal Aid Car Insurance Policy backoffice application administration system
Home & Away Financial application Landscape map Products Business Home Travel Liability Car Legal Aid Functions Insurance Insurance Insurance Insurance Insurance Web portal Maintaining Customer & Call center application Intermediary Relations Legal Aid Customer relationship management system CRM
Contracting Home & Away Policy administration Legal Aid Claim Car insurance back Handling application office system Home & Away Financial application Financial Handling
Document Document management system Processing Business Processes & Services
Customer
Insurance Claim Claims Customer Premium application registration payment information payment service service service service service
Close Contract Handle Claim Inform Customer Collect Premium Application Usage
Handle Claim
Register Accept Valuate Pay
Customer Claims Scanning Printing Payment administration administration service service service service service
Document Home & Away Home & Away CRM management Policy Financial application system administration application Application Structure
Home & Away Policy administration
Risk Claim data Policy data Customer Assessment management management data access
Insurance request Damage claim data Insurance policy Customer file data data data Infrastructure
ArchiSurance
NAS File server Intermediary
Mainframe TCP/IP Admin LAN Firewall Firewall LAN Network server Message Queing
DBMS Unix server farm
Unix Unix CICS server server Deployment
Home & Away Home & Away Call center CRM Car Insurance Web portal Policy Financial application application application administration application
Document Legal Aid management backoffice system system
Unix server farm Mainframe
NAS LAN File server
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 Contextual
= Planner’s view
Enterprise Model Business
Conceptual
= Owner’s view
System Model Application Logical
= Designer’s view
Natural
language
Attributes
Structure Behaviour
Technology Model Information Physical = Builder’s view Technology
Detailed representation As Built = Subcontractor’s view
Functioning Enterprise Functioning = User's view 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
A Architecture H Vision Architecture B Business Change Business Business Management Architecture Architecture
C G Requirements Information Data Application Implementation Systems Application Governance Management Architectures Architecture Architecture
F D Technology Migration Technology Technology Planning E Architecture 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 [email protected] 053-4850456