Strategy-Focused Architecture Decision Making

Chapter
Part of the Embedded Systems book series (EMSY)

Abstract

Making architecture investment decisions is challenging as it requires knowing and structurally combining best practices in management, economics, and architecting. This chapter describes a structured approach towards architecture decision making that integrates established management techniques, strategy maps and balanced scorecards, with established architecting practice, scenario and business case analysis. We have named this the Strategy-focused Architecture (StArch) approach. In this chapter, we exemplify each step of StArch using a real-life project at Philips Healthcare. StArch has been evaluated by the practitioners who indicated their satisfaction as well as suggested improvements to the existing decision making process in the organization.

Keywords

Architecture investment Decision making Strategy map Balanced scorecards 

Notes

Acknowledgements

We would like to thank the people at Philips Healthcare, especially the members of the team, as well as our colleagues Rob van Ommering, Aleksandra Tesanovic, Daniel Borches, Gürcan Güleşir, and Piërre van de Laar for their comments on earlier versions of this chapter.

References

  1. Bass L, Kazman R, Clements P (2003) Software architecture in practice. Addison Wesley, Reading, MAGoogle Scholar
  2. Böckle G, Clements P, McGregor JD et al. (2004) Calculating ROI for software product lines. IEEE Softw 21(3):23–31CrossRefGoogle Scholar
  3. Boehm BW (2006) Value-based software engineering: seven key elements and ethical considerations. In: Biffl S et al. (eds) Value-based software engineering. Springer, New YorkGoogle Scholar
  4. Boehm BW, Horowitz E, Madachy R et al. (2000) Software cost estimation with COCOMO II. Prentice Hall, Upper Saddle River, NJGoogle Scholar
  5. Clements P, McGregor JD, Cohen SG (2005) The Structured Intuitive Model for Product Line Economics (SIMPLE). Technical Report CMU/SEI-2005-TR-003, Carnegie Mellon UniversityGoogle Scholar
  6. Ivanovic A, America P (2008) Economics of architectural investments in industrial practice. In: 2nd international workshop on measurement and economics of software product lines (Volume 2 of SPLC proceedings), Limerick, IrelandGoogle Scholar
  7. Ivanovic A, America P (2010) Information needed for architecture decision making. In: 1st international workshop in product line approaches in software engineering (PLEASE2010), Cape Town, South AfricaGoogle Scholar
  8. Kaplan RS, Norton DP (1992) The balanced scorecard: measures that drive performance. Harv Bus Rev 70(1):71–79Google Scholar
  9. Kaplan RS, Norton DP (2004) Strategy maps: converting intangible assets into tangible outcomes. Harvard Business School, Boston, MAGoogle Scholar
  10. Kazman R, Asundi J, Klein M (2002) Making Architecture Design Decisions: An Economic Approach. Technical Report CMU/SEI-2002-TR-035, Carnegie Mellon UniversityGoogle Scholar
  11. Malan R, Bredemeyer D (2002) Chap. 1. Software architecture: central concerns, key decisions. Visual architecture action guide book. http://www.bredemeyer.com/pdf_files/ArchitectureDefinition.PDF. Accessed at 25 Sept 2010
  12. Moore M, Kazman R, Klein M, Asundi J (2003) Quantifying the value of architecture design decisions: lessons from the field. In: 25th IEEE international conference on software engineering, Portland, OregonGoogle Scholar
  13. Schmid K (2003) A quantitative model of the value of architecture in product line adoption. In: Fifth international workshop on product family engineering (PFE-5), Siena, Italy, SpringerGoogle Scholar
  14. Tennent J, Friend G (2005) Guide to business modeling. Bloomberg Press, New YorkGoogle Scholar
  15. van der Linden F, Schmid K, Rommes E (2007) Software product lines in action. Springer, HeidelbergGoogle Scholar

Copyright information

© Springer Science+Business Media B.V. 2010

Authors and Affiliations

  1. 1.Philips ResearchEindhovenThe Netherlands

Personalised recommendations