Industrial tools for the feature location problem: an exploratory study

Abstract

Software engineers who maintain and enhance large systems often encounter the feature location problem: where in the many thousands of lines of code is a particular user feature implemented? Several methods of addressing the problem have been proposed, most of which involve tracing the execution of the system and analyzing the traces. Some supporting academic tools are available. However, companies that depend on the successful evolution of large systems are more likely to use new methods if they are supported by industrial‐strength tools of known reliability. This article describes a study performed with Motorola, Inc. to see whether there were any pitfalls in using Metrowerks CodeTEST and Klocwork inSight for feature location on message‐passing software similar to systems that Motorola maintains. These two tools were combined with TraceGraph, an academic trace comparison tool. The study identified two main problems. First, some ‘glue’ code and workarounds were needed to get CodeTEST to generate a trace for an interval of time in which the feature was operating. Second, getting information out of TraceGraph and into inSight was needlessly complicated for a user. However, with a moderate amount of work, the tool combination was effective in locating, understanding and documenting features. Study participants completed these steps in typically 3–4 hours per feature, studying only a few hundred lines out of a 200 000 line system. An ongoing project with Motorola is focused on improving tool integration with the hope of making feature location common practice at Motorola. Copyright © 2006 John Wiley & Sons, Ltd.

A Controlled Experiment for Program Comprehension through Trace Visualization

“…OVATION; TPTP* preliminary; user feedback general understanding [15] SCENE* preliminary software reuse [6], [16] ISVIS* case study architecture reconstruction, feature location [17], [18] SCED; SHIMBA case study debugging; various comprehension tasks [19] FORM case study detailed understanding; distributed systems [20] JAVAVIS preliminary; user feedback educational purposes; detailed understanding [21], [4], [22], [23] SEAT small case studies; user feedback general understanding [24], [25], [26], [27] SCENARIOGRAPHER multiple case studies detailed understanding; distributed systems; feature analysis; large-scale software [28], [29], [30] small case study quality control; conformance checking [10] multiple case studies general understanding [31] case study trace comparison; feature analysis [32] case study feature analysis [33] case study architecture reconstruction; conformance checking; behavioral profiles [34] TRACEGRAPH industrial case study feature analysis [35], [36] SDR; JRET* multiple case studies detailed understanding through test cases [37] FIELD; JIVE; JOVE multiple case studies performance monitoring; phase detection [38] --API understanding [39], [7] EXTRAVIS* multiple case studies fan-in/-out analysis; feature analysis; phase detection [40] OASIS user study various comprehension tasks [41] small case studies general understanding; wireless sensor networks March 8, 2010 DRAFT Cornelissen, Zaidman, van Deursen -A Controlled Experiment for Program Comprehension…”

“…Their ideas are illustrated in a case study. Simmons et al used TraceGraph to compare execution traces with the aim of locating features [34]. Furthermore, they integrate the results of their feature location technique into a commercial static analysis tool so as to make feature location more accessible to their industrial partner.…”

Concept location using formal concept analysis and information retrieval

“…A more up-to-date summary of all existing approaches can be found in the literature [Antoniol and Guéhéneuc 2006;Revelle and Poshyvanyk 2009], whereas a summary of industrial tools available for feature location is available in the work of Simmons et al [Simmons et al 2006].…”

Combining Formal Concept Analysis with Information Retrieval for Concept Location in Source Code

“…A more up-to-date summary of all existing approaches can be found in [5], whereas a summary of industrial tools available for feature location is available in [18].…”