Blending Conceptual and Evolutionary Couplings to Support Change Impact Analysis in Source Code
Authors:
- Huzefa KagdiHKHuzefa Kagdi
- Malcom GethersMGMalcom Gethers
- Denys PoshyvanykDPDenys Poshyvanyk
- Michael L. CollardMCMichael L. Collard
- 1 October 2010
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 10951350,p. 119-128
Abstract
The paper presents an approach that combines conceptual and evolutionary techniques to support change impact analysis in source code. Information Retrieval (IR) is used to derive conceptual couplings from the source code in a single version (release) of a software system. Evolutionary couplings are mined from source code commits. The premise is that such combined methods provide improvements to the accuracy of impact sets. A rigorous empirical assessment on the changes of the open source systems Apache httpd, ArgoUML, iBatis, and KOffice is also reported. The results show that a combination of these two techniques, across several cut points, provides statistically significant improvements in accuracy over either of the two techniques used independently. Improvements in recall values of up to 20% over the conceptual technique in KOffice and up to 45% over the evolutionary technique in iBatis were reported.Keywords
This publication has 38 references indexed in Scilit:
- Using information retrieval based coupling measures for impact analysisEmpirical Software Engineering, 2008
- Recovering traceability links in software artifact management systems using information retrieval methodsACM Transactions on Software Engineering and Methodology, 2007
- Combining Formal Concept Analysis with Information Retrieval for Concept Location in Source Code2007
- The Conceptual Coupling Metrics for Object-Oriented Systems2007 IEEE International Conference on Software Maintenance, 2006
- Concise and Consistent Naming2005
- An XML-based lightweight C++ fact extractor2004
- An approach to classify software maintenance requests2003
- Points-to analysis for Java using annotated constraints2001
- The impact analysis task in software maintenance: a model and a case study1994
- Using program slicing in software maintenanceIEEE Transactions on Software Engineering, 1991