Enterprise Architecture Modelling with ArchiMate

Transcription

1 Enterprise Architecture Modelling with ArchiMate Marc Lankhorst Principal Researcher Enterprise Architecture Utrecht University, January 11, 2010

2 Overview Introduction Enterprise architecture The ArchiMate modelling language Integration of business, applications, and technology Role of orientation Example: ArchiSurance, merger of an insurance company Relation with other developments UML, BPMN Zachman Framework TOGAF

3 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

4 Enterprise Architecture

5 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

6 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

7 Role of Enterprise Architecture Mission Vision Strategy as is Goals to be enterprise architecture domain/aspect architectures Actions culture leadership people products processes Operations people IT

8 Enterprise Architecture: Describing Coherence Information architecture? Product architecture Process architecture? Application architecture?? Technical architecture?

9 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

10 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)

11 ArchiMate Focus Visualisation Analysis Integration

12 ArchiMate Scope Formal models Analysis Design Communication with stakeholders Visualisation Napkin Whiteboard Powerpoint Idea Architecture process Use Link with implementation Management Maintenance Version control

13 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

14 Service Orientation

15 Design Paradigms Increased focus on the outside : Structured programming Object orientation Component-based development Service-oriented architecture (SOA) (Event-driven architecture?)

16 Service Orientation Service Unit of externally available functionality Offered via clear interfaces Relevant for the environment Web s as a prominent technological example

17 Service-Oriented Architecture Is A way of thinking A bridge between business and IT Is not Web s Asynchronous communication A software artefact (an ESB)

18 Services are Central to ArchiMate Customer External business Business External application External infra. Internal business Internal application Internal infra. Application Technology

19 Integrated Modelling

20 Integration An architecture might encompass for example: products & s organisation processes information applications systems networks This requires concepts for domains and relations, linked with existing techniques

21 The ArchiMate Language High-level modelling within a domain ArchiMate language Basis for visualisations Modelling relations between domains Relate to standards Basis for analyses

22 more generic more specific Abstraction Levels Object Generic concepts Relation Application Process Enterprise architecture concepts Company-specific concepts, standards, e.g. UML, BPMN

23 Layers and Aspects Business Products & Services Business Functions Information Processes Organisation Application Data Applications Technology Technical Infrastructure Passive structure object Behaviour verb Active structure subject

24 Generic Structure at Each Layer External Service Interface Internal Object Behaviour element Structure element Passive structure Behaviour Active structure Similar concepts at each layer make the language easier to learn and more consistent in use (cf. Fred Brooks conceptual integrity )

25 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

26 Business Functions and Actors business actor ArchiSurance business function assignment Contracting Insurance policies Claim Handling flow

27 Product and Services business actor Customer business role assignment value Insurant Security product Travel Insurance Insurance application Claim registration Customer information Claim payment Policy business contract

28 Business Process Customer business actor Insurant business role business used by Claim registration Customer Information realisation Handle Claim Claim payment access business object Damage occurred Register Accept Valuate Pay Notification event Reject business process triggering junction

29 Interfaces & Services business Sell product Selling Buy product Seller Buyer business interface

30 Interacties & Collaborations business interaction Sell product Complete transaction Buy product Seller Buyer business collaboration

31 Information Customer aggregation Customer file composition realisation representation specialisation Insurance request Insurance policy Damage claim Claim form Travel insurance policy Car insurance policy Home insurance policy Liability insurance policy Legal aid insurance policy

32 Application Concepts application Policy creation application interface application component Policy administration Financial administration application function Policy creation Policy access Premium collection data object Policy data Customer file data

33 Application Usage by Business Processes Handle claim Register Accept Valuate Pay Notification Customer administration Claim administration Payment CRM system Policy administration Financial application Notification data

34 Technology Concepts infrastructure artifact Database access Database tables IBM System z DB2 Database LAN Sun Blade iplanet App. server Fin. application EJBs network system software association device

35 Deployment CRM system Customer data Financial application Database access Database tables IBM System z DB2 Database LAN Sun Blade iplanet App. server Fin. application EJBs

36 Derived Relations? Client Insurant Claim registration Damage claiming process Registration Customer administration Weakest link determines composition: association 1 access 2 use 3 realisation 4 assignment 5 aggregation 6 composition 7 CRM system

