The document discusses a case study on modeling TOGAF with ArchiMate, focusing on a company's adoption of methodologies to improve enterprise architecture. It outlines the challenges faced due to complex legacy systems and the necessity for collaboration among different methods, revealing efforts to pilot TOGAF and ArchiMate diagramming within current projects. Key lessons learned include the need for standardized guidelines and enhancements to ArchiMate to better support enterprise modeling initiatives.

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

2. BackgroundChoosing and Adopting a MethodologyModeling with TOGAF and ArchiMateLearnings and SuggestionsAgendaJanuary 25, 20112

3. Founded in 1906 in Portland, Oregon and still based thereWent public in 1999 as Stancorp Financial Group (NYSE: SFG)3,200 employees in 55 offices across the United StatesLargest business is insurance for 26,000 groups with 6.5 million individualsProvides 4,000 group retirement plans for 500,000 participantsAlso offers commercial mortgages, individual disability and annuity, and personal financial adviceInsurance and retirement plans sold through a broad broker networkVisit www.standard.comRecession Layoffs, foreclosures, loss of investments and savingsImpact on disposable incomeIncreased risk of stress-induced health concernsDepression Anxiety Compulsive behaviors (over-easting; excessive gambling and/or spending)Substance abuse About The StandardJanuary 25, 20113

4. 4IT at The StandardJanuary 25, 2011

5. 5Enterprise Architecture at The StandardSmall EA team with strong business relationships leads broader “Architecture Community”Community-based “Architecture Assurance” process governs major projectsReviews and approves Architecture Notebook rooted in OpenUP software development process Evaluates enterprise implications of proposed architecture Sample initiatives CRMContact Center Master Data ManagementIdentity ManagementLegacy Application Assessment January 25, 2011

6. 6EA Challenges and AssetsChallenges

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 collaboration7Methodology ChallengesJanuary 25, 2011SlidesPapersERDLandscapesCapabilityMapsArchitectureNotebooksUML 4+1ExecutionArchitecturesPhysicalLifecycle MgmtDiagramsRoadmapsEA Planning

22. Desire forMulti-year business-driven technology strategyBusiness service cost transparencyIncreasing importance of SaaS, PaaS, offshore software engineering and on-site consultantsInternal proposals“IT Information Management ““Model-Based Architecture”Enterprise-wide initiatives such as CRM and Contact CenterRealization that we were not getting the full benefit of our Casewise enterprise modeling toolset investmentPast difficulties with proprietary methodologies8Methodology Selection TriggersJanuary 25, 2011