Tools for supporting the collaborative process

Rhyne, James R.; Wolf, Catherine G.

doi:10.1145/142621.142645

Cited by 20 publications

(7 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The DDG fragment shows that the Undo Extract Dimension step takes the developer to another Revert [1] step. In this second invocation of the Revert step, the changes are reverted when pfroot [6] is returned to its original state before the Extract Dimension step. This enables the developer to make another selection with dimension [1]=source.…”

Section: Supporting Undomentioning

confidence: 99%

“…The notions of undo list to keep track of chronologically-ordered, program-state derivations and time to mark an event in the program, are similar to our proposed DDG and process control-flow definitions in the process domain. Rhyne and Wolf proposed to add a log of user actions, in addition to the history list that only keeps program state derivations [6]. This joins control-flow and data-flow, similarly to what a DDG does, but DDG is a history with respect to the process.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Supporting process undo and redo in software engineering decision making

Zhao

Brun

Osterweil

2013

Proceedings of the 2013 International Conference on Software and System Process

View full text Add to dashboard Cite

This paper presents a provenance-based approach for supporting undo and redo for software engineers. Writing software entails creating and reworking intricately intertwined software artifacts. After discovering a mistake in an earlier-completed task, a developer may wish to redo this task, but without undoing much of the work done since. Unfortunately, state-of-the-practice undo and redo mechanisms force the developer to manually redo the work completed since the mistake. This can cause considerable extra, often errorprone work.We propose tracking the software engineering process provenance data, and using it to enable (1) undoing tasks by reverting the state of the process execution, (2) revisiting an old task while storing the provenance of undone tasks, and (3) automatically redoing those undone tasks that are consistent with the revision. Our case study of a developer performing a well-understood but complex refactoring demonstrates how our approach can greatly reduce the cost of mistakes made early but discovered late.

show abstract

Section: Supporting Undomentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Supporting process undo and redo in software engineering decision making

Zhao

Brun

Osterweil

2013

Proceedings of the 2013 International Conference on Software and System Process

View full text Add to dashboard Cite

show abstract

“…In the WeMet system [15]a distributed, collaborative drawing systemthe history is also automatically captured. According to the authors this allows users to "reconstruct the present," and among other things allows parties that join work in progress to review the work performed by the other participants so far.…”

Section: History Through Capture and Accessmentioning

confidence: 99%

Where do web sites come from?

Klemmer

Thomsen

Phelps-Goodman

et al. 2002

Proceedings of the SIGCHI Conference on Human Factors in Computing Systems

View full text Add to dashboard Cite

To form a deep understanding of the present; we need to find and engage history. We present an informal history capture and retrieval mechanism for collaborative, earlystage information design. This history system is implemented in the context of the Designers' Outpost, a wall-scale, tangible interface for collaborative web site design. The interface elements in this history system are designed to be fluid and comfortable for early-phase design. As demonstrated by an informal lab study with six professional designers, this history system enhances the design process itself, and provides new opportunities for reasoning about the design of complex artifacts. The Designers' Outpost: Collaborative DesignOur history system is built as an extension of the Designers' Outpost [7], a tool that supports information design for the web. In our previous studies into web design, we found that pens, paper, walls, and tables were often used for explaining, developing, and communicating ideas during the early phases of design. Outpost embraces and extends this paper-based practice through a large electronic wall with a tangible user interface (see Figure 1).Users have the same fundamental capabilities in the Outpost system as in a paper and whiteboard system. One can create new pages by writing on new Post-it notes, add them to the electronic wall and organize a site by physically Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.

show abstract

“…In most applications (including examples in the literature such as [12] and [16]), history is represented by a graph with a maximal vertex degree of one (more commonly known as a "line"), as in Figure 1.…”

Section: Background: History Models For Single-level Undo/redomentioning

confidence: 99%

“…These include such tools as GINA [1] and Amulet [13], which use a complex branching model of time for undo and redo operations; Chimera [12], which provides a history model which preserves dependency relationships between operations; WeMet [16], which provides tools for rapidly scanning shared timelines; and Timewarp [4], which uses different points in the overall global timeline. This second contribution only addresses interleaving in the context of linear timelines, not divergent timelines.…”

Section: Introductionmentioning

confidence: 99%

A temporal model for multi-level undo and redo

Edwards

Igarashi

LaMarca

et al. 2000

Proceedings of the 13th Annual ACM Symposium on User Interface Software and Technology - UIST '00

View full text Add to dashboard Cite

divergent and convergent timelines as a way to support collaboration, and provides facilities for conflict resolution. Even in systems without such rich models of history, time is often an explicit-and directly manipulable-part of the user interface, and user experience. Systems such as TimeMachine Computing [15] and Lifestreams [6] are exemplars of this trend.All of these systems rely on an explicit model of history, which can be scanned to support search or "navigation" over a timeline, and all allow their timelines to be "traversed" to move the application's state to other points in its history. However, as powerful as these applications are, their timeline representations are for the most part exceedingly simple. They typically support only linear, not branching timelines (GINA and Timewarp are exceptions, however); the "nodes" in a timeline must represent atomic operations with side effects that are well understood at the time the application is created; and, typically, the timeline of the entire application must be navigated or traversed as a whole-it is impossible to have a portion of the timeline exist in a "bubble" that can be manipulated separately.While we don't commonly encounter such rich models of time in our day to day experience, they can be extremely useful nonetheless. Divergent timelines, for example, can be employed to allow users to interact with different but related versions of an artifact, and then reconcile those differences later. The ability to expand the representation of time in ways that better accommodate side effects can make applications easier to write. And being able to separate the history of one nested artifact from the history of the application as a whole can allow users to work locally on a document, project source code, et cetera, and still integrate their changes globally. This paper presents an expansion of the most traditional representation of timelines, which is based on the command object idiom. The research here makes two contributions. First it extends this traditional model of history to better support the causality effects often found in "real" applications. This first extension works for both linear and divergent timelines. Second, this new causal model is then extended to support multi-level or "interleaved" timelines, in which the various components of an artifact can exist at ABSTRACT A number of recent systems have provided rich facilities for manipulating the timelines of applications. Such timelines represent the history of an application's use in some session, and captures the effects of the user's interactions with that application. Applications can use timeline manipulation techniques prosaically as a way to provide undo and redo within an application context; more interestingly, they can use these same techniques to make an application's history directly manipulable in richer ways by users. This paper presents a number of extensions to current techniques for representing and managing application timelines. The first extension captures causal relations...

show abstract

Tools for supporting the collaborative process

Cited by 20 publications

References 16 publications

Supporting process undo and redo in software engineering decision making

Supporting process undo and redo in software engineering decision making

Where do web sites come from?

A temporal model for multi-level undo and redo

Contact Info

Product

Resources

About