Skip to main navigation Skip to search Skip to main content

The impact of view histories on edit recommendations

  • Seonah Lee
  • , Sungwon Kang
  • , Sunghun Kim
  • , Matt Staats

Research output: Contribution to journalJournal Articlepeer-review

Abstract

Recommendation systems are intended to increase developer productivity by recommending files to edit. These systems mine association rules in software revision histories. However, mining coarse-grained rules using only edit histories produces recommendations with low accuracy, and can only produce recommendations after a developer edits a file. In this work, we explore the use of finer-grained association rules, based on the insight that view histories help characterize the contexts of files to edit. To leverage this additional context and fine-grained association rules, we have developed MI, a recommendation system extending ROSE, an existing edit-based recommendation system. We then conducted a comparative simulation of ROSE and MI using the interaction histories stored in the Eclipse Bugzilla system. The simulation demonstrates that MI predicts the files to edit with significantly higher recommendation accuracy than ROSE (about 63 over 35 percent), and makes recommendations earlier, often before developers begin editing. Our results clearly demonstrate the value of considering both views and edits in systems to recommend files to edit, and results in more accurate, earlier, and more flexible recommendations.

Original languageEnglish
Article number6926851
Pages (from-to)314-330
Number of pages17
JournalIEEE Transactions on Software Engineering
Volume41
Issue number3
DOIs
Publication statusPublished - 1 Mar 2015

Bibliographical note

Publisher Copyright:
© 2014 IEEE.

Keywords

  • Programming environments/construction tools
  • association rules
  • data mining
  • interactive environments
  • programmer interaction histories
  • software maintenance

Fingerprint

Dive into the research topics of 'The impact of view histories on edit recommendations'. Together they form a unique fingerprint.

Cite this