Moving from Checkmate to ArchiMate An introduction to the ArchiMate Forum & Language Louw Labuschagne Certified TOGAF Practitioner

Agenda  Why use a formal Enterprise Architecture Language  Where did ArchiMate originate  How is ArchiMate constructed  When should you use different views  What do I need to know when modelling in a tool  Who do I contact to join the Open Group or the ArchiMate Forum

Agenda  Why use a formal Enterprise Architecture Language  Where did ArchiMate originate  How is ArchiMate constructed  When should you use different views  What do I need to know when modelling in a tool  Who do I contact to join the Open Group or the ArchiMate Forum

Have you ever seen the following happen?    ABCDEFABCDEF MNOPQRMNOPQR G  H  I  J K  L  STUVWXSTUVWX YZYZ Apply English Language Rules

Can you now answer the question? THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG...Because everyone in the room were taught the english language rules...  Standard form for each shape  Standard spelling for using shapes  Standard pronunciations for each shape  Standard meanings of each shape  Standard rules for the use of shapes

Key requirements of an Enterprise Architecture Modelling Language  Focused on modelling inter-domain relations  Modelling the global structure within each domain, showing the main elements and their dependencies, in a way that is easy to understand for non-experts of the domain  Models must be interpreted in an unambiguous way  Visualise models in a different way, tailored towards specific stakeholders with specific information requirements

Introduction to [Ahr-ki-meyt]  ArchiMate provides instruments to support enterprise architects in describing, analysing and visualising the relationships among business domains in an unambiguous way  ArchiMate is an open and independent modelling language for enterprise architecture  Supported by leading EA tool vendors  Tailored towards specific stakeholders addressing specific information requirements

Agenda  Why use a formal Enterprise Architecture Language  Where did ArchiMate originate  How is ArchiMate constructed  When should you use different views  What do I need to know when modelling in a tool  Who do I contact to join the Open Group or the ArchiMate Forum

History  ArchiMate Language Primer  2004 Telematica Instituut  guage=nl guage=nl  ArchiMate Made Practical  2007 Archimate Foundation   ArchiMate 1.0 Technical Standard  2008 Open Group Review of the Technical Standard 

Focus of the ArchiMate Forum  Standardise ArchiMate version 1.0  maintain backward compatability  Develop ArchiMate 2.0 draft standard  tighter integration with TOGAF  still ensuring backward compatibility

Agenda  Why use a formal Enterprise Architecture Language  Where did ArchiMate originate  How is ArchiMate constructed  When should you use different views  What do I need to know when modelling in a tool  Who do I contact to join the Open Group or the ArchiMate Forum

Services Approach  A service is defined as a unit of functionality that some entity (e.g., a system, organisation or department) makes available to its environment, and which has some value for certain entities in the environment.

Layered Approach

Language Elements  Behavioural or dynamic aspect  Behavioural concepts are assigned to structural concepts, to show who or what displays the behaviour  Structural or static aspect  Active structural elements  the business actors, application components and devices that display actual behaviour, i.e., the ‘subjects’ of activity  Passive structural elements  i.e., the objects on which behaviour is performed  External view and an internal view  For the external users, only this external functionality, together with non-functional aspects such as the quality of service, costs etc., are relevant

ArchiMate Notation Passive Structure Active Structure Behaviour

Example

Agenda  Why use a formal Enterprise Architecture Language  Where did ArchiMate originate  How is ArchiMate constructed  When should you use different views  What do I need to know when modelling in a tool  Who do I contact to join the Open Group or the ArchiMate Forum

ArchiMate Viewpoints Purpose: navigate, design, support design decisions, compare alternatives Purpose: decision-making Purpose: explain, convince, obtain commitment Stakeholders: software engineer, process owner Purpose: design, manage Stakeholders: operational managers Purpose: Analyse dependencies, impact-of-change Stakeholders: enterprise architect, CIO,CEO Purpose: change management

ArchiMate Informing Viewpoints These viewpoints help to inform any stakeholder about the enterprise architecture, in order to achieve understanding, obtain commitment, and convince adversaries. Typical examples are illustrations, animations, cartoons, flyers, etc.

Informal Notation Passive Structure Active Structure Behaviour

Whiteboard Friendly  The Introductory viewpoint tries to avoid the impression that the architectural design is already fixed, an idea that may easily arise when using a more formal, highly structured or detailed visualisation  No technology required  Good workshop technique with stakeholders

Decision Support Viewpoints Decision support views assist managers in the process of decision making by offering insight into cross-domain architecture relations, typically through projections and intersections of underlying models, but also by means of analytical techniques. Typical examples are cross-reference tables, landscape maps, lists and reports.

Visio  Visio Templates available from ArchiMate Foundation website  The model on the right is used as an example of how to abstract a view for easy communication using a tool like Visio

Example  Shapes can be substituted to assist with communication

Example  New images are used to replace the standard shapes

Example  The shapes are abstracted based on the rules defined in the ArchiMate standard

ArchiMate Design Viewpoints Design viewpoints support architects and designers in the design process from initial sketch to detailed design. Typically, design viewpoints consist of diagrams, like those used in e.g. UML.

Agenda  Why use a formal Enterprise Architecture Language  Where did ArchiMate originate  How is ArchiMate constructed  When should you use different views  What do I need to know when modelling in a tool  Who do I contact to join the Open Group or the ArchiMate Forum

ArchiMate Domains

Meta Model

ArchiMate Concepts: Business

ArchiMate Concepts: Application

ArchiMate Concepts: Technology

ArchiMate Design Viewpoints  From any given element in a model, we can define viewpoints in four metaphorical directions: 1.‘inwards’, toward the internal composition of the element; 2.‘upwards’, towards the elements that are supported by it; 3.‘downwards’, toward its realisation by other elements; 4.‘sideways’, towards peer elements with which it cooperates.

Composition: Business Function VIEWPOINT NAME Business Function STAKEHOLDERSEnterprise, process, domain architects CONCERNSIdentification of essential activities Identification of compentencies Reduction of complexity PURPOSEDesigning ABSTRACTION LEVEL Coherence LAYERSBusiness ASPECTSBehaviour,(Active)

Example Composition: Business Function

Cooperation: Actor VIEWPOINT NAME Actor Cooperation STAKEHOLDERSEnterprise, process, domain architects CONCERNSRelations of actors with their environment PURPOSEDesigning ABSTRACTION LEVEL Coherence LAYERSBusiness, (application) ASPECTSStructure, behaviour

Example Cooperation: Actor

Support: Infrastructure Usage VIEWPOINT NAME Infrastructure Usage STAKEHOLDERSApplication, infrastructure architects Operational managers CONCERNSDependencies, performance, scalability PURPOSEDesigning ABSTRACTION LEVEL Coherence LAYERSApplication, technology ASPECTSActive, (behaviour)

Example Support: Infrastructure Usage

Realisation: Service Realisation VIEWPOINT NAME Service Realisation STAKEHOLDERSProcess, domain architects Product & operational managers CONCERNSAdded value of business processes Consistency & completeness Responsibilities PURPOSEDesigning, deciding ABSTRACTION LEVEL Coherence LAYERSBusiness, (application) ASPECTSBehaviour, (active), (passive)

Example Realisation: Service Realisation

Agenda  Why use a formal Enterprise Architecture Language  Where did ArchiMate originate  How is ArchiMate constructed  When should you use different views  What do I need to know when modelling in a tool  Who do I contact to join the Open Group or the ArchiMate Forum

Open Group or ArchiMate Forum Membership Enquiries Sarina Viljoen Certified TOGAF Practitioner Tel: Fax: Mobile: Skype: sarina.viljoen