On dynamic feature location

Koschke, Rainer; Quante, Jochen

doi:10.1145/1101908.1101923

Cited by 54 publications

(34 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Full methods are associated with features. However, only a small portion of the code in a method may actually pertain to a feature (Koschke and Quante 2005;Revelle et al 2005). Therefore, a finer level of granularity such as statements or basic blocks would be more accurate.…”

Section: Internal Threats To Validitymentioning

confidence: 99%

Using structural and textual information to capture feature coupling in object-oriented software

2011

View full text Add to dashboard Cite

Previous studies have demonstrated the relationship between coupling and external software quality attributes, such as fault-proneness, and the application of coupling to software maintenance tasks, such as impact analysis. These previous studies concentrate on class coupling. However, there is a growing focus on the study of features in software, and features are often implemented across multiple classes, meaning class-level coupling measures are not applicable. We ask the pertinent question, "Is measuring coupling at the feature-level also useful?" We define new feature coupling metrics based on structural and textual source code information and extend the unified framework for coupling measurement to include these new metrics. We also conduct three extensive case studies to evaluate these new metrics and answer this research question. The first study examines the relationship between feature coupling and fault-proneness, the second assesses feature coupling in the context of impact analysis, and the third study surveys developers to determine if the metrics align with what they consider to be coupled features. All three studies provide evidence that feature coupling metrics are indeed useful new measures that capture coupling at a higher level of abstraction than classes and can be useful for finding bugs, guiding testing effort, and assessing impact of changes.

show abstract

Section: Internal Threats To Validitymentioning

confidence: 99%

Using structural and textual information to capture feature coupling in object-oriented software

2011

View full text Add to dashboard Cite

show abstract

“…Koschke's approach [7] extracting feature-specific methods is a promising approach to extracting phase-specific methods. Rountev's approach [15] extracting variable names for objects may be effective to extract names of important objects representing a phase.…”

Section: Mapping Features To Phasesmentioning

confidence: 99%

Feature-level phase detection for execution trace using object cache

Watanabe

Ishio

Inoue

2008

Proceedings of the 2008 International Workshop on Dynamic Analysis: Held in Conjunction With the ACM SIGSOFT International Symp

View full text Add to dashboard Cite

Visualizing collaborations of objects is important for developers understanding and debugging an object-oriented program. Many techniques and tools are proposed to visualize dynamic collaborations involved in an execution trace of a system, however, an execution trace may be too large to be transformed into a single diagram. In this paper, we propose a novel approach to efficiently detecting phases, or high-level behavioral units described in a use-case scenario. Our idea is based on the nature of object-oriented programming; a phase starts with preparing objects for the phase and ends with destroying temporary objects. Our technique uses a LRU cache for observing a working set of objects, and interprets a sharp rise in the frequency of the cache update as a phase transition. We have applied our approach to two industrial applications and found that our approach is promising to visualize a phase corresponding to a feature as a sequence diagram.

show abstract

“…While dynamic approaches collect precise information about the program execution, they are safe only with respect to the input that was actually considered during runtime to gather the information, and generalizing from this data may not be safe [20]. In addition, while generally a feature is a realization of a system requirement -either functional or non-functional -executable test-cases or scenarios can exhibit only functional requirements of the system that are visible at the user level.…”

Section: Classification and Methodologymentioning

confidence: 99%

“…Koschke et al [20] extend the work of Eisenbarth et al [14] by considering statement-level rather than method-level computation units.…”

Section: Plain Outputmentioning

confidence: 99%

A Survey of Feature Location Techniques

2013

View full text Add to dashboard Cite

Feature location techniques aim at locating software artifacts that implement a specific program functionality, a.k.a. a feature. These techniques support developers during various activities such as software maintenance, aspect-or featureoriented refactoring, and others. For example, detecting artifacts that correspond to product line features can assist the transition from unstructured to systematic reuse approaches promoted by software product line engineering (SPLE). Managing features, as well as the traceability between these features and the artifacts that implement them, is an essential task of the SPLE domain engineering phase, during which the product line resources are specified, designed and implemented. In this chapter, we provide an overview of existing feature location techniques. We describe their implementation strategies and exemplify the techniques on a realistic use-case. We also discuss their properties, strengths and weaknesses and provide guidelines that can be used by practitioners when deciding which feature location technique to choose. Our survey shows that none of the existing feature location techniques are designed to consider families of related products and only treat different products of a product line as individual, unrelated entities. We thus discuss possible directions for leveraging SPLE architectures in order to improve the feature location process.

show abstract

On dynamic feature location

Cited by 54 publications

References 9 publications

Using structural and textual information to capture feature coupling in object-oriented software

Using structural and textual information to capture feature coupling in object-oriented software

Feature-level phase detection for execution trace using object cache

A Survey of Feature Location Techniques

Contact Info

Product

Resources

About