Compact visualization of Java program execution

Abstract

Summary The context of this work is a practical, open‐source visualization system, called JIVE, that supports two forms of runtime visualizations of Java programs – object diagrams and sequence diagrams. They capture, respectively, the current execution state and execution history of a Java program. These diagrams are similar to those found in the UML for specifying design–time decisions. In our work, we construct these diagrams at execution time, thereby ensuring continuity of notation from design to execution. In so doing, a few extensions to the UML notation are proposed in order to better represent runtime behavior. As sequence diagrams can become long and unwieldy, we present techniques for their compact representation. A key result in this paper is a novel labeling scheme based upon regular expressions to compactly represent long sequences and an O(r2) algorithm for computing these labels, where r is the length of the input sequence, based upon the concept of ‘tandem repeats’ in a sequence. Horizontal compaction greatly helps minimize the extent of white space in sequence diagrams by the elimination of object lifelines and also by grouping lifelines together. We propose a novel extension to the sequence diagram to deal with out‐of‐model calls when the lifelines of certain classes of objects are filtered out of the visualization, but method calls may occur between in‐model and out‐of‐model calls. The paper also presents compaction techniques for multi‐threaded Java execution with different forms of synchronization. Finally, we present experimental results from compacting the runtime visualizations of a variety of Java programs and execution trace sizes in order to demonstrate the practicality and efficacy of our techniques. Copyright © 2016 John Wiley & Sons, Ltd.

DyeVC: an approach for monitoring and visualizing distributed repositories

“…Program analysis and software visualization communities have already proposed trace reduction methods (Kuhn and Greevy 2006;Cornelissen et al 2008;Noda et al 2012;Jayaraman et al 2017). In (Kuhn and Greevy 2006) and (Cornelissen et al 2008), a trace Approaches allow visualizing only local commits.…”

“…Particularly, method call sequences are summarized in one method-call chain (Kuhn and Greevy 2006). Also, compact sequence diagram generation is studied in (Noda et al 2012) and (Jayaraman et al 2017). To have a better sequence diagram representation of the program execution, Noda's method (Noda et al 2012) abstracts the history of object interaction by grouping strongly correlated objects.…”

“…These objects are compacted, achieving an appropriate reduction in the number of objects appearing in the sequence diagram, which results in compression of this diagram along the horizontal axis. Also, (Jayaraman et al 2017) presents vertical and horizontal sequence diagram compaction techniques. For this end, one-to-one correspondence between call trees and sequence diagrams is used.…”

Making Sense of Actor Behaviour

“…Other approaches to sense-making include the interrogation of system traces and source-level debuggers. The visualization of Java execution traces in terms of object diagrams and sequence diagrams is proposed as a means for sense-making in [20]. Our approach provides a structured framework for defining many types of diagram including object and sequence.…”

Pewss: A platform of extensible workflow simulation service for workflow scheduling research

“…Visualization has been demonstrated effective in many research areas for helping the analysis of system behavior or experimental results, eg, visualizing Java program execution behavior. 29 It could be also very helpful for workflow scheduling research. Therefore, both WorkflowSim 14 and CloudWorkflowSimulator 15 provide several visualization functions for workflow execution schedule.…”