Replaying past changes in multi-developer projects

Hattori, Lile; Lungu, Mircea; Lanza, Michele (2010). Replaying past changes in multi-developer projects. In: Proceedings of the Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE) (pp. 13-22). New York: Association for Computing Machinery ACM 10.1145/1862372.1862379

Text p13-hattori.pdf - Published Version Restricted to registered users only Available under License Publisher holds Copyright. Download (1MB)

What was I working on before the weekend? and What were the members of my team working on during the last week? are common questions that are frequently asked by a developer. They can be answered if one keeps track of who changes what in the source code. In this work, we present Replay, a tool that allows one to replay past changes as they happened at a fine-grained level, where a developer can watch what she has done or understand what her colleagues have done in past development sessions. With this tool, developers are able to not only understand what sequence of changes brought the system to a certain state (e.g., the introduction of a defect), but also deduce reasons for why her colleagues performed those changes. One of the applications of such a tool is also discovering the changes that broke the code of a developer.

Interest & Impact

Downloads

0 since deposited on 04 Oct 2013
0 in the past 12 months

Citations

5 Citations in Web of Science ®
6 Citations in Scopus

Search

in Google Scholar™

Services

Actions (login required)

Edit item

Actions (login required)

Edit item