Last updated on Monday, October 06, 2025
@inproceedings{VanRysselberghe04ICSM,
author = {Filip {Van Rysselberghe} and Serge Demeyer},
booktitle = {Proceedings {ICSM}'04 (International Conference on
Software Maintenance)},
note = {Acceptance ratio: 48/122 = 39\%},
pages = {328-337},
publisher = {{IEEE} Press},
title = {Studying Software Evolution Information By
Visualizing the Change History},
year = {2004},
abstract = {Before re-engineering a large and complex software
system, it is wise to study its change history in
order to identify the most valuable and problematic
parts. Unfortunately, typical change histories
contain thousands of entries, therefore the challenge
is to discover those changes which are relevant for
both the current and future situations of our product
and process. In this paper, we demonstrate how a
simple visualization allows us to recognize relevant
changes. Applying the technique on the change history
of Tomcat, we have been able to identify (a) unstable
components, (b) coherent entities, (c) design and
architectural evolution, and (d) fluctuations in team
productivity},
annote = {internationalconference},
top = {A in CORE2013},
}