Skip to main content

Identifying and Understanding Architectural Risks in Software Evolution: An Empirical Study

  • Conference paper
Product-Focused Software Process Improvement (PROFES 2008)

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 5089))

Abstract

Software risk management studies commonly focus on project level risks and strategies. Software architecture investigations are often concerned with the design, implementation and maintenance of the architecture. However, there has been little effort to study risk management in the context of software architecture. We have identified risks and corresponding management strategies specific to software architecture evolution as they occur in industry, from interviews with 16 Norwegian IT-professionals. The most influential (and frequent) risk was “Lack of stakeholder communication affected implementation of new and changed architectural requirements negatively”. The second most frequent risk was “Poor clustering of functionality affected performance negatively”. Architects focus mainly on architecture creation. However, their awareness of needed improvements in architecture evaluation and documentation is increasing. Most have no formally defined/documented architecture evaluation method, nor mention it as a mitigation strategy. Instead, problems are fixed as they occur, e.g. to obtain the missing artefacts.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2nd edn. Addison-Wesley, Reading (2004)

    Google Scholar 

  2. Bass, L., Buhman, C., Comella-Dorda, S., Long, F., Robert, J., Seacord, R., Wallnau, K.: Volume I: Market Assessment of Component-based Software Engineering in SEI Technical Report number CMU/SEI-2001-TN-007 (2001)

    Google Scholar 

  3. Belady, L.A., Lehman, M.M.: A model of a Large Program Development. IBM Systems Journal 15(1), 225–252 (1976)

    Article  MATH  Google Scholar 

  4. Bennett, K.H., Rajlich, V.: Software Maintenance and Evolution: A Roadmap. In: ICSE 2000 – Future of Software Engineering, Limerick, Ireland, pp. 73–87 (2000)

    Google Scholar 

  5. Sommerville, I.: Software Engineering, 6th edn., p. 728. Addison-Wesley, Reading (2001)

    Google Scholar 

  6. Ropponen, J., Lyytinen, K.: Components of Software Development Risk: How to Address Them? A Project Manager Survey. IEEE Transactions on Software Engineering 26(2), 98–112 (2000)

    Article  Google Scholar 

  7. Ali Babar, M., Bass, L., Gorton, I.: Factors Influencing Industrial Practices of Software Architecture Evaluation: An Empirical Investigation. In: QoSA 2007, Medford, Massachusetts, USA, July 12-13 (2007)

    Google Scholar 

  8. Boehm, B.W.: Software Risk management: Principles and Practices. IEEE Software 8(1), 32–41 (1991)

    Article  Google Scholar 

  9. Carr, M., Kondra, S., Monarch, I., Ulrich, F., Walker, C.: Taxonomy-Based Risk Identification, Technical Report SEI-93-TR-006, SEI, Pittsburgh, USA (1993)

    Google Scholar 

  10. Keil, M., Kule, P.E., Lyytinen, K., Schmidt, R.C.: A Framework for Identifying Softare Project Risks. Communications of the ACM 4(11), 76–83 (1998)

    Article  Google Scholar 

  11. Boehm, B.W.: A Spiral Model of Software Development and Enhancement. IEEE Computer 21(5), 61–72 (1988)

    Google Scholar 

  12. Gemmer, A.: Risk Management: Moving Beyond Process. IEEE Computer 30(5), 33–41 (1997)

    Google Scholar 

  13. Hecht, H.: Systems Reliability and Failure Prevention. Artech House Publishers (2004)

    Google Scholar 

  14. Clerc, V., Lago, P., van Vliet, H.: The Architect’s Mindset. In: QoSA 2007, Medford, Massachusetts, USA, July 12-13 (2007)

    Google Scholar 

  15. Wohlin, C., Runeson, P., Höst, M., Ohlsson, M.C., Regnell, B., Wesslén, A.: Experimentation in Software Engineering – An Introduction. Kluwer Academic Publishers, Dordrecht (2002)

    Google Scholar 

  16. Seaman, C.B.: Qualitative Methods in Empirical Studies of Software Engineering. IEEE Transactions on Software Engineering 25(4), 557–572 (1999)

    Article  Google Scholar 

  17. Lethbridge, T.C., Sim, S.E., Singer, J.: Studying Software Engineers: Data Collection Techniques for Software Field Studies. Empirical Software Engineering 10(3), 311–341 (2005)

    Article  Google Scholar 

  18. Kitchenham, B., Pfleeger, S.L.: Principles of Survey Research, Parts 1 to 6. ACM Software Engineering Notes (2001 – 2002)

    Google Scholar 

  19. Messerschmitt, D.G., Szyperski, C.: Marketplace Issues in Software Planning and Design. IEEE Software 21(3), 62–70 (2004)

    Article  Google Scholar 

  20. Johnson, R.E., Foote, B.: Designing Reusable Classes. Journal of Object-Oriented Programming 1(2), 22–35 (1988)

    Google Scholar 

  21. Bass, L., Nord, R., Wood, W., Zubrow, D.: Risk Themes Discovered Through Architecture Evaluations. In: Proc. WICSA 2007 (2007)

    Google Scholar 

  22. O’Connell, D.: Boeing’s Experiences using the SEI ATAM® and QAW Processes (April 2006), http://www.sei.cmu.edu/architecture/saturn/2006/OConnell.pdf

  23. Charette, R.N.: Why software fails. Spectrum 42(9), 42–49 (2005)

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Andreas Jedlitschka Outi Salo

Rights and permissions

Reprints and permissions

Copyright information

© 2008 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Slyngstad, O.P.N., Li, J., Conradi, R., Babar, M.A. (2008). Identifying and Understanding Architectural Risks in Software Evolution: An Empirical Study. In: Jedlitschka, A., Salo, O. (eds) Product-Focused Software Process Improvement. PROFES 2008. Lecture Notes in Computer Science, vol 5089. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-69566-0_32

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-69566-0_32

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-69564-6

  • Online ISBN: 978-3-540-69566-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics