Visualization of fine-grained code change history

Yoon, Young Seok; Myers, Brad A.; Koo, Sebon

doi:10.1109/vlhcc.2013.6645254

Cited by 51 publications

(29 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An exploratory study with Fluorite identified various reasons why developers often have to backtrack during coding [26]. Moreover, Yoon et al presented Azurite [16], [27], a tool that employs two user interfaces to visualize finegrained code change history: a timeline view and a code history diff view. These views provide rich manipulation of code (e.g., selective undo) and simplify answering frequently asked questions related to code editing history.…”

Section: Toolsmentioning

confidence: 99%

“…For example, SpyWare [8], Syde [9], Fluorite [10], CodingTracker [11], and OperationRecorder [12] are embedded into modern integrated development environments (IDEs) and capture all of the fine-grained code changes performed on the editors provided by their respective IDEs. In addition, some of these recording tools collaborate with tools that visualize, filter, and/or replay recorded code changes [13]- [16].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

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

Section: Toolsmentioning

confidence: 99%

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

show abstract

“…AZURITE is an Eclipse plug-in that visualizes fine-grained code change histories [12]. The tool provides two views that let developers navigate through the history of changes.…”

Section: Related Workmentioning

confidence: 99%

Visual Storytelling of Development Sessions

Minelli

Baracchi

Mocci

et al. 2014

2014 IEEE International Conference on Software Maintenance and Evolution

View full text Add to dashboard Cite

Most development activities, like program understanding, source code navigation and editing, are supported by Integrated Development Environments (IDEs). They provide different tools and user interfaces (UI) to interact with the source code, such as browsers, debuggers, and inspectors. It is uncertain how and when programmers use different UI elements of an IDE and to what extent they appropriately support development.Previously we developed DFLOW, a tool that seamlessly records and processes interaction data. Our long-term goal is to assess to what extent the UIs of IDEs support the workflow of developers and whether they can be improved. As a first step we present our approach to analyze development sessions in the form of visual storytelling. We illustrate our initial catalogue of visualizations through two development stories.

show abstract

“…The timeline visualization is the basic user interface used to interact with the edit history. More details of timeline visualization and the other user interfaces can be found in [3].…”

Section: A Timeline Visualizationmentioning

confidence: 99%

“…The demonstrated features will include the user interfaces that were previously published [3], as well as newly added features designed based on user feedback (Section III).…”

Section: Introductionmentioning

confidence: 99%

A demonstration of AZURITE: Backtracking tool for programmers

Myers

2014

2014 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)

Self Cite

View full text Add to dashboard Cite

Abstract-Programmers often need to backtrack, but backtracking support in modern programming environments is limited. Previously, we have conducted a series of studies, which discovered that backtracking in programming is in fact prevalent and programmers need better backtracking tools. In this demonstration, we will present our backtracking tool called AZURITE, which provides selective undo and history search and visualization features in the Eclipse code editor. The demonstration will include the user interface presented in our previous work, as well as the new features added in response to user feedback.

show abstract

Visualization of fine-grained code change history

Cited by 51 publications

References 36 publications

Slicing Fine-Grained Code Change History

Slicing Fine-Grained Code Change History

Visual Storytelling of Development Sessions

A demonstration of AZURITE: Backtracking tool for programmers

Contact Info

Product

Resources

About