1 / 44

Moving from Checkmate to ArchiMate

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

nadda
Download Presentation

Moving from Checkmate to ArchiMate

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

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

  4. Have you ever seen the following happen? THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG A A B B C C D D E E F F G G H H I I J J K K L L M M N N O O P P Q Q R R S S T T U U V V W W X X Y Y Z Z Apply English Language Rules

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

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

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

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

  9. History • ArchiMate Language Primer • 2004 TelematicaInstituut • http://www.telin.nl/index.cfm?ID=252&context=253&language=nl • ArchiMate Made Practical • 2007 Archimate Foundation • http://www.archimate.org/ • ArchiMate 1.0 Technical Standard • 2008 Open Group Review of the Technical Standard • http://www.opengroup.org/archimate/

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

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

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

  13. Layered Approach Business Layer • The Business layer offers products and services to external customers, which are realised in the organisation by business processes performed by business actors. Application Layer • The Application layer supports the business layer with application services which are realised by (software) applications. Technology Layer • The Technology layer offers infrastructural services (e.g., processing, storage and communication services) needed to run applications, realised by computer and communication hardware and system software.

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

  15. ArchiMate Notation Active Structure Passive Structure Behaviour

  16. Example

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

  18. ArchiMate Viewpoints Purpose: decision-making Purpose: navigate, design, support design decisions, compare alternatives 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

  19. ArchiMateInforming 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.

  20. Informal Notation Active Structure Passive Structure Behaviour

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

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

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

  24. Example • Shapes can be substituted to assist with communication

  25. Example • New images are used to replace the standard shapes

  26. Example • The shapes are abstracted based on the rules defined in the ArchiMate standard

  27. ArchiMateDesign 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.

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

  29. ArchiMateDomains

  30. Meta Model

  31. ArchiMate Concepts: Business

  32. ArchiMate Concepts: Application

  33. ArchiMate Concepts: Technology

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

  35. Composition: Business Function

  36. Example Composition: Business Function

  37. Cooperation: Actor

  38. ExampleCooperation: Actor

  39. Support: Infrastructure Usage

  40. ExampleSupport: Infrastructure Usage

  41. Realisation: Service Realisation

  42. ExampleRealisation: Service Realisation

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

  44. Open Group or ArchiMate Forum Membership Enquiries Sarina Viljoen Certified TOGAF Practitioner e-mail s.viljoen@opengroup.org Tel:  +27 11 805 3734 Fax: +27 86 532 0704 Mobile: +27 82 825 3496 Skype: sarina.viljoen www.opengroup.org

More Related