Automatically identifying changes that impact code-to-design traceability during evolution

  • Authors:

  • Maen Hammad;Michael L. Collard;Jonathan I. Maletic

  • Affiliations:

  • Department of Computer Science, Kent State University, Kent, USA 44242;Department of Computer Science, The University of Akron, Akron, USA 44325;Department of Computer Science, Kent State University, Kent, USA 44242

  • Venue:
  • Software Quality Control
  • Year:
  • 2011

Quantified Score

Hi-index 0.00

Visualization

Abstract

An approach is presented that automatically determines if a given source code change impacts the design (i.e., UML class diagram) of the system. This allows code-to-design traceability to be consistently maintained as the source code evolves. The approach uses lightweight analysis and syntactic differencing of the source code changes to determine if the change alters the class diagram in the context of abstract design. The intent is to support both the simultaneous updating of design documents with code changes and bringing old design documents up to date with current code given the change history. An efficient tool was developed to support the approach and is applied to an open source system. The results are evaluated and compared against manual inspection by human experts. The tool performs better than (error prone) manual inspection. The developed approach and tool were used to empirically investigate and understand how changes to source code (i.e., commits) break code-to-design traceability during evolution and the benefits from such understanding. Commits are categorized as design impact or no impact. The commits of four open source projects over 3-year time durations are extracted and analyzed. The results of the study show that most of the code changes do not impact the design and these commits have a smaller number of changed files and changed less lines compared to commits with design impact. The results also show that most bug fixes do not impact design.