Modeling TOGAF with ArchiMate


Published on

The TOGAF® Architecture Development Method recommends that "an architecture description be encoded in a standard language". As the Open Group standard for enterprise modeling, Archimate is a strong candidate for this role. This presentation will explore how a diversified financial services company selected and is using Archimate for its TOGAF® implementation. The speaker will compare available enterprise modeling languages and explain why Archimate was selected, and will explain how his organization developed an enabling metamodel and diagram templates using a leading enterprise modeling tool. Methodology transition will also be covered, including how existing diagram types were mapped to TOGAF®, and how TOGAF® diagram content was mapped to Archimate.

Delivered at February 2011 Open Group San Diego Conference

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • InsuranceLife, Accidental Death and Dismemberment, Disability, Dental, Vision and AnnuitiesRetirement plansPublic and private-sectorDefined benefit (pension) and defined contribution
  • MethodologyCommentsZachman:Pioneering, comprehensive frameworkModel-Driven Architecture: Focused on portable application and service developmentSOA Reference Model: Focused on distributed software designIDEF:Family of 14 separate methods used primarily in defense and government work.IEEE 1471-2000:Defines fundamental EA conceptsExtended EA Framework: Framework based on ZachmanEnterprise Architecture Planning:Focuses on Zachman owner and planner views. Apparently defined primarily in Spewak book.TOGAF: Comprehensive, focused on EA, broadly sponsored and accepted, updated regularly.
  • The purpose of the Data Dissemination diagram is to show the relationship between data entity, business service, and application components. The diagram shows how the logical entities are to be physically realized by application components. This allows effective sizing to be carried out and the IT footprint to be refined. Moreover, by assigning business value to data, an indication of the business criticality of application components can be gained.Additionally, the diagram may show data replication and system ownership of the master reference for data. In this instance, it can show two copies and the master-copy relationship between them. This diagram can include services; that is, services encapsulate data and they reside in an application, or services that reside on an application and access data encapsulated within the application.
  • The purpose of the Application Communication diagram is to depict all models and mappings related to communication between applications in the metamodel entity.It shows application components and interfaces between components. Interfaces may be associated with data entities where appropriate. Applications may be associated with business services where appropriate. Communication should be logical and should only show intermediary technology where it is architecturally relevant.
  • The Platform Decomposition diagram depicts the technology platform that supports the operations of the Information Systems Architecture. The diagram covers all aspects of the infrastructure platform and provides an overview of the enterprise's technology platform. The diagram can be expanded to map the technology platform to appropriate application components within a specific functional or process area. This diagram may show details of specification, such as product versions, number of CPUs, etc. or simply could be an informal "eye-chart" providing an overview of the technical environment.
  • Modeling TOGAF with ArchiMate

    1. 1. January 25, 2011<br />Case Study: Modeling TOGAF™ with ArchiMate®<br />Iver Band<br />Open Group Conference, San Diego, California, USA<br />
    2. 2. Background<br />Choosing and Adopting a Methodology<br />Modeling with TOGAF and ArchiMate<br />Learnings and Suggestions<br />Agenda<br />January 25, 2011<br />2<br />
    3. 3. Founded in 1906 in Portland, Oregon and still based there<br />Went public in 1999 as Stancorp Financial Group (NYSE: SFG)<br />3,200 employees in 55 offices across the United States<br />Largest business is insurance for 26,000 groups with 6.5 million individuals<br />Provides 4,000 group retirement plans for 500,000 participants<br />Also offers commercial mortgages, individual disability and annuity, and personal financial advice<br />Insurance and retirement plans sold through a broad broker network<br />Visit<br />Recession <br />Layoffs, foreclosures, loss of investments and savings<br />Impact on disposable income<br />Increased risk of stress-induced health concerns<br />Depression <br />Anxiety <br />Compulsive behaviors (over-easting; excessive gambling and/or spending)<br />Substance abuse <br />About The Standard<br />January 25, 2011<br />3<br />
    4. 4. 4<br />IT at The Standard<br />January 25, 2011<br />
    5. 5. 5<br />Enterprise Architecture at The Standard<br />Small EA team with strong business relationships leads broader “Architecture Community”<br />Community-based “Architecture Assurance” process governs major projects<br />Reviews and approves Architecture Notebook rooted in OpenUP software development process <br />Evaluates enterprise implications of proposed architecture <br />Sample initiatives <br />CRM<br />Contact Center<br /> Master Data Management<br />Identity Management<br />Legacy Application Assessment <br />January 25, 2011<br />
    6. 6. 6<br />EA Challenges and Assets<br /><ul><li>Challenges
    7. 7. Complex legacy applications
    8. 8. Demanding business initiatives leave little capacity for tool and methodology development
    9. 9. Lots of complexity and change to manage relative to available resources
    10. 10. Assets
    11. 11. Architectural Descriptions
    12. 12. Business capability maps
    13. 13. Enterprise data model
    14. 14. Current and future state application architectures with asset lifecycle states
    15. 15. Core infrastructure strategy, architecture, roadmaps
    16. 16. Data center facilities and disaster recovery
    17. 17. Network
    18. 18. Server platforms
    19. 19. Casewise Corporate Modeler and Corporate Exchange
    20. 20. “Archipedia” SharePoint site collection</li></ul>January 25, 2011<br />
    21. 21. 1. Architecture guidance and methods were difficult to use<br /> 2. Diversity of methods hindered collaboration<br />7<br />Methodology Challenges<br />January 25, 2011<br />Slides<br />Papers<br />ERD<br />Landscapes<br />CapabilityMaps<br />ArchitectureNotebooks<br />UML 4+1<br />ExecutionArchitectures<br />Physical<br />Lifecycle Mgmt<br />Diagrams<br />Roadmaps<br />EA Planning<br />
    22. 22. Desire for<br />Multi-year business-driven technology strategy<br />Business service cost transparency<br />Increasing importance of SaaS, PaaS, offshore software engineering and on-site consultants<br />Internal proposals<br />“IT Information Management “<br />“Model-Based Architecture”<br />Enterprise-wide initiatives such as CRM and Contact Center<br />Realization that we were not getting the full benefit of our Casewise enterprise modeling toolset investment<br />Past difficulties with proprietary methodologies<br />8<br />Methodology Selection Triggers<br />January 25, 2011<br />
    23. 23. 9<br />Methodology Requirements<br />January 25, 2011<br />
    24. 24. 10<br />Methodology Comparison<br />January 25, 2011<br />
    25. 25. 11<br />“Model-Based Architecture” Implementation Approach<br />Most IT architecture at The Standard is project-driven, so the easiest approach was to pilot within those efforts<br />Encourage TOGAF/ArchiMate diagramming using Visio stencil<br />Enable TOGAF/ArchiMate diagramming in Casewise<br />Show benefits with major initiative deliverables<br />Build enterprise model in Casewise from existing assets (in progress)<br />Then, implement broader TOGAF concepts (just beginning)<br />ADM, repository, content model and reference models<br />January 25, 2011<br />
    26. 26. 12<br />Evolving The Standard’s “Architecture Notebook” towards TOGAF, ArchiMate and Casewise<br />
    27. 27. 13<br />Expressing Solution and Landscape Information with Annotated ArchiMate<br />January 25, 2011<br />Architecturally SignificantRequirement<br />Key<br />Architecture Decision<br />Dependency<br />Goal or Constraint<br />Feature<br />Option<br />
    28. 28. 14<br />Moving from Internal “Logical View” to…<br />January 25, 2011<br />
    29. 29. 15<br />ArchiMate Layered View of Major Solution<br />January 25, 2011<br />
    30. 30. Moving from Overloaded “Data View” to TOGAF Data Dissemination Diagram<br />
    31. 31. Moving from Overloaded “Data View” toTOGAF Application Communication Diagram<br />
    32. 32. 18<br />Moving from Overloaded “Physical View” to…<br />January 25, 2011<br />
    33. 33. 19<br />TOGAF Platform Decomposition Diagram of Major Solution<br />January 25, 2011<br />
    34. 34. Methodology and tools are the infrastructure of architecture<br />Maintaining them requires an ongoing investment<br />Every project can either strengthen or weaken them<br />IT professionals prefer standard methodologies and the tools that enable them<br />TOGAF and ArchiMate are based on a broad consensus<br />Experienced architects find them familiar and can adopt them quickly<br />Standard languages and methods are increasingly valuable as collaboration across organizations, cultures and geographies becomes ubiquitous<br />20<br />Lessons Learned<br />January 25, 2011<br />
    35. 35. Reconcile ArchiMate viewpoints and TOGAF Architecture Content Framework<br />Develop a set of quick start guidelines for organizations that want to use TOGAF for different purposes<br />Develop TOGAF-based annotation conventions for ArchiMate symbols<br />Add representation of motivations to ArchiMate<br />Add a compact service bus representation to ArchiMate<br />Develop explicit mappings between ArchiMate and UML<br />Allow placement of ArchiMate group name on inside of dashed rectangle for more efficient space usage<br />21<br />Suggestions for TOGAF and ArchiMate<br />January 25, 2011<br />