2007
DOI: 10.1109/tse.2007.1016
|View full text |Cite
|
Sign up to set email alerts
|

Feature Location Using Probabilistic Ranking of Methods Based on Execution Scenarios and Information Retrieval

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
362
0
1

Year Published

2009
2009
2016
2016

Publication Types

Select...
5
3
1

Relationship

5
4

Authors

Journals

citations
Cited by 395 publications
(380 citation statements)
references
References 42 publications
1
362
0
1
Order By: Relevance
“…In their seminal work, Wilde and Scully [24] used test cases to produce execution traces; concepts location was performed by comparing different traces: one in which the concept is executed and another without concept. Similarly, Poshyvanyk et al [19] used multiple traces from multiple scenarios.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In their seminal work, Wilde and Scully [24] used test cases to produce execution traces; concepts location was performed by comparing different traces: one in which the concept is executed and another without concept. Similarly, Poshyvanyk et al [19] used multiple traces from multiple scenarios.…”
Section: Related Workmentioning
confidence: 99%
“…An important task during program comprehension is concept location, which aims at identifying concepts (e.g., domain concepts, user-observable features) and locating them within code regions or, more generally, into software artifact chunks [14,8]. The literature reports concept location approaches built upon static [1] and dynamic [24,23] analyses; information retrieval (IR) [19]; and hybrid (static and dynamic) [3,12,5] techniques. Dynamic and hybrid approaches rely on execution traces.…”
Section: Introductionmentioning
confidence: 99%
“…For a given class C (considered to be a starting point of a change task, which may be identified by a programmer via a feature location technique, e.g., PROMESIR [34]), the remaining classes in the system are ranked according to their strength of coupling to the class C, based on a coupling measure or a combination of such measures (see some previous work on the details [8,35]). The list of ranked classes is presented to the developer for further inspection (for instance, a ranked list of classes as shown in an existing tool for impact analysis, namely JRipples [32]).…”
Section: ) Impact Analysis Using Coupling Metricsmentioning
confidence: 99%
“…Identifying the parts of the source code that correspond to a specific functionality is a prerequisite to several maintenance tasks. This process is referred to as feature location [13] and it is a part of the incremental change [15]. For example, assume a developer is working on text editor software and needs to modify the file printing feature to ensure the files can be also printed to PDF format.…”
Section: A Feature Location (Fl)mentioning
confidence: 99%