Enriching revision history with interactions

Authors:
Chris Parnin;Carsten Görg;Spencer Rugaber
Affiliations:
Georgia Institute of Technology, Atlanta, GA;Georgia Institute of Technology, Atlanta, GA;Georgia Institute of Technology, Atlanta, GA
Venue:
Proceedings of the 2006 international workshop on Mining software repositories
Year:
2006

Citing 8
Cited 3

Edit wear and read wear

CHI '92 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Term Weighting Approaches in Automatic Text Retrieval

Term Weighting Approaches in Automatic Text Retrieval
Mylar: a degree-of-interest model for IDEs

Proceedings of the 4th international conference on Aspect-oriented software development
Towards understanding programs through wear-based filtering

SoftVis '05 Proceedings of the 2005 ACM symposium on Software visualization
When do changes induce fixes?

MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Error detection by refactoring reconstruction

MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Mining student CVS repositories for performance indicators

MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
NavTracks: Supporting Navigation in Software Maintenance

ICSM '05 Proceedings of the 21st IEEE International Conference on Software Maintenance

Understanding interaction differences between newcomer and expert programmers

Proceedings of the 2008 international workshop on Recommendation systems for software engineering
A degree-of-knowledge model to capture source code familiarity

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Degree-of-knowledge: Modeling a developer's knowledge of code

ACM Transactions on Software Engineering and Methodology (TOSEM)

Quantified Score

Hi-index	0.00

Visualization

Abstract

Revision history provides a rich source of information to improve the understanding of changes made to programs, but it yields only limited insight into how these changes occurred. We explore an additional source of information - program viewing and editing history - where all historical artifacts associated with the program are included. In particular, we suggest augmenting revision histories with the interaction history of programmers. Using this additional information source enables the development of several interesting applications including an influence-recommendation system and a task-mining system. We present some results from a case study in which interaction histories from professional programmers were obtained and analyzed.