loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
30th Annual IEEE/NASA Software Engineering Workshop SEW-30 (SEW'06)
Understanding Change Requests to Predict Software Impact
Columbia, Maryland
April 24-April 28
ISBN: 0-7695-2624-1
ASCII Text
x 
 
Christopher Ackermann, Mikael Lindvall, "Understanding Change Requests to Predict Software Impact," Software Engineering Workshop, Annual IEEE/NASA Goddard, pp. 66-75, 30th Annual IEEE/NASA Software Engineering Workshop SEW-30 (SEW'06), 2006.
 
 
BibTex
x
 
@article{ 10.1109/SEW.2006.36,
author = {Christopher Ackermann and Mikael Lindvall},
title = {Understanding Change Requests to Predict Software Impact},
journal ={Software Engineering Workshop, Annual IEEE/NASA Goddard},
volume = {0},
year = {2006},
issn = {1550-6215},
pages = {66-75},
doi = {http://doi.ieeecomputersociety.org/10.1109/SEW.2006.36},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Software Engineering Workshop, Annual IEEE/NASA Goddard
TI - Understanding Change Requests to Predict Software Impact
SN - 1550-6215
SP66
EP75
A1 - Christopher Ackermann,
A1 - Mikael Lindvall,
PY - 2006
KW - null
VL - 0
JA - Software Engineering Workshop, Annual IEEE/NASA Goddard
ER -
 
Christopher Ackermann, Fraunhofer Center for Experimental Software Engineering Maryland, USA
Mikael Lindvall, Fraunhofer Center for Experimental Software Engineering Maryland, USA
During its lifecycle, software experiences numerous changes that are either due to bug fixes or to the incorporation of new features. Implementing such changes is often more difficult than expected, which frequently leads to underestimation of the associated implementation effort.

This paper describes work that aims to understand change impact based on the visualization of the characteristics of change requests using standard diagrams (e.g. UML diagrams). Each diagram depicts different aspects of a software system and can illustrate factors that might drive the implementation effort.

Using examples, in which we analyze three change requests, we describe how we determined the characteristics of the change requests. We furthermore discuss how the impact of change requests on diagrams relates to the implementation effort.

Our overall goal is to develop a new impact analysis approach that helps determine software change impact based on the use of specific diagrams.

Citation:
Christopher Ackermann, Mikael Lindvall, "Understanding Change Requests to Predict Software Impact," sew, pp.66-75, 30th Annual IEEE/NASA Software Engineering Workshop SEW-30 (SEW'06), 2006
Usage of this product signifies your acceptance of the Terms of Use.