Locating Features in Source Code

598 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Asking and Answering Questions during a Programming Change Task (2008, background): “Eisenbarth and Koschke combines dynamic and static analysis information to identify computation units that contribute to a feature [10].”
Software Architecture Reconstruction: A Process-Oriented Taxonomy (2009, background): “Formal concept analysis is a branch of lattice theory used to identify design patterns [6], features [35], [52], or modules [143].”
Feature location in source code: a taxonomy and survey (2013, methodology): “’s [7] formal concept analysis of execution traces FLT in an industrial setting.”
Feature Location Using Probabilistic Ranking of Methods Based on Execution Scenarios and Information Retrieval (2007, background): “[9] combined both static (that is, dependencies) and dynamic (that is, execution traces) data to identify features in programs.”
A Systematic Survey of Program Comprehension through Dynamic Analysis (2008, background): “Since program comprehension is a broad subject that has potential overlaps with such fields as debugging, a clear definition of the scope of our survey is required.”
An information retrieval approach to concept location in source code (2004, background): “Eisenbarth et al. [9] use dynamic information gathered from scenarios of invoking features in a system.”
IssueExec: A Test-Driven Approach for Localizing Software Engineering Issues (2026, unknown): “Publication date: May 2018.”