ArchiMate: A Modeling Language for Enterprise Architecture

Transcription

1 INF5120 F7 part 2: March 5 th, 2007 ArchiMate: A Modeling Language for Enterprise Architecture From the book : Enterprise Architecture at Work Modeling,Communication and Analysis By Marc Lankhorst et. al Telematica Instituut The Netherlands See + artikkel: Enterprise Modeling Overview Introduction Enterprise architecture & ArchiMate The ArchiMate modeling language Integration of business, applications, and technology Service orientation Example Communicating architectures ArchiMate adoption in practice 1

2 Partners Telematica Instituut Enterprise Architecture & ArchiMate 2

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

4 Governance With Architecture Architecture is a strategic tool not just high-level design Architecture goes beyond ICT: enterprise architecture Stability & flexibility Seem to be contradictory, but a good architecture facilitates change! Communication with stakeholders architects, managers, customers, engineers, Analysis impact-of-change cost & performance 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 4

5 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 models in many languages (UML, IDEF, BPMN, ARIS,...) Communicating about architecture with others Tool interoperability Needed: well-founded and practical standard for enterprise architecture modeling 5

6 ArchiMate Focus Visualization Analysis Integration What Has ArchiMate Delivered? A vision on enterprise architecture Focus on the relations between business and IT A language for describing architectures models give precision and make tool support possible Techniques for visualisation and analysis, aimed at various stakeholders A basis and vision for tools Visio stencils Long term goal: vendor-independent standard for architecture description 6

7 Integrated Modelling Integration An architecture might encompass for example: products organisation business processes applications systems This requires concepts for domains and relations, linked with existing techniques 7

8 The ArchiMate Language High-level modeling within a domain ArchiMate language Basis for visualizations Modeling relations between domains Basis for analyses Layers, Aspects, and Domains Environment Business Information domain Product domain Process domain Organization domain Application Data domain Application domain Technology Technical infrastructure domain Information Behavior Structure 8

9 Generic Structure at Each Layer External Internal Information Behavior Structure Business Functions and Actors business actor ArchiSurance assignment Contracting Insurance policies Claim Handling business function flow 9

10 Product and Services business role value Customer Security product Travel Insurance Insurance application Claim registration Customer information Claim payment Policy business contract Business Process Customer business actor Insurant business role Claim registration business Customer Information realisation Handle Claim used by Claim payment business object Damage occurred Register Accept Valuate Pay Notification event business process access 10

11 Business Interactions Insurer ArchiSurance Customer business actor business collaboration Claim registration partners aggregation Insurant business role assigment Register business interaction 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 11

12 Business Layer Metamodel Product Meaning Value Representation Contract Business Business interface Business collaboration Event Business object Business process / function / interaction Business role Business actor Application Concepts application Policy creation application interface application component Policy administration Financial administration Policy creation Premium collection application function data object Policy data application interaction Customer file data 12

13 Application Usage by Business Processes Handle claim Registration Acceptance Valuation Payment Notification Customer administration Claim administration Payment CRM system Policy administration Financial application Notification data Application Layer Metamodel 13

14 Technology Concepts Database access MQ messaging Infrastructure Database tables artifact zseries Mainframe DB2 Database LAN Sun Blade iplanet App. server Fin. application EJBs system software network association device Deployment of Applications CRM system Policy administration Financial application Notification data Database access MQ messaging Database tables zseries Mainframe DB2 Database LAN Sun Blade iplanet App. server Fin. application EJBs 14

15 Technology Layer Metamodel Infrastructure Infrastructure interface Artifact Node Communication path System software Device Network Roles and actors Layered Architecture Business layer Client Insurant ArchiSurance Insurer External business s Claim registration Damage claiming process Customer information Claims payment Registration Acceptance Valuation Payment External application s Customer administration Claims administration Payment Application components and s Application layer Customer information CRM system Claim information Policy administration Financial application External infrastructure s Claim files Customer files Infrastructure Technology layer zseries mainframe DB2 database Sun Blade iplanet app server Financial application EJBs 15

