Software Evolution Comprehension: Replay to the Rescue

Hattori, Lile; D’Ambros, Marco; Lanza, Michele; Lungu, Mircea

doi:10.1109/icpc.2011.39

Cited by 27 publications

(34 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We further looked for questions spanning multiple facets to evaluate our integrated approach. We compiled our set of 13 tasks from the work of LaToza et al [2006], Sillito et al [2006;2008], Ko et al [2007], de Alwis and Murphy [2008], Fritz and Murphy [2010], and Hattori et al [2011]. These tasks are listed in Table III.…”

Section: Choosing the Tasksmentioning

confidence: 99%

“…The developers who have changed Class 3 in the past? [Hattori et al 2011] Rationale. Team activity awareness is helpful for coordination and for finding experts of a particular part of a software system.…”

Section: History Domain T4mentioning

confidence: 99%

“…The last five files changed by Developer 1 ? [Hattori et al 2011] Rationale. When one has to replace a previous project team member, it is important to quickly get an overview on the member's previous work.…”

Section: History Domain T4mentioning

confidence: 99%

See 2 more Smart Citations

Evaluating a query framework for software evolution data

Würsch

Giger

Gall

2013

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

With the steady advances in tooling to support software engineering, mastering all the features of modern IDEs, version control systems, and project trackers is becoming increasingly difficult. Answering even the most common developer questions can be surprisingly tedious and difficult. In this paper we present a user study with 35 subjects to evaluate our quasi-natural language interface that provides access to various facets of the evolution of a software system but requires almost zero learning effort. Our approach is tightly woven into the Eclipse IDE and allows developers to answer questions related to source code, development history, or bug and issue management. The results of our evaluation show that our query interface can outperform classical software engineering tools in terms of correctness, while yielding significant time savings to its users and greatly advancing the state of the art in terms of usability and learnability. A Evaluating a Query Framework for Software Evolution DataMICHAEL WÜRSCH, EMANUEL GIGER, and HARALD C. GALL, Department of Informatics, University of ZurichWith the steady advances in tooling to support software engineering, mastering all the features of modern IDEs, version control systems, and project trackers is becoming increasingly difficult. Answering even the most common developer questions can be surprisingly tedious and difficult. In this paper we present a user study with 35 subjects to evaluate our quasi-natural language interface that provides access to various facets of the evolution of a software system but requires almost zero learning effort. Our approach is tightly woven into the Eclipse IDE and allows developers to answer questions related to source code, development history, or bug and issue management. The results of our evaluation show that our query interface can outperform classical software engineering tools in terms of correctness, while yielding significant time savings to its users and greatly advancing the state of the art in terms of usability and learnability.

show abstract

Section: Choosing the Tasksmentioning

confidence: 99%

Section: History Domain T4mentioning

confidence: 99%

See 1 more Smart Citation

Evaluating a query framework for software evolution data

Würsch

Giger

Gall

2013

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…Syde and Replay are tools for Eclipse that can record finegrained change history of Javabased systems in multi developer settings [8]. These tools are intended to help developers understand the code's evolution, but they could Figure 1.…”

Section: Related Workmentioning

confidence: 99%

Capturing and analyzing low-level events from the code editor

Yoon

Myers

2011

Proceedings of the 3rd ACM SIGPLAN Workshop on Evaluation and Usability of Programming Languages and Tools

View full text Add to dashboard Cite

In this paper, we present FLUORITE, a publicly available event logging plugin for Eclipse which captures all of the lowlevel events when using the Eclipse code editor. FLUORITE captures not only what types of events occurred in the code editor, but also more detailed information such as the inserted and deleted text and the specific parameters for each command. This enables the detection of many usage patterns that could otherwise not be recognized, such as "typo correction" that requires knowing that the entered text is immediately deleted and replaced. Moreover, the snapshots of each source code file that has been opened during the session can be completely reproduced using the collected information. We also provide analysis and visual ization tools which report various statistics about usage patterns, and we provide the logs in an XML format so others can write their own analyzers. FLUORITE can be used for not only evaluating existing tools, but also for discover ing issues that motivate new tools.

show abstract

“…For example, a controlled experiment conducted by Hattori et al demonstrated that the chronological replaying of finegrained code changes outperforms existing commit-based versioning systems such as CVS [17] or Subversion [18] by helping programmers find answers to questions related to software evolution [19]. In addition, Parnin and DeLine investigated what is needed to assist programmers when they resume interrupted programming tasks [20].…”

Section: Introductionmentioning

confidence: 99%

Slicing Fine-Grained Code Change History

Maruyama

Omori

Hayashi

2016

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYChange-aware development environments can automatically record fine-grained code changes on a program and allow programmers to replay the recorded changes in chronological order. However, since they do not always need to replay all the code changes to investigate how a particular entity of the program has been changed, they often eliminate several code changes of no interest by manually skipping them in replaying. This skipping action is an obstacle that makes many programmers hesitate when they use existing replaying tools. This paper proposes a slicing mechanism that automatically removes manually skipped code changes from the whole history of past code changes and extracts only those necessary to build a particular class member of a Java program. In this mechanism, fine-grained code changes are represented by edit operations recorded on the source code of a program and dependencies among edit operations are formalized. The paper also presents a running tool that slices the operation history and replays its resulting slices. With this tool, programmers can avoid replaying nonessential edit operations for the construction of class members that they want to understand. Experimental results show that the tool offered improvements over conventional replaying tools with respect to the reduction of the number of edit operations needed to be examined and over history filtering tools with respect to the accuracy of edit operations to be replayed.

show abstract

Software Evolution Comprehension: Replay to the Rescue

Cited by 27 publications

References 25 publications

Evaluating a query framework for software evolution data

Evaluating a query framework for software evolution data

Capturing and analyzing low-level events from the code editor

Slicing Fine-Grained Code Change History

Contact Info

Product

Resources

About