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

1. January 25, 2011 Case Study: Modeling TOGAF™ with ArchiMate® Iver Band Open Group Conference, San Diego, California, USA

2. Background Choosing and Adopting a Methodology Modeling with TOGAF and ArchiMate Learnings and Suggestions Agenda January 25, 2011 2

3. Founded in 1906 in Portland, Oregon and still based there Went public in 1999 as Stancorp Financial Group (NYSE: SFG) 3,200 employees in 55 offices across the United States Largest business is insurance for 26,000 groups with 6.5 million individuals Provides 4,000 group retirement plans for 500,000 participants Also offers commercial mortgages, individual disability and annuity, and personal financial advice Insurance and retirement plans sold through a broad broker network Visit www.standard.com Recession Layoffs, foreclosures, loss of investments and savings Impact on disposable income Increased risk of stress-induced health concerns Depression Anxiety Compulsive behaviors (over-easting; excessive gambling and/or spending) Substance abuse About The Standard January 25, 2011 3

4. 4 IT at The Standard January 25, 2011

5. 5 Enterprise Architecture at The Standard Small EA team with strong business relationships leads broader “Architecture Community” Community-based “Architecture Assurance” process governs major projects Reviews and approves Architecture Notebook rooted in OpenUP software development process Evaluates enterprise implications of proposed architecture Sample initiatives CRM Contact Center Master Data Management Identity Management Legacy Application Assessment January 25, 2011

7. Complex legacy applications

8. Demanding business initiatives leave little capacity for tool and methodology development

9. Lots of complexity and change to manage relative to available resources

10. Assets

11. Architectural Descriptions

12. Business capability maps

13. Enterprise data model

14. Current and future state application architectures with asset lifecycle states

15. Core infrastructure strategy, architecture, roadmaps

16. Data center facilities and disaster recovery

17. Network

18. Server platforms

19. Casewise Corporate Modeler and Corporate Exchange

20. “Archipedia” SharePoint site collectionJanuary 25, 2011

21. 1. Architecture guidance and methods were difficult to use 2. Diversity of methods hindered collaboration 7 Methodology Challenges January 25, 2011 Slides Papers ERD Landscapes CapabilityMaps ArchitectureNotebooks UML 4+1 ExecutionArchitectures Physical Lifecycle Mgmt Diagrams Roadmaps EA Planning

22. Desire for Multi-year business-driven technology strategy Business service cost transparency Increasing importance of SaaS, PaaS, offshore software engineering and on-site consultants Internal proposals “IT Information Management “ “Model-Based Architecture” Enterprise-wide initiatives such as CRM and Contact Center Realization that we were not getting the full benefit of our Casewise enterprise modeling toolset investment Past difficulties with proprietary methodologies 8 Methodology Selection Triggers January 25, 2011

23. 9 Methodology Requirements January 25, 2011

24. 10 Methodology Comparison January 25, 2011

25. 11 “Model-Based Architecture” Implementation Approach Most IT architecture at The Standard is project-driven, so the easiest approach was to pilot within those efforts Encourage TOGAF/ArchiMate diagramming using Visio stencil Enable TOGAF/ArchiMate diagramming in Casewise Show benefits with major initiative deliverables Build enterprise model in Casewise from existing assets (in progress) Then, implement broader TOGAF concepts (just beginning) ADM, repository, content model and reference models January 25, 2011

26. 12 Evolving The Standard’s “Architecture Notebook” towards TOGAF, ArchiMate and Casewise

27. 13 Expressing Solution and Landscape Information with Annotated ArchiMate January 25, 2011 Architecturally SignificantRequirement Key Architecture Decision Dependency Goal or Constraint Feature Option

28. 14 Moving from Internal “Logical View” to… January 25, 2011

29. 15 ArchiMate Layered View of Major Solution January 25, 2011

30. Moving from Overloaded “Data View” to TOGAF Data Dissemination Diagram

31. Moving from Overloaded “Data View” toTOGAF Application Communication Diagram

32. 18 Moving from Overloaded “Physical View” to… January 25, 2011

33. 19 TOGAF Platform Decomposition Diagram of Major Solution January 25, 2011

34. Methodology and tools are the infrastructure of architecture Maintaining them requires an ongoing investment Every project can either strengthen or weaken them IT professionals prefer standard methodologies and the tools that enable them TOGAF and ArchiMate are based on a broad consensus Experienced architects find them familiar and can adopt them quickly Standard languages and methods are increasingly valuable as collaboration across organizations, cultures and geographies becomes ubiquitous 20 Lessons Learned January 25, 2011

35. Reconcile ArchiMate viewpoints and TOGAF Architecture Content Framework Develop a set of quick start guidelines for organizations that want to use TOGAF for different purposes Develop TOGAF-based annotation conventions for ArchiMate symbols Add representation of motivations to ArchiMate Add a compact service bus representation to ArchiMate Develop explicit mappings between ArchiMate and UML Allow placement of ArchiMate group name on inside of dashed rectangle for more efficient space usage 21 Suggestions for TOGAF and ArchiMate January 25, 2011