ArchiMate Tutorial The open standard language for modelling en visualizing enterprise architecture Remco Blom, BiZZdesign
Created with Wordle.net
Do you recognize this? Information architecture? Product architecture Process architecture?? Application architecture? Technical architecture?
Proposed schedule Introduction Enterprise Architecture ArchiMate Motivation and scope Framework Examples Meta model Views and viewpoints Relations with other languages Support for ArchiMate Summary
Enterprise Architecture Some basic concepts
Enterprise Architecture ISO/IEC 42010: Architecture: the structure of a system in terms of its components, their externally visible properties, their relations, and the underlying principles Structure with a vision
Why Enterprise Architecture? Managing change and complexity: Aligning business and IT Outsourcing Impact analysis Project support (project start architectures) Portfolio management Communication with stakeholders Obtaining insight in current situation (as-is) So enterprise architecture as a tool for communication for governance for innovation Flickr by neil nathanson
Views on Enterprise Architecture? A process Way of working Aimed at the development and use of enterprise architectures within an enterprise With people and resources A product A design that shows the coherence between products, processes, organisation, information supply and infrastructure, based on a vision and certain explicit starting points, principles and preferences With the objective of steering changes Information architecture? Application architecture? Process architecture?? Technical architecture?
Important notions (IEEE 1471) A stakeholder is a person or organisation with a certain interest in (part of) an architecture A view is a representation of a system from the perspective of a set of concerns of one or more stakeholders. A view is what you see. A viewpoint is where you are looking from. It defines how to build a view, e.g. by means of a template. Different stakeholders Have different interests and use different concepts Have different views Have different viewpoints On the basis of one consistent architectural model
Example viewpoint en view Example 1 Stakeholder: city council Concern: development plan Viewpoint: photo of district from the air View: Aerial Example 2 Stakeholder: house owner Concern: building permit Viewpoint: Corner of the street, scope is one house View: Ground photo
IEEE 1471 (summary) Stakeholder is important to 1..* is addressed to 1..* has 1..* Concern used to cover 1..* Viewpoint conforms to View participates in 1..* establishes methods for 1..* consists of 1..* Model
Ingredients of an EA Approach TOGAF ArchiMate Process Viewpoints Language Enterprise Continuum, Repository, Reference Models
Why one language? Communication No ambiguity Coherence Consistency Visualization Analysis
ArchiMate A language for describing architectures Covers business, application and technology layers With relations between these layers Graphical language with formal semantics, enabling analysis and tool support Techniques for visualization and analysis, aimed at various stakeholders Open standard maintained by The Open Group See www.opengroup.org/archimate or www.archimate.org
The ArchiMate Language High-level modelling within a domain ArchiMate language Basis for visualisations modelling relations between domains Relate to standards Basis for analyses
Layers, Aspects, and Domains Environment Product domain Business Information domain Process domain Organization domain Application Data domain Application domain Technology Technical infrastructure domain Passive object Behaviour verb Active subject
Language summary Business Representation Business object Business service Business process Business interface Business role Business actor Application Data object Application service Application function Application interface Application component Technology Artifact Infrastructure service System software Infrastructure interface Node Network
Some examples of the ArchiMate language for educational purposes Examples created using BiZZdesign Architect
Products and services Contract Product Value Role Insurance Policy Damage insurance Being insured Customer Policy mutation Service Payment Service Policy Service Premium Service Declaration Service Aggregation Association Business services
Processes and roles Event Process Event Damage notification Accept and Register claim Assess claim Pay claim :-) customer Administrative employee Taxateur Employee Finance Specialist Car damage Role Triggering Assignment
Business functions System development Marketing Product development Customer relations Financial handling Claims handling Asset management Contracting Facturation Assessment Risk management Contract changes Collecting Acceptance Treasury Customer changes Composition (by nesting) Business Function
Business objects Insurance request Insurance Damage data Life insurance Travel insurance Pension insurance Damage insurance Damage form Aggregation Specialization Realization Business object Representation
Applications and application services Accept and Register claim Assess claim Business process Register Service Acceptation Service Assessment service Application service Registration systeem Assessment system Application component Customer administration system Used-by Realization Composition Payment system Acceptation system Acceptation Interface Application interface
Infrastructure Acceptation system Claim Files Service Customer administration system Customer File Service Application component Infrastructure service System software Mainframe CICS NAS File Server Unix Server Farm Node Used-by Realization Assignment Composition Message Queing DBMS Network LAN Firewall Profit Unix Server 1 Unix Server 2 Device
Layered view Declaration Service Payment Service Damage notification Accept and Register claim Assess claim Pay claim :-) customer Acceptation Service Assessment service Customer administration service Payment system Acceptation system Assessment system Customer administration system Messaging service Claim Files Service Customer File Service Message Queing Mainframe DBMS CICS NAS File Server
Derived relations
Generic meta model ArchiMate External Internal Passive structure Behaviour Active structure
Business layer meta model
Application layer meta model
Technology layer meta model Infrastructure service Infrastructure interface Artifact Node Communication path System software Device Network
Some examples from daily practice
Example: City of Enschede - 1 Vaststelling huisnummers (Basisregistratie Vastgoed) Staatnaamgeving (Basisregistratie Vastgoed) Product Registreren adressen/straten Wijzigen adressen/straten ADR4all Registreren gebieden Wijzigen gebieden Application with functions Afmelden straten/adressen Afmelden gebieden Straat Huisnummer + letter + toevoeging Adres Gebied Stadsdeel Buurt Application data objects Postcode Wijk ADR4all database Database
Example: City of Enschede - 2 Bestand uitvoerder bodemonderzoek Bodemsanering (Uitvoering Milieu) Bodemonderzoek (Uitvoering Milieu) Wet-bodembescherming Controle bodem (Handhaving milieu) (Uitvoering Milieu) SIKB tool BIS4all SUB4all (voor BIS4all) Import XML bodemonderzoeksdata Registreren bodemonderzoeken Registreren locaties onderzoek Registreren bodemverontreininging Export naar XML Registreren potentieel vervuilde locatie Managementrapportages ArcView Analyseresultaten Peilbuisgegevens Boorgegevens Status Bodeminformatie Geografische contouren Soort Kosten Vergunning / besluit Adres Kadastrale gegevens Geografische informatie Subject BIS4all database ADR4all database KAD4all database GDS SUB4all database voor BIS
Example: City of Enschede - 3 Applicaties Aan- en verkoopboek Verwervingsysteem VR-Beheer Beheersysteem onroerend goed Speeltoestel BIS4all PIV4all ADR4all Rioolkaarten RBS DHV Basisbeheer DHV Rioolbeheer DHV Wegbeheer BWT4all Plan32 Melddesk G4net Gegevensobjecten die met adressen / locaties te ameken hebben Adres Verblijfplaats Straat Locatie Huisnummer Adreshistorie Postcode Huisnummer + letter + toevoeging Onderliggende databases G4net database Speeltoestel database Verwervingssyteem database RBS database ADR4all database VR-Beheer database PIV4all database Beheersysteem database Aan- en verkoopboek database Database rioolkaarten Plan32 database Melddesk database DHV database Which data is used by which application, and stored in which database
Example: 3 technical universities Activiteitoverstijgende informatievoorziening Nieuwe informatie beschikbaar Ophalen informatie Bewerken informatie Beschikbaar stellen informatie Informatie is aangeboden Legenda Via: - Toekenningsrelatie Naar: - Bedrijfsactor Student Onderwijsondersteuning Opstellen berichten A process Docent Use of business objects (access relation by nesting) Per opleiding de ingeschreven studenten Profielinformatie Legenda Via: - Toekenningsrelatie Naar: - Bedrijfsactor Onderwijsondersteuning Student Docent Ophalen informatie Workflow informatie Voorkeurskanaal Activiteitoverstijgende informatievoorziening Bewerken informatie Per opleiding de ingeschreven studenten Opstellen berichten Beschikbaar stellen informatie Mededelingen Huisregels Mededelingen Nieuwsberichten Nieuwsberichten
Example: 3 technical universities Ophalen informatie Resultaten raadpleegservice Activiteitspecifieke informatievoorziening Bewerken informatie Informatie over activiteit bewerkservice Beschikbaar stellen informatie Notificatieservice Rooster raadpleegservice Resultaten raadpleegservice Onderwijscontent raadpleegservice Profielinformatie service Profielinformatie bewerkservice Informatie over activiteit raadpleegservice Onderwijscontent bewerkservice Inschrijving raadpleegservice Deelnemerslijst raadpleegservice Inschrijving raadpleegservice Onderwijscontent raadpleegservice Resultaten bewerkservice Informatie over activiteit raadpleegservice Nieuwsberichten service Profielinformatie raadpleegservice Opstellen berichten Nieuwsberichten service Use of application services by the process (used by relation by nesting)
Viewpoints and views in ArchiMate Classifications and examples
Less is more let s ask the architect to leave out this rubbish, then we will get a nice result!
Classification viewpoints ArchiMate product manager, CIO, CEO architect, software developer, business process designer Designing Deciding Informing customer, employee, others Goal Details Coherence Contents Overview
Viewpoint Types Viewpoints for designing typically used by architects in the design process Examples: Application diagram, Process diagram Viewpoints for deciding intended to support managers in making decisions Examples: landscape map, cross-reference table, analysis report Viewpoints for informing inform stakeholders about an architecture Examples: process illustration, animation, cartoon
Level of Detail Details small part of an architecture with high level of detail e.g. for a software engineer designing and implementing a component, or process owner responsible for optimizing a process Coherence spans multiple aspects or layers and shows their relations e.g. for an operational manager responsible for IT support for a number of business processes Overview abstract, comprehensive view of multiple aspects and layers for enterprise architects and upper-level managers
Examples views Register Service Acceptation Service Assessment service Registration systeem Assessment system Document Information System Customer administration system Payment system Acceptation system Acceptation Interface
Modelling and Views Klant Verzekerde Declaration Service Payment Service Polismutatie Service Declaratie Service Polis Service Premie Service Schadebetaling Service Damage notification Accept and Register claim Assess claim Pay claim :-) customer Behandelen claim Acceptation Service Assessment service Customer administration service Registreren Accepteren Beoordelen Uitbetalen Registratie Service Acceptatie Service Beoordelings service Klantbeheer service Verzekeraar Payment system Acceptation system Assessment system Customer administration system Messaging service Claim Files Service Customer File Service Registratie systeem Acceptatie systeem Beoordelings systeem Klantbeheer applicatie Message Queing Mainframe DBMS CICS NAS File Server Data access service Document informatie service Messaging service Claim Files Service File Service Controle service Customer File Service Mainframe DBMS Message Queing CICS NAS File Server
Roadmapping: differences as-is/to-be Register Service Acceptation Service Assessment service Legenda Show differences between periods both in 2006 - current state and 2010 - future state only in period 2006 - current state only in period 2010 - future state Registration systeem Assessment system Document Information System Customer administration system Payment system Acceptation system Acceptation Interface
ArchiMate and Flickr by nicolas demers-stoddart
ArchiMate and other languages ArchiMate: perfect starting point for MDA and software development ArchiMate incorporates the service paradigm ArchiMate has implementation relationships to process modelling languages (BPNM, BPEL) ArchiMate has implementation relationships to software engineering design languages (UML) ArchiMate connects architectural domains It has a broader scope, but less detail than UML and BPMN It does not replace specialized languages for different architectural domains, such as UML, BPMN and others
ArchiMate and the ADM Business layer Application layer Technology layer Information Behaviour Structure
ArchiMate and support ArchiMate is commercially supported By (certified) toolvendors BiZZdesign: Architect Casewise: Corporate Modeler IDS Scheer: Aris ArchiMate Modeler Telelogic: System Architect Troux: Metis By a large number of service providers like Atos Origin, BiZZdesign, Capgemini, Getronics, Logica, Ordina, And used by many organisations Finance, governance, transport, energy, water, education, health care, health insurance, industry, public sector,
ArchiMate in HE
ArchiMate and Service providers
ArchiMate and The Open Group ArchiMate is maintained by The Open Group Including certification for tool support, training and individuals The ArchiMate Forum platform and community for everyone involved with the use and evolution of ArchiMate Henry Franken (chair, BiZZdesign) Erik Proper (vice-chair, Capgemini) Roland Ettema (Logica) Garry Doherty (director Open Group)
Modelling..YES WE CAN! The language for describing enterprise architectures Covers business, application and technology layer With relations between these layers Graphical language with formal semantics, enabling analysis and tool support Techniques for visualization and analysis, aimed at various stakeholders Widely supported Open standard maintained by The Open Group
Question? Created with Wordle.net