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.

Design your Business, Model your Architecture (presentation by Marc Lankhorst of BiZZdesign at I.T. Works/LoQutus meetup)

2.116 visualizaciones

Publicado el

Presentation by Marc Lankhorst of BiZZdesign at I.T. Works/LoQutus meetup on July 1st, 2014 @Vlerick School. See for full details on this meetup.

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

Design your Business, Model your Architecture (presentation by Marc Lankhorst of BiZZdesign at I.T. Works/LoQutus meetup)

  1. 1. Design Your Business, Model Your Architecture M L khMarc Lankhorst Ghent, 1 July 2014
  2. 2. Marc Lankhorst +31 6 44 092 359 htt // bi d i • Service line manager Enterprise Architecture • Service line manager Enterprise Architecture • Responsible for BiZZdesign’s EA proposition • Enterprise architect trainer coach project manager• Enterprise architect, trainer, coach, project manager • Manager of the original ArchiMate development project • TOGAF and ArchiMate certifiedTOGAF and ArchiMate certified 2
  3. 3. BiZZdesign: Integrated Service Offeringg g g Enterprise  Architecture  Business  Modeling Lean &  Business Process  Management Management  Consulting servicesConsulting services ToolingTooling TrainingTraining Best practicesBest practices 3
  4. 4. BiZZdesign Worldwide: Offices and Partnersg BiZZdesign offices Official BiZZdesign resellersOfficial BiZZdesign resellers
  5. 5. Let’s Get to Know Each Other! Raise your hand: • Who has not heard of ArchiMate before this event? • Who is using ArchiMate?Who is using ArchiMate? • Who is ArchiMate certified? • Who has ever attended a TOGAF training course?g • Who is TOGAF9 certified? • Who is a business or IT architect? • Who just discovered he or she is in the wrong room?…. 5
  7. 7. Enterprise Architecture:  B t St t d I l t tiBetween Strategy and Implementation Successful organizations link their business strategy to  their operations and create agility by effective and  coherent usage of:coherent usage of:  • explicit business strategy modelling • business model innovation• business model innovation • enterprise architecture • business process & business rule managementbusiness process & business rule management • data and system designs Enterprise architecture is the linking pin between strategy  and implementation
  8. 8. Enterprise Architecture: Realizing Strategyp g gy Mission Strategy Vision Goalsas is to be Actionsenterprise architecture solution hit t culture people leadership architectures people Operations peopleprocesses ITproducts …
  9. 9. The Problem… 9
  10. 10. Architecture Models • Use models to describe enterprise architectures d l b h k d l d l d d• Models can be checked, visualized, analyzed, managed,  integrated, transformed, interpreted, and sometimes  even executedeven executed • Needed: well founded practical and vendor• Needed: well‐founded, practical, and vendor‐ independent standard for enterprise architecture  modelingg 10
  11. 11. ArchiMate • A language to describe architectures • A graphical notation with formal semanticsg p • A framework that describes the business, application and technology layersapplication, and technology layers – With Relations between the layers E t i f ti ti i l t ti & i ti• Extensions for motivation, implementation & migration • Techniques for visualizations and analyses for different  stakeholders • An open standard maintained by The Open Group 11
  12. 12. Positioning ArchiMateg Business Model Canvas Strategic Management How do we position ourselves w.r.t. our environment? Business Model Canvas Five Forces model Value Chain model SWOT AnalysisSWOT Analysis Enterprise Architecture How do we organize ourselves? ArchiMate models BPMN models Design & Implementation How do we perform our business & IT efficiently? BPMN models TDM models UML models ERD d lERD models
  13. 13. History of ArchiMatey 2012 20132002 ‐ 2004 2009 13
  14. 14. Requirements on the ArchiMate Languageq g g ArchiMate lHigh level languageHigh‐level  modeling within a Basis forwithin a  domain Basis for visualizations Modeling relations  between domains Basis for analysesRelate to standardsstandards 14
  15. 15. Notation • Most concepts have two notations: – IconIcon – Box with icon • Sharp corners = structure • Rounded corners = behavior • Cut‐off corners = motivation • Notation resembles UML and BPMN – to stay close to what architects already know • Relations (arrows etc.) are also mostly taken from existing  languages, with a few exceptions 15
  16. 16. ArchiMate Core Framework Passive Structure Behavior Active Structure Layers Business Layer Application Layer Technology Layer 16 Aspects
  17. 17. Aspectsp Behavior Element Active Structure Element Passive Structure  Element (the verb) (subject doing the action) Element (object being acted on) 17
  18. 18. Generic Structure at Each Layery External InternalInternal Passive Behavior ActivePassive structure Behavior Active structure Si il h l k h lSimilar concepts at each layer make the language  easier to learn and more consistent in use 18
  19. 19. Services as Binding Conceptg p External Customer External business service Internal business service Business business service Application External application service pp Internal application service Internal infra service External infra. service Technology infra. service 19
  20. 20. Notation • Most concepts have two notations: – IconIcon – Box with icon • Sharp corners = structure • Rounded corners = behavior • Cut‐off corners = motivation • Notation resembles UML and BPMN – to stay close to what architects already know • Relations (arrows etc.) are also mostly taken from existing  languages, with a few exceptions 20
  21. 21. ArchiMate Core Summaryy usinessBonApplicatioAologyTechno hPassive Structure Behavior Active structure 21
  22. 22. Layered View Exampley p Business A li tiApplication Technologygy 22
  23. 23. Motivation Extension 23
  24. 24. Implementation & Migration Extensionp g 24
  25. 25. Passive structure Behavior Active structure Motivation usinessBnApplicationAgyTechnolog entation ration Impleme &Migr
  26. 26. ArchiMate and TOGAF: Complementary Standardsp y • TOGAF: The Open Group Architecture Framework A hit t D l t M th d (ADM) id f– Architecture Development Method (ADM) provides a way of  working  – Methodical support, but no description techniquepp p q • ArchiMate: – A description language – But no prescribed way of working • Ideal opportunity for combining forces! 26
  27. 27. TOGAF, ArchiMate Core and Extensions M , Motivatio Preliminary TOGAF ADM n Business A Architecture Vision B Business H Architecture Change ArchiMate Core Business Business R i t Architecture C Information g Management G Architecture ApplicationData Application Requirements Management Information Systems Architectures G Implementation Governance Application Architecture Data Architecture Technology D Technology Architecture F Migration Planning E Opportunities and  l Technology Architecture Solutions 27
  29. 29. Modeling at the Strategic Levelg g • Stakeholders at the CxO level are not used to formal models • But they do use techniques like: – Balanced Scorecard – Business Model Canvas – SWOT analysesSWOT analyses – Five Forces model – Operating models – Value chain models • These provide a starting point for your architecture effort – Give the motivation for architectural decisions – And architecture provides feedback about feasibility of strategy:  scenarios roadmaps etcscenarios, roadmaps, etc. 29
  30. 30. Business Model Canvas as Front‐End for EA VALUE CUSTOMER MARKETKEY KEY VALUE PROPOSITION CUSTOMER RELATIONSHIPS MARKET SEGMENTS KEY PARTNERS KEY ACTIVITIES Process views Delivery Concepts KEY Product/market/channel Context views Concepts Process improvement CHANNELS KEY RESOURCES views Organisation viewsCollaboration i Channel views Application views views Channel Mix‐views REVENUE STREAMSCOST STRUCTURE Cost heat maps Revenue Heat maps © Based on Business model generation, 2009, Alexander Osterwalder, Yves Pigneur.  Graphic via
  31. 31. Business Model Canvas as Starting Pointg • ‘Translate’ your business model into a starting point for  architecture modeling  Ki k t t th i l t ti b i li ti• Kick‐start the implementation: business, application,  technology
  33. 33. ArchiMate, UML & BPMN, • ArchiMate connects architectural domains B t d t f i l t ti d t il– But does not focus on implementation details – Broader scope, but less detail than e.g. UML (software), BPMN  (processes)(p ) – No replacement for these, but an ‘umbrella’ on top • Several ArchiMate concepts derived from BPMN and  UML – Easy to link to e.g. UML descriptions of detailed design or  BPMN process modelsBPMN process models • Example: UMLExample: UML 33
  34. 34. Scope of ArchiMate and UML Passive Active p Passive  Structure Behavior Active Structure Motivation E t iEnterprise Architecture ArchiMate Solution Architecture Solution UML Design 34
  35. 35. ArchiMate Concepts Inspired by UMLp p y ArchiMate UML 35
  36. 36. Integrationg 36
  38. 38. Architecture Modeling Should be Integrated… g g • With the architecture process TOGAF ADM th– TOGAF ADM or any other • With architecture and  implementation governanceimplementation governance – Validate the models  • With other modeling effortsWith other modeling efforts – Strategy, business models – Process and rule models – Software models – … 38 When using models, work from the perspective of  stakeholders, products and deliverables!  
  39. 39. Big Architecture Drawings Make Nice Wallpapers…g g p p 39
  40. 40. … But I Would Rather Use a Tool… 40
  41. 41. … That Provides Different Views on a Model P2 A2 S2 A2 F1 Repositoryp y 41
  42. 42. Consistent and Integrated Modeling…g g • is a kind of knowledge management h l d• helps to integrate various domains • links vision to realization • enables stakeholder‐specific view generation • supports analyses, e.g. traceability 42 Position ArchiMate as an umbrella language for integrated  high‐level modeling and analyses over various domains
  43. 43. ArchiMate is Useful To... • Bridge the gap between ‘free‐format’ strategy models  and detailed solution architecture modelsand detailed solution architecture models • Enhance communication  M k d l l bl• Make models analyzable • Have a common basis for  more detailed modelingmore detailed modeling 43 Relate your ArchiMate models to your operating model or  business model when communicating to C‐level
  44. 44. ArchiMate is a Start ‐ Not an Endpointp • Open standard is a “safe choice” h k b ll• Think big, start small – There are many possible  concepts and relationsconcepts and relations – Select and learn • Implementing ArchiMate means p g a change in how architects work  – Takes time – Communication – Management support 44 Consider the implementation of ArchiMate as a project…  Include change management aspects
  45. 45. ArchiMate’s Active User Communityy • ArchiMate Forum of The Open Group htt // hi t– • ArchiMate LinkedIn group http://www linkedin com/groups/ArchiMate 50758–‐50758 – > 4700 members, exponential growth  – Many lively discussions on y y practical applications of the  language, suggestions for  improvement, etc.improvement, etc. 45 Interested? Join the community!
  46. 46. Questions?Q Marc M. Lankhorst Service line manager Enterprise ArchitectureService line manager Enterprise Architecture +31 644 092 35931 644 092 359 Webinars, blogs, e‐books, customer stories, trainingWebinars, blogs, e books, customer stories, training  portfolio, software and more on 46
  47. 47. ©BiZZdesign. All rights reserved. BiZZdesign and BiZZdesign logos are registered trademarks of BiZZdesign Company.