• Like
Modeling the Backstory with the ArchiMate Motivation Extension
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Modeling the Backstory with the ArchiMate Motivation Extension

  • 2,594 views
Published

 

Published in Economy & Finance , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,594
On SlideShare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
136
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. July 17, 2012Modeling the Backstory with theArchiMate® Motivation ExtensionIver Band © 2010 Standard Insurance CompanyThe 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 Company2 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 Employees3 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. 294 July 18, 2012 © 2010 Standard Insurance Company
  • 5. The ArchiMate Language5 July 18, 2012 © 2010 Standard Insurance Company
  • 6. The ArchiMate Core and Extensions Support the TOGAF ADM6 July 18, 2012 © 2010 Standard Insurance Company
  • 7. Modeling TOGAF ACF Principles, Vision, Requirements and Roadmap Concepts7 July 18, 2012 © 2010 Standard Insurance Company
  • 8. Modeling TOGAF Business Architecture Concepts8 July 18, 2012 © 2010 Standard Insurance Company
  • 9. Motivational Element Relationships with ArchiMate Core and Structural Elements9 July 18, 2012 © 2010 Standard Insurance Company
  • 10. Motivation Extension Metamodel10 © 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 Relationships13 © 2010 Standard Insurance Company July 18, 2012
  • 14. Motivation Extension Summary14 © 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 practices15 © 2010 Standard Insurance Company July 18, 2012
  • 16. Extending the Motivation Metamodel16 © 2010 Standard Insurance Company July 18, 2012
  • 17. Stakeholder View17 © 2010 Standard Insurance Company July 18, 2012
  • 18. Goal Realization View18 © 2010 Standard Insurance Company July 18, 2012
  • 19. Goal Contribution View19 © 2010 Standard Insurance Company July 18, 2012
  • 20. Principles View20 © 2010 Standard Insurance Company July 18, 2012
  • 21. Requirements Realization View21 © 2010 Standard Insurance Company July 18, 2012
  • 22. Motivation View22 © 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 requirements23 © 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.com24 © 2010 Standard Insurance Company July 18, 2012
  • 25. © 2010 Standard Insurance Company