eROSE: guiding programmers in eclipse

Authors:
Thomas Zimmermann;Valentin Dallmeier;Konstantin Halachev;Andreas Zeller
Affiliations:
Saarland University, Saarbrücken, Germany;Saarland University, Saarbrücken, Germany;Saarland University, Saarbrücken, Germany;Saarland University, Saarbrücken, Germany
Venue:
OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Year:
2005

Citing 2
Cited 1

Fast Algorithms for Mining Association Rules in Large Databases

VLDB '94 Proceedings of the 20th International Conference on Very Large Data Bases
Mining Version Histories to Guide Software Changes

IEEE Transactions on Software Engineering

Subverting the fundamentals sequence: using version control to enhance course management

Proceedings of the 38th SIGCSE technical symposium on Computer science education

Quantified Score

Hi-index	0.00

Visualization

Abstract

The eROSE plugin for ECLIPSE uses version archives to guide programmers: You changed fKeys[] and eROSE suggests you to change initDefaults(), because both items always have been changed together in the past. In addition, eROSE points out item coupling that is undetectable by program analysis, for instance between fKeys[] and a properties file. All eROSE needs is a CVS repository; we designed eROSE to be as efficient and unobtrusive as possible.