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 attention to maximise their effectiveness. This led us to wonder whether successful experienced architects have any common techniques or heuristics that they use to help them achieve this. In an earlier study where, having interviewed experienced architects, we found that in fact there were some common heuristics that they use, we created a simple model based on an analysis of their advice. In this paper we explain how we validated that model with a wider survey of experienced enterprise and software architects and, from the findings of that study, extended the model with an additional dimension. This resulted in our model having four primary guidelines, which are: focus on stakeholder needs and priorities, prioritise time according to risks, delegate as much as possible, and ensure team effectiveness.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Achimugu, P., Selamat, A., Ibrahim, R., Mahrin, M.: A systematic literature review of software requirements prioritization research. Inf. Softw. Technol. 56(6), 568–585 (2014)
Allen, D.: Getting Things Done: The Art of Stress-free Productivity, 2nd edn. Piatkus, Piatkus (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). https://doi.org/10.1007/3-540-28244-0_4
Harindran A., Chandra V.: Research Methodology. Pearson, London (2017).
Herrmann, A., Daneva, M.: Requirements prioritization based on benefit and cost prediction: an agenda for future research. In: Tetsuo, T. (ed.) 2008 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 Boston (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
Woods, E., Bashroush, R.: A model for prioritization of software architecture effort. In: Lopes, A., de Lemos, R. (eds.) ECSA 2017. LNCS, vol. 10475, pp. 183–190. Springer, Cham (2017). https://doi.org/10.1007/978-3-319-65831-5_13
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2021 Springer Nature Switzerland AG
About this paper
Cite this paper
Woods, E., Bashroush, R. (2021). How Software Architects Focus Their Attention. In: Biffl, S., Navarro, E., Löwe, W., Sirjani, M., Mirandola, R., Weyns, D. (eds) Software Architecture. ECSA 2021. Lecture Notes in Computer Science(), vol 12857. Springer, Cham. https://doi.org/10.1007/978-3-030-86044-8_21
Download citation
DOI: https://doi.org/10.1007/978-3-030-86044-8_21
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-86043-1
Online ISBN: 978-3-030-86044-8
eBook Packages: Computer ScienceComputer Science (R0)