Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Archimate - an introduction

633 visualizaciones

Publicado el

An introduction to Archimate 3.0, with a strong emphasis on the technology layer

Publicado en: Tecnología
  • Sé el primero en comentar

Archimate - an introduction

  1. 1. AN INTRODUCTION TO (c) 2018, Stefan Luyten
  2. 2. SETTING THE SCENE
  3. 3. ARCHIMATE DIFFERENT WORLD, DIFFERENT FRAMEWORKS
  4. 4. ARCHIMATE SCOPE VS LEVEL OF DETAIL SC ScopeSC Simple Detailed BUSINESS MODEL BUSINESS PROCESS MODEL SOFTWAR E MODEL INFRASTR UCTURE MODEL STRATEGI C MODEL DATA MODEL ENTERPRISE MODEL
  5. 5. OVERVIEW
  6. 6. ARCHIMATE WHAT IS ARCHIMATE ? ▸A common language for describing: ▸Business processes ▸Organizational structures ▸Information flows ▸IT systems and applications ▸Technical infrastructure ▸The dependencies and interactions between all of the above ▸Archimate is for an organization what blueprints are for a building: ▸Different views (Structures, electricity, plumbing, …) ▸Different stakeholders & views (Mason, electrician, plumber, …)
  7. 7. PASSIVE STRUCTU RE BEHAVIO UR ACTIVE STRUCTU RE ARCHIMATE ARCHIMATE LAYERS & ASPECTS BUSINESS APPLICATION TECHNOLOGY Layers Aspects
  8. 8. ARCHIMATE THE FULL PICTURE
  9. 9. ARCHIMATE EXAMPLES - BUSINESS LAYER (STRUCTURE)
  10. 10. ARCHIMATE EXAMPLES - APPLICATION LAYER (STRUCTURE) Active structure Passive structure
  11. 11. ARCHIMATE EXAMPLES - APPLICATION LAYER (BEHAVIOUR) SAME AS ON PREVIOU S SLIDE SAME AS ON PREVIOU S SLIDE All archimate elements will be stored in a central, version-controlled database Can be queried, for example: “show me all relations with the eCommerce platform” “The eCommerce platform has 2 interfaces and contains 1 process”
  12. 12. ARCHIMATE EXAMPLES - APPLICATION LAYER (STRUCTURE) Active structure Passive structure
  13. 13. HOW TO START
  14. 14. ARCHIMATE GENERAL APPROACH ▸Keep it lean: only model what you’ll need ▸Start with added value by expressing it as a service (WHAT is needed) ▸Continue with HOW the service will be offered and WITH WHAT it will be implemented
  15. 15. ARCHIMATE WHAT - HOW - WITH WHAT WHAT HOW WITH WHAT Behaviour Structure Behaviour Structure
  16. 16. ARCHIMATE WHWW - EXAMPLE 1 WHAT HOW WITH WHAT
  17. 17. ARCHIMATE WHWW - EXAMPLE 2 WHAT HOW Simplified WHAT WITH WHAT WITH WHAT
  18. 18. ARCHIMATE STACKING WHWW Logical world Physical world
  19. 19. CROSSING THE BOUNDARIES Cross-layer dependencies
  20. 20. ARCHIMATE CROSS-LAYER DEPENDENCIES ▸The business layer is SERVED by the application layer ▸The application layer is SERVED by the technology layer ▸A business object is REALIZED by an application object ▸An application object is REALIZED by a technology object (artifact) TYPICALLY, only SERVING or REALIZATION relationships cross layer boundaries
  21. 21. ARCHIMATE CROSS-LAYER DEPENDENCIES Serving relationship Realization relationshipRealization relationship Serving relationship Realization relationshipRealization relationship
  22. 22. ARCHIMATE CROSS-LAYER DEPENDENCIES Serving relationship Realization relationship Serving relationship Realization relationshipServing relationship
  23. 23. APPLICATION LAYER
  24. 24. ARCHIMATE EXAMPLE Internals (HOW) Externals (WHAT) Structure (HOW)
  25. 25. TECHNOLOGY LAYER
  26. 26. ARCHIMATE EXAMPLE Technology artifact Technology function System software Node (performs technology behaviour and execute, store, and process technology objects) (used to model the software environment in which Artifacts run) (represents a piece of data that is used or produced in a software development process, or by deployment and operation of an IT system.) (describes the internal behaviour of a Node)
  27. 27. ARCHIMATE PHYSICAL SERVER & CONNECTIVITY Device (a physical IT resource upon which system software and Artifacts may be stored or deployed for execution) Path (represents a link between two or more Nodes, through which these nodes can exchange data or material) Communication network (connects two or more Devices)
  28. 28. ARCHIMATE VIRTUALIZATION Device (a physical IT resource upon which system software and Artifacts may be stored or deployed for execution)
  29. 29. ARCHIMATE CLOUD SERVICES ON PREMISES IAAS PAAS SAAS
  30. 30. VIEWS & VIEWPOINTS
  31. 31. ARCHIMATE VIEW ▸In Archimate, architects can define their own views on the enterprise architecture ▸A view represents a part of the architecture ▸A stakeholder looks at the architecture from a certain viewpoint. ▸A viewpoint is a selection of a relevant subset of the Archimate concepts and their relationships, based on the combination of two dimensions: Purpose and Content
  32. 32. ARCHIMATE VIEWPOINTS
  33. 33. ARCHIMATE TECHNOLOGY VIEWPOINTS ▸Basic Archimate viewpoints: http://pubs.opengroup.org/architecture/archimate3- doc/apdxc.html ▸Technology viewpoints: ▸Technology viewpoint ▸Technology usage viewpoint
  34. 34. ARCHIMATE TECHNOLOGY USAGE VIEWPOINT
  35. 35. ARCHIMATE TECHNOLOGY VIEWPOINT
  36. 36. TOOL
  37. 37. ARCHIMATE ARCHI ▸https://www.archimatetool.com ▸Collaboration using BitBucket, git, ….

×