37 External processes, roles and actors Layered Architecture External business s Claim registration Submit claim Customer information Insurant Claims payment Customer Business layer Internal processes, roles and actors Handle claim ArchiSurance Registration Acceptance Valuation Payment Insurer External application s Customer administration Claims administration Payment Application components and s Application layer CRM system Customer information Customer data Claim information Policy administration Financial application External infrastructure s Claim files Customer files Infrastructure Technology layer IBM System z DB2 Customer db-tables LAN Blade Application server Financial application EJBs

38 Overview of Core Concepts Business object Data object Artifact System software Device Network Infrastructure interface Application component Business role Business process Event Business Application Application function Infrastructure Application interface Business interface Business Application Technology Passive structure Behaviour Active structure triggering flow aggregation assignment access realization association composition Value Meaning use Business actor

39 Services as Binding Concept Customer External business Business External application External infra. Internal business Internal application Internal infra. Application Technology

40 Example ArchiSurance Integrating an Insurance Company after a Merger

41 Business Functions Customer information Product information Insurer Product information Customer information Maintaining Intermediary Relations Maintaining Customer Relations Insurance information Claims Customer Intermediary Customer information Claims Contracts Contracting Insurance policies Claims Handling Claim information Insurance policies Claims Asset Management Money Money Financial Handling Claim payments Insurance premiums Customer s Bank

42 Product Customer "be insured" (security) Travel Insurance Insurance application Premium payment Customer data mutation Travel insurance policy Claim registration Customer information Claims payment

43 Organisation ArchiSurance Customer Relations Intermediary Relations Front Office Home & Away Car Back Office Legal Aid Document Processing SSC Finance Product Development HRM

44 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

45 Applications Front office Call center application Web portal Legal Aid CRM application Legal Aid CRM Home & Away Car Home & Away Policy administration Car Insurance application Legal Aid backoffice system Home & Away Financial application

46 Business Functions Maintaining Customer & Intermediary Relations Landscape map Products Home Insurance Travel Insurance Liability Insurance Web portal Call center application Car Insurance Customer relationship management system Legal Aid Insurance Legal Aid CRM Contracting Claim Handling Financial Handling Home & Away Policy administration Home & Away Financial application Car insurance application Legal Aid back office system Document Processing Document management system

47 Business Processes & Services Customer Insurance application Claim registration Claims payment Customer information Premium payment Close Contract Handle Claim Inform Customer Collect Premium

48 Application Usage Handle Claim Register Accept Valuate Pay Scanning Customer administration Claims administration Printing Payment Document management system CRM application Home & Away Policy administration Home & Away Financial application

49 Application Structure Home & Away Policy administration Risk Assessment Claim data management Policy data management Customer data access Insurance request data Damage claim data Insurance policy data Customer file data

50 Infrastructure ArchiSurance NAS File server Intermediary Mainframe LAN Firewall TCP/IP Network Firewall LAN Admin server Message Queing DBMS Unix server farm CICS Unix server Unix server

51 Deployment Web portal Call center application CRM application Home & Away Policy administration Home & Away Financial application Car Insurance application Document management system Legal Aid backoffice system Unix server farm Mainframe NAS File server LAN Firewall Network

52 Relation to Other Developments

53 Boundaries Strategy Change Principles Business domains ArchiMate Time Realisation Method Location Physical resources Semantics Metadata

54 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

55 Information Behaviour Structure Attributes Natural language ArchiMate and Zachman What How Where Who When Why Scope = Planner s view Contextual Enterprise Model = Owner s view Business Conceptual System Model = Designer s view Application Logical Technology Model = Builder s view Technology Physical Detailed representation = Subcontractor s view As Built Functioning Enterprise = User's view Functioning

56 ArchiMate and The Open Group

57 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.

58 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

59 TOGAF and ArchiMate Preliminary H Architecture Change Management A Architecture Vision B Business Architecture Business Architecture G Implementation Governance Requirements Management C Information Systems Architectures Data Architecture Application Architecture Application F Migration Planning E Opportunities and Solutions D Technology Architecture Technology Architecture Technology TOGAF ADM ArchiMate

60 ArchiMate Usage in Practice

61 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

62

63

64

65 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)

66 ?

67 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 Lankhorst@telin.nl