Please use this identifier to cite or link to this item:
https://hdl.handle.net/2440/88473
Citations | ||
Scopus | Web of Science® | Altmetric |
---|---|---|
?
|
?
|
Type: | Conference paper |
Title: | Identifying and understanding architectural risks in software evolution: an empirical study |
Author: | Slyngstad, O. Li, J. Conradi, R. Babar, M. |
Citation: | Lecture Notes in Artificial Intelligence, 2008 / Jedlitschka, A., Salo, O. (ed./s), vol.5089 LNCS, pp.400-414 |
Publisher: | Springer |
Publisher Place: | Online |
Issue Date: | 2008 |
Series/Report no.: | Lecture Notes in Computer Science; v. 5089 |
ISBN: | 3540695648 9783540695646 |
ISSN: | 0302-9743 1611-3349 |
Conference Name: | 9th International Conference on Product-Focused Software Process Improvement (PROFES 2008) (23 Jun 2008 - 25 Jun 2008 : Monte Porzio Catone, Italy) |
Editor: | Jedlitschka, A. Salo, O. |
Statement of Responsibility: | Odd Petter Nord Slyngstad, Jingyue Li, Reidar Conradi, and M. Ali Babar |
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. |
Keywords: | software architecture software evolution risk management software architecture evaluation |
Rights: | © Springer-Verlag Berlin Heidelberg 2008 |
DOI: | 10.1007/978-3-540-69566-0_32 |
Published version: | http://dx.doi.org/10.1007/978-3-540-69566-0_32 |
Appears in Collections: | Aurora harvest 7 Computer Science publications |
Files in This Item:
There are no files associated with this item.
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.