16 Services as Binding Concept Customer External business Business External application External infra. Internal business Internal application Internal infra. Application Technology ArchiMate in Practice: Tax Administration - UWV 16

17 Service-Oriented Business Process Integration Company/ Agent Tax and Customs Administration UWV Submit tax return Process payroll tax return TCA Transfer tax return data Process corrections Process payroll tax return UWV Payroll tax return Process Refinement Tax and Customs Administration Payroll tax return Submit tax return Process payroll tax return TCA Receive tax return Transfer tax return data Confirmation Relations information Notification rejection Levy Correction request Collections administration Levyings administration Notification error Send notification Notify Process corrections Process corrections 17

18 Detailed Process with Application Support PTR msg. F = / month Paper PTR F = / month small: 98,10% web: 1,72 % Receive paper PTR Receive PTR Scan document document Receive electronic PTR Receive decode PTR small Legal archive large: Receive 0,17 % PTR large Receive PTR web Receive tax return Medium- independent processing make available receive and convert check handle notify receipt Nominative discards data DCS Electronic PTR MOS OB 2000 FOL FOS FOS external internal FOS Temporary storage file BvR BBA WGA AVANTi Notification UKV internal messaging Process Detailed Applications Medium- independent processing Medium independent PTR Nominative lines Structural conversion Convert PTR file Collective lines Receive and check PTR processing 10% Handle discards Notify receipt Make available Send nominative lines Message Conversion Message Reception FOS Internal PTR Data XMLmessage conversion & splitting Receive message Receive PTR Send PTR Nominative part Collective part AVANTi UKV internal messaging 18

19 Applications Infrastructure PTR data MTA in P44 in P44 discardshandling BAPI unpack MQ dispatch MOS FOS internal OB2000 App. hosting Sybase access Message switch MQ messaging Execution environment Discards administration BS Ch. MOS ->FOS Sybase DBMS QM QM APMOSU7- MOS production APFOSU 4- FOS internal production Total Infrastructure Message store FOL DCS FOS Extern MOS FOSintern AVANTi UKV intern bericht App. hosting Berichtenswitch MQ messaging App. hosting Berichtenswitch Berichtenswitch messaging MQ Opvolger OB2000 App. hosting Sybase toegang MQ messaging FBX Gateway App. hosting Berichtenswitch MQ messaging Mesg. broker DB toegang MQ messaging MQ messaging CICS DB toegang MQ MQ messaging messaging Mesg. broker Web Application server BS Ch. FOL ->FOS Executieomgeving BS Ch. DCS ->FOS Executieomgeving Uitval- Admin. BS Ch. MOS ->FOS BS Executieomgeving XIB Ch. FOS -> Msg. Store MB Message admin. Ch. Avanti-> Msg. Store Ch. FOS-> Avanti CICS poort fabriek Admin. Ch. AVANTi ->UKV MB Sybase DBMS Message database DB2UAVIDB 01 MQ Poort cluster QM QM QM QM QM QM QPE1 QM QPE2 QM FOL -Formulieren Online (2 of 3) Document Conversie Systeem APMOSU7-MOS productie APFOSU1-FOS extern productie, APFOSU2 APFOSU4-FOS intern productie, APFOSU3 Unix Server - Message Store P-partitie-Mainframe Exploitatie ( Particulieren en Ondernemingen) Unix-cluster: UKV intern Berichtenserver 19

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

21 Viewpoints Classification product manager, CIO, CEO architect, software developer, business process designer Designing Deciding Informing customer, employee, others Details Coherence Overview 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 21

22 Application Behaviour Policy creation Home & Away Policy administration Policy creation Calculate risk Calculate premium Create policy Store policy Insurance request Insurance policy Customer file 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 22

23 Landscape map ArchiSurance Business Functions Products Maintaining Customer & Intermediary Relations 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 Viewpoints for Informing Process illustration Goal is communication Pictures aimed at non-architects $ Kluis Archief Bestand bericht document 23

