Dimensions of tools for detecting software conflicts

  • Authors:
  • Prasun Dewan

  • Affiliations:
  • University of North Carolina, Chapel Hill, NC

  • Venue:
  • Proceedings of the 2008 international workshop on Recommendation systems for software engineering
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

Previous work has found that the number of defects in a source file is proportional to the number of developers who concurrently access the file. Several "conflict-recommender" tools have been proposed that can aid programmers in detecting conflicts that lead to such defects. These can be classified according to several design dimensions including how early in the programming process the (potential) conflict is identified; which, if any, of existing software systems must be extended to create the tool; the granularity of the program constructs that are identified as conflicting; the criteria used for identifying conflicts; how the conflict information is obtained; and whether the tool supports individual or collaborative inspection of the conflict. The various points defined by this design space can be analyzed according to several evaluation dimensions including the number of false positives and negatives given by the tool; how much effort is required to find/fix the conflict; the computation and communication costs of the tool; how much change it requires to the current software development process; how much screen realestate is used by the tool during coding; and to what extent is the privacy of programmers invaded. The identification and analysis of these design and evaluation dimensions can lead to better evaluation of the various aspects of existing tools and an integrated tool that combines orthogonal features of different tools.