Modeling the Backstory with the ArchiMate Motivation Extension
6 likes5,948 views
The document discusses using the ArchiMate Motivation extension to model the underlying reasons and motivations for enterprise architecture design and changes. It provides an overview of key concepts in the ArchiMate language and motivation extension and presents a case study of how an insurance company used it to improve customer service through a CRM implementation. The motivation extension allows architects to link requirements to other model elements and develop views to help stakeholders refine requirements.
Modeling the Backstory with the ArchiMate Motivation Extension
- 1. July 17, 2012 Modeling the Backstory with the ArchiMate® Motivation Extension Iver Band © 2010 Standard Insurance Company The Open Group Conference, Washington, D.C.
- 2. Agenda • Background • Introduction to the ArchiMate Motivation Extension • Case Study: Improving Customer Service with Enterprise CRM • Conclusion Thanks to Joahna Kuiper, Business Architect at Standard Insurance Company 2 July 18, 2012 © 2010 Standard Insurance Company
- 3. The Standard • Financial services company • Founded in 1906 • Our purpose: We help people achieve financial well-being and peace of mind. • Expertise: • Group Life & Disability Insurance • Individual Disability Insurance • Retirement Plans • Individual Annuities • Commercial Mortgages • Investment advice • Headquarters in Portland, Ore. • 3,100 Employees 3 July 18, 2012 © 2010 Standard Insurance Company
- 4. Fundamental Ideas • Backstory: a story that tells what led up to the main story... • Merriam-Webster® online dictionary • Motivational concepts are used to model the motivations, or reasons, that underlie the design or change of some enterprise architecture. • ArchiMate® 2.0 Specification, p 118 • A requirement is defined as a statement of need that must be realized by a system. • ArchiMate® 2.0 Specification, p 122 • The cost of fixing software defects increases 10-100 times from the requirements analysis phase to post-release • McConnell, Steve (2004). Code Complete (2nd ed.). Microsoft Press. p. 29 4 July 18, 2012 © 2010 Standard Insurance Company
- 5. The ArchiMate Language 5 July 18, 2012 © 2010 Standard Insurance Company
- 6. The ArchiMate Core and Extensions Support the TOGAF ADM 6 July 18, 2012 © 2010 Standard Insurance Company
- 7. Modeling TOGAF ACF Principles, Vision, Requirements and Roadmap Concepts 7 July 18, 2012 © 2010 Standard Insurance Company
- 8. Modeling TOGAF Business Architecture Concepts 8 July 18, 2012 © 2010 Standard Insurance Company
- 9. Motivational Element Relationships with ArchiMate Core and Structural Elements 9 July 18, 2012 © 2010 Standard Insurance Company
- 10. Motivation Extension Metamodel 10 © 2010 Standard Insurance Company July 18, 2012
- 11. Motivational Concepts (1 of 2) 11 © 2010 Standard Insurance Company July 18, 2012
- 12. Motivational Concepts (2 of 2) 12 © 2010 Standard Insurance Company July 18, 2012
- 13. Motivational Relationships 13 © 2010 Standard Insurance Company July 18, 2012
- 14. Motivation Extension Summary 14 © 2010 Standard Insurance Company July 18, 2012
- 15. Case Study: Improving Customer Service with Enterprise CRM • Aspects of fast-paced initial phase of major SaaS implementation with complex on-premises integration requirements • Used internal content framework based on the Eclipse Process Framework OpenUP process. Some key concepts include • Architecturally Significant Requirements – Typically central to system purpose – Technically challenging or constraining • Architectural Goals – Provide motivation and rationale for decisions – Typically address solution lifespan and need to adapt to change • Exceptions – Temporary departures from standards or accepted practices 15 © 2010 Standard Insurance Company July 18, 2012
- 16. Extending the Motivation Metamodel 16 © 2010 Standard Insurance Company July 18, 2012
- 17. Stakeholder View 17 © 2010 Standard Insurance Company July 18, 2012
- 18. Goal Realization View 18 © 2010 Standard Insurance Company July 18, 2012
- 19. Goal Contribution View 19 © 2010 Standard Insurance Company July 18, 2012
- 20. Principles View 20 © 2010 Standard Insurance Company July 18, 2012
- 21. Requirements Realization View 21 © 2010 Standard Insurance Company July 18, 2012
- 22. Motivation View 22 © 2010 Standard Insurance Company July 18, 2012
- 23. Conclusion • Architects and analysts gathering requirements can increase their effectiveness by using the ArchiMate Motivation extension to: • Model requirements in relationship with other motivational, structural and behavioral elements • Develop graphical views that express these models • Use these views to interact with stakeholders for the purpose of extending and refining these requirements 23 © 2010 Standard Insurance Company July 18, 2012
- 24. References • ArchiMate 2.0 • http://theopengroup.org/archimate/downloads.htm • TOGAF 9.1 • http://pubs.opengroup.org/architecture/togaf9-doc/arch/ • White Paper: Using the TOGAF® 9.1 Architecture Content Framework with the ArchiMate® 2.0 Modeling Language • https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.js p?publicationid=12697 • Code Complete, Second Edition • http://www.cc2e.com/Default.aspx • Eclipse Process Framework • http://www.eclipse.org/epf/ • Presenter: iver.band@standard.com 24 © 2010 Standard Insurance Company July 18, 2012
- 25. © 2010 Standard Insurance Company