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 isto be enterprise architecture domain/aspect architectures culture people leadership Operations … peopleprocessesITproducts Role of Enterprise Architecture

Enterprise Architecture: Describing Coherence Process architecture Application architecture Technical architecture Information architectureProduct 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 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 specific ProcessApplication 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 BehaviourActive 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 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 PayValuateAcceptRegister 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

Interacties & Collaborations

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 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 RegisterPayValuateAccept Notifi- cation Financial application Policy 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 ClientInsurant Damage claiming process Registration Claim registration service administration Customer service CRM system ? Weakest link determines composition: association1 access 2 use3 realisation4 assignment5 aggregation6 composition7

Layered Architecture Business layer Application layer Technology layer

Overview of Core Concepts

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

ArchiSurance (I) ArchiSurance was originally in home and travel insurance has merged with PRO-FIT (car insurance) and LegallyYours (legal aid) Business functions are used for high-level insight in ArchiSurance’s primary operations: Customer and Intermediary relations Contracting Claims handling Financial handling Asset management

Business Functions

Product

ArchiSurance (II) Post-merger integration is in full swing Front offices for customer and intermediary relations But still three different back offices: Home & Away Car Legal Aid Shared Service Center for document processing (scanning, printing, archiving) Supporting departments

Organisation

Organisation & Business Functions

ArchiSurance (III) However, IT integration is a problem: “Home & Away” have separate financial and policy administration systems, and use the central CRM system and call center “Car” have their own monolithic system, but use the central CRM system and call center “Legal Aid” have their own back- and front office systems

Applications

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

ArchiSurance (IV) Processes within the back office link the external products and services with the internal systems IT integration should be “invisible” to ArchiSurance’s clients: products & services remain the same

Business Processes & Services

Application Usage

Application Structure

ArchiSurance (V) Application infrastructure moving towards J2EE Service-based approach will be used Existing infrastructure remains largely intact (network, mainframe, Unix server farm), but will be consolidated and virtualised

Infrastructure

Deployment

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.

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

Application Behaviour

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

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 ArchiSurance

Viewpoints for Informing Process illustration Goal is communication Pictures aimed at ‘non-architects’

Process Illustration (I)

Process Illustration (II)

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 Business Application Technology Structure Behaviour Information Attributes Natural language

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 ADMArchiMate 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

USERS

CONSULTING & TOOLS

EDUCATION

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 suitable for a first try, but no substitute for a ‘real’ tool Open source Bolton University: (work in progress)

?

More Information? Most ArchiMate results are available through the website: See also The Open Group’s ArchiMate Forum: Marc Lankhorst Novay P.O. Box AN Enschede The Netherlands Marc