The Community for Technology Leaders
RSS Icon
Issue No.07 - July (2000 vol.26)
pp: 653-661
<p><b>Abstract</b>—This paper is an attempt to understand the processes by which software ages. We define code to be aged or decayed if its structure makes it unnecessarily difficult to understand or change and we measure the extent of decay by counting the number of faults in code in a period of time. Using change management data from a very large, long-lived software system, we explore the extent to which measurements from the change history are successful in predicting the distribution over modules of these incidences of faults. In general, process measures based on the change history are more useful in predicting fault rates than product metrics of the code: For instance, the number of times code has been changed is a better indication of how many faults it will contain than is its length. We also compare the fault rates of code of various ages, finding that if a module is, on the average, a year older than an otherwise similar module, the older module will have roughly a third fewer faults. Our most successful model measures the fault potential of a module as the sum of contributions from all of the times the module has been changed, with large, recent changes receiving the most weight.</p>
Fault potential, code decay, change management data, metrics, statistical analysis, generalized linear models.
Todd L. Graves, Alan F. Karr, J.s. Marron, Harvey Siy, "Predicting Fault Incidence Using Software Change History", IEEE Transactions on Software Engineering, vol.26, no. 7, pp. 653-661, July 2000, doi:10.1109/32.859533
18 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool