Which Feature Location Technique is Better?

被引:7
作者
Hill, Emily [1 ]
Bacchelli, Alberto [2 ,3 ]
Binkley, Dave [4 ]
Dit, Bogdan [5 ]
Lawrie, Dawn [4 ]
Oliveto, Rocco [6 ]
机构
[1] Montclair State Univ, Montclair, NJ 07043 USA
[2] Univ Lugano, Lugano, Switzerland
[3] Delft Univ Technol, NL-2600 AA Delft, Netherlands
[4] Loyola Univ Maryland, Baltimore, MD USA
[5] Coll William & Mary, Williamsburg, VA 23187 USA
[6] Univ Molise, Pessac, France
来源
2013 29TH IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE (ICSM) | 2013年
关键词
Feature location; Concern location; Relevance measures; Empirical studies;
D O I
10.1109/ICSM.2013.59
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
Feature location is a fundamental step in software evolution tasks such as debugging, understanding, and reuse. Numerous automated and semi-automated feature location techniques (FLTs) have been proposed, but the question remains: How do we objectively determine which FLT is most effective? Existing evaluations frequently use bug fix data, which includes the location of the fix, but not what other code needs to be understood to make the fix. Existing evaluation measures such as precision, recall, effectiveness, mean average precision (MAP), and mean reciprocal rank (MRR) will not differentiate between a FLT that ranks higher these related elements over completely irrelevant ones. We propose an alternative measure of relevance based on the likelihood of a developer finding the bug fix locations from a ranked list of results. Our initial evaluation shows that by modeling user behavior, our proposed evaluation methodology can compare and evaluate FLTs fairly.
引用
收藏
页码:408 / 411
页数:4
相关论文
共 11 条
[1]  
[Anonymous], 2008, Introduction to information retrieval
[2]  
[Anonymous], SOCSTR20073 MCGILL U
[3]  
[Anonymous], MSR
[4]  
[Anonymous], ICSE
[5]  
Dit B., 2013, MSR
[6]   Feature location in source code: a taxonomy and survey [J].
Dit, Bogdan ;
Revelle, Meghan ;
Gethers, Malcom ;
Poshyvanyk, Denys .
JOURNAL OF SOFTWARE-EVOLUTION AND PROCESS, 2013, 25 (01) :53-95
[7]  
Lawrance J., 2013, IEEE TSE, V39
[8]  
Petrenko M., 2013, INF SOFTW TECH, V55
[9]  
Rajlich V., 2002, IWPC
[10]  
Savage T., 2010, AOSD