Industrial tools for the feature location problem: an exploratory study: Practice Articles

  • Authors:

  • Sharon Simmons;Dennis Edwards;Norman Wilde;Josh Homan;Michael Groble

  • Affiliations:

  • Department of Computer Science, University of West Florida, Pensacola, FL 32514, U.S.A.;Department of Computer Science, University of West Florida, Pensacola, FL 32514, U.S.A.;Department of Computer Science, University of West Florida, Pensacola, FL 32514, U.S.A.;Department of Computer Science, University of West Florida, Pensacola, FL 32514, U.S.A.;Motorola, Inc., 1295 East Algonquin Road, Schaumburg, IL 60196, U.S.A.

  • Venue:
  • Journal of Software Maintenance and Evolution: Research and Practice
  • Year:
  • 2006

Quantified Score

Hi-index 0.00

Visualization

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.