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

  • Authors:

  • Odd Petter Slyngstad;Jingyue Li;Reidar Conradi;M. Ali Babar

  • Affiliations:

  • Department of Computer and Information Science (IDI), Norwegian University of Science and Technology (NTNU), Trondheim, Norway;Department of Computer and Information Science (IDI), Norwegian University of Science and Technology (NTNU), Trondheim, Norway;Department of Computer and Information Science (IDI), Norwegian University of Science and Technology (NTNU), Trondheim, Norway;LERO--- The Irish Software Engineering Centre, University of Limerick, Limerick, Ireland

  • Venue:
  • PROFES '08 Proceedings of the 9th international conference on Product-Focused Software Process Improvement
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

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.