24 Process Illustration (I) Roles Particulier Douane eenheid BCICT RDW Inning External Organisational s Aangifte behandeling Aangifte betaling Administratie Inning Balie Aangifte adiministratie Fiattering BPM process Klant behandeling adiministratie inning aangifte Kluis Geld Archief Application components Aangifte bestand Vordering BPM client RIN Catalogus Waarde BPM server Betaling Infrastructure BPM workstation (Douaneeenheid) WAN BPM server (BCICT) W AN RIN server (Inning) Process Illustration (II) RDW acceptgiro BPM 17 ex3 BPM 17 ex2 Archief Administratie betaling BPM aangiftepunt Douane eenheid $ Kluis Balie Behandeling BPM 17 ex1 BPM workstation (Douane eenheid) BCICT automatiserings centrum betaling Aangifte Bestand betaling Catalog. waarde BPM server (BCICT) vordering aangifte RIN server (Inning) Inning Inning 24

25 ArchiMate Adoption ArchiMate and TOGAF TOGAF: The Open Group Architecture Framework Provides methodical support for architects Architecture Development Method (ADM) gives you a process ArchiMate and TOGAF nicely complement each other: ArchiMate provides no architecture process TOGAF provides no architecture modelling technique E.g. Atos Origin NL use ArchiMate and TOGAF together 25

26 ArchiMate and Zachman What? How? Where? Who? When? Why? Planner Owner Designer Builder Subcontractor Information Business Behaviour Application Technology Structure Attributes Natural language Scope (contextual) Enterprise model (conceptual) System model (logical) Technology model (physical) Detailed representations Data Function Network People (out of context) Time Motivation ArchiMate and UML ArchiMate connects architectural domains It has a broader scope, but less detail than UML It acknowledges the need for specialized languages for different architectural domains, such as UML, BPMN and others Transformations to more detailed, specialized models Several ArchiMate concepts derived from UML (esp. for application and infrastructure) First version of a UML profile for ArchiMate available 26

27 ArchiMate and Model-Driven Architecture Computation Independent Model (CIM) Business model Domain model Business requirements Platform Independent Model (PIM) e.g. BPMN Model independent of workflow engine, or UML model independent of computing platform mapping mapping mapping mapping ArchiMate may help bridge the gap between CIM and PIM ArchiMate Platform Specific Model (PSM) e.g. UML model for a J2EE platform Results in Practice Applications at over 30 organizations e.g. Dutch Tax Administration and many other companies and government institutes Tools BiZZdesign, Troux Metis (certified) IDS Scheer, Adaptive, Telelogic (implementing) MEGA, Casewise, ASG, IBM (interested) Education Used by several Dutch universities and other educational institutes Rapidly growing international attention 27

28 ArchiMate Users User organizations CFI Dutch Tax Administration CITO ABN AMRO Leiden University ABP Avans Hogeschool SVB UWV Hogeschool van Amsterdam ABZ Fontys Hogescholen VGZ-IZA NHTV SNS Reaal ICT consultants Interpolis Ordina Zwitserleven Fortis Getronics PinkRoccade Quion Sogeti Stater Atos Origin NS CIBIT TNT LogicaCMG Philips Tool vendors Kluwer BiZZdesign Vitens Troux Dutch Police Autoriteit Financiële IDS Scheer Markten Adaptive Province of Groningen Province of Overijssel Province of Gelderland Ministry of the Interior Raad van State Agilense Research & education Telematica Instituut Leiden University Radboud University Nijmegen Centrum voor Wiskunde & Informatica Hogeschool van Amsterdam Avans Hogeschool CIBIT University of Twente Lisbon Technical University Delft University of Technology TU Eindhoven ArchiMate Forum Open cooperation between ArchiMate users, vendors, educators, and consultants Long term objective: An independent standard for describing enterprise architectures Goals of the ArchiMate Forum: Creating critical mass Supporting organizations in applying ArchiMate Contributing to international standards 28

29 Members ArchiMate Forum 29