Abstract—This research extends an existing source code change taxonomy that was designed to analyze change coupling. The extension expands change types related to statements in order to achieve more granular data about the type of statement that is changed. The extended taxonomy is evaluated to determine if it can be applied to software fault analysis. We found that the extended change types occur consistently and with high frequency in fault fixes for Eclipse 2.0 and 3.0. Faults were then clustered according to the source code changes and analyzed. We found that the types and sizes of clusters are highly correlated, indicating some consistency in the patterns of the fault fixes. Finally, we performed an initial investigation to determine w...
Example-based transformational approaches to automate adaptive maintenance changes plays an importan...
To reduce the manual effort of assessing potential affected program parts during software evolution,...
To reduce the manual effort of assessing potential affected program parts during software evolution,...
Preprint of paper published in: 9th IEEE Working Conference on Mining Software Repositories (MSR), 2...
In software evolution analysis, many approaches analyze release history data available through versi...
A quality assurance activity, known as software fault prediction, can reduce development costs and i...
During program development, testing and code editing are interleaved activities. When tests unexpect...
Software products can only be improved if we have a good understanding of the faults they typically ...
Software products can only be improved if we have a good understanding of the faults they typically ...
Abstract—Keeping evolving systems fault free is hard. Change impact analysis is a well-studied metho...
Bug fix is an important and challenging task in software development and maintenance. Bug fix is als...
This paper introduces a new technique for finding latent software bugs called change classification....
Twenty-seven automatically extractable bug fix patterns are defined using the syntax components and ...
Traditional algorithms for detecting differences in source code focus on differences between lines. ...
Many research areas in software engineering, such as mutation testing, automatic repair, fault local...
Example-based transformational approaches to automate adaptive maintenance changes plays an importan...
To reduce the manual effort of assessing potential affected program parts during software evolution,...
To reduce the manual effort of assessing potential affected program parts during software evolution,...
Preprint of paper published in: 9th IEEE Working Conference on Mining Software Repositories (MSR), 2...
In software evolution analysis, many approaches analyze release history data available through versi...
A quality assurance activity, known as software fault prediction, can reduce development costs and i...
During program development, testing and code editing are interleaved activities. When tests unexpect...
Software products can only be improved if we have a good understanding of the faults they typically ...
Software products can only be improved if we have a good understanding of the faults they typically ...
Abstract—Keeping evolving systems fault free is hard. Change impact analysis is a well-studied metho...
Bug fix is an important and challenging task in software development and maintenance. Bug fix is als...
This paper introduces a new technique for finding latent software bugs called change classification....
Twenty-seven automatically extractable bug fix patterns are defined using the syntax components and ...
Traditional algorithms for detecting differences in source code focus on differences between lines. ...
Many research areas in software engineering, such as mutation testing, automatic repair, fault local...
Example-based transformational approaches to automate adaptive maintenance changes plays an importan...
To reduce the manual effort of assessing potential affected program parts during software evolution,...
To reduce the manual effort of assessing potential affected program parts during software evolution,...