kirancodes.me
To Proof Maintenance & Beyond!

Development History Granularity Transformations (N)

Kivanç Muslu, Luke Swart, Yuriy Brun, Michael D. Ernst

Abstract

Development histories can simplify some software engineering tasks, butdifferent tasks require different history granularities. For example, a history that includes every edit that resulted in compiling code is needed when searching for the cause of a regression, whereas a history that contains only changes relevant to a feature is needed for understanding the evolution of the feature. Unfortunately, today, both manual and automated history generation result in a single-granularity history. This paper introduces the concept of multi-grained development history views and the architecture of Codebase Manipulation, a tool that automatically records a fine-grained history and manages its granularity by applying granularity transformations.

BibTeX
@inproceedings{Muslu-al:ASE15,
  author    = {Kivan{\c{c}} Muslu and
               Luke Swart and
               Yuriy Brun and
               Michael D. Ernst},
  title     = {Development History Granularity Transformations {(N)}},
  booktitle = {ASE},
  pages     = {697--702},
  publisher = {{IEEE} Computer Society},
  year      = {2015},
}

Related papers