Search: onr:"swepub:oai:gup.ub.gu.se/197771" >
Identifying risky a...
Identifying risky areas of software code in Agile/Lean software development: An industrial experience report
-
- Antinyan, Vard, 1984 (author)
- Gothenburg University,Göteborgs universitet,Institutionen för data- och informationsteknik (GU),Department of Computer Science and Engineering (GU),University of Gothenburg
-
- Staron, Miroslaw, 1977 (author)
- Gothenburg University,Göteborgs universitet,Institutionen för data- och informationsteknik (GU),Department of Computer Science and Engineering (GU),University of Gothenburg
-
Meding, Wilhelm (author)
-
show more...
-
Österström, P. (author)
-
Wikström, E. (author)
-
Wranker, J. (author)
-
Henriksson, A. (author)
-
Hansson, Jörgen, 1970 (author)
-
show less...
-
(creator_code:org_t)
- ISBN 9781479941742
- IEEE, 2014
- 2014
- English.
-
In: 2014 Software Evolution Week - IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering, CSMR-WCRE 2014 - Proceedings. - : IEEE. - 9781479941742
- Related links:
-
http://dx.doi.org/10...
-
show more...
-
https://gup.ub.gu.se...
-
https://doi.org/10.1...
-
https://research.cha...
-
show less...
Abstract
Subject headings
Close
- Modern software development relies on incremental delivery to facilitate quick response to customers' requests. In this dynamic environment the continuous modifications of software code can cause risks for software developers; when developing a new feature increment, the added or modified code may contain fault-prone or difficult-to-maintain elements. The outcome of these risks can be defective software or decreased development velocity. This study presents a method to identify the risky areas and assess the risk when developing software code in Lean/Agile environment. We have conducted an action research project in two large companies, Ericsson AB and Volvo Group Truck Technology. During the study we have measured a set of code properties and investigated their influence on risk. The results show that the superposition of two metrics, complexity and revisions of a source code file, can effectively enable identification and assessment of the risk. We also illustrate how this kind of assessment can be successfully used by software developers to manage risks on a weekly basis as well as release-wise. A measurement system for systematic risk assessment has been introduced to two companies. © 2014 IEEE.
Subject headings
- NATURVETENSKAP -- Data- och informationsvetenskap (hsv//swe)
- NATURAL SCIENCES -- Computer and Information Sciences (hsv//eng)
Keyword
- agile
- correlation
- metric risk
- software
- software
Publication and Content Type
- ref (subject category)
- kon (subject category)
Find in a library
To the university's database
- By the author/editor
-
Antinyan, Vard, ...
-
Staron, Miroslaw ...
-
Meding, Wilhelm
-
Österström, P.
-
Wikström, E.
-
Wranker, J.
-
show more...
-
Henriksson, A.
-
Hansson, Jörgen, ...
-
show less...
- About the subject
-
- NATURAL SCIENCES
-
NATURAL SCIENCES
-
and Computer and Inf ...
- Articles in the publication
-
2014 Software Ev ...
- By the university
-
University of Gothenburg
-
Chalmers University of Technology