Abstract
As part of our software architecture research and practice we have found that a common difficulty for new architects is knowing where to focus their effort to maximise their effectiveness. This led us to wonder whether successful experienced architects have reusable heuristics or guidelines that they follow to help them prioritise their work. To investigate this we have performed a study using semi-structured interviews to explore how experienced software architects prioritise their activities in order to maximise their effectiveness. From the primary data collected through the interviews we have synthesised a simple model that organises and explains the heuristics that we found to be common across a number of experienced software architects.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Allen, D.: Getting Things Done: The Art of Stress-free Productivity, 2nd edn. Piatkus, London (2015)
Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 3rd edn. Addison Wesley, Upper Saddle River (2012)
Berander, P., Andrews, A.: Requirements prioritization. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 69–94. Springer, Heidelberg (2005)
Charmaz, K.: Constructing Grounded Theory: A Practical Guide through Qualitative Analysis. Sage, London (2006)
De Marco, T.: Slack: Getting Past Burn-out, Busywork, and the Myth of Total Efficiency. Dorset House, New York (2001)
Fairbanks, G.: Just Enough Software Architecture, A Risk Driven Approach. Marshall & Brainerd, Boulder (2010)
Herrmann, A., Daneva, M.: Requirements prioritization based on benefit and cost prediction: an agenda for future research. In: Tetsuo, T. (ed.) 16th IEEE International Requirements Engineering, RE 2008. IEEE (2008)
Karlsson, J., Ryan, K.: A cost-value approach for prioritizing requirements. IEEE Softw. 14(5), 67–74 (1997)
Koch, K.: The 80/20 Principle: The Secret of Achieving More with Less. Nicholas Brearley Publishing, London (2007)
Kruchten, P.: What do software architects really do? J. Syst. Softw. 81(12), 2413–2416 (2008)
Matt, G.E., Cook, T.D.: Threats to the validity of research synthesis. In: Cooper, H., Hedges, L.V. (eds.) The Handbook of Research Synthesis, pp. 503–520. Russell Sage Foundation, New York (1994)
Poort, E.R., van Vliet, H.: RCDA: architecting as a risk-and cost management discipline. J. Syst. Softw. 85(9), 1995–2013 (2012)
Reimer, F.J., Quartaroli, M.T., Lapan, S.D.: Qualitative Research: An Introduction to Methods and Designs. Wiley, London (2012)
Rozanski, N., Woods, E.: Software systems architecture, working with stakeholders using viewpoints and perspectives, 2nd edn. Addison Wesley, Upper Saddle River (2011)
Wikipedia, Situational Awareness. https://en.wikipedia.org/wiki/Situation_awareness. Accessed 10 Apr 2017
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2017 Springer International Publishing AG
About this paper
Cite this paper
Woods, E., Bashroush, R. (2017). A Model for Prioritization of Software Architecture Effort. In: Lopes, A., de Lemos, R. (eds) Software Architecture. ECSA 2017. Lecture Notes in Computer Science(), vol 10475. Springer, Cham. https://doi.org/10.1007/978-3-319-65831-5_13
Download citation
DOI: https://doi.org/10.1007/978-3-319-65831-5_13
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-65830-8
Online ISBN: 978-3-319-65831-5
eBook Packages: Computer ScienceComputer Science (R0)