Repeatedly-executed-method viewer for efficient visualization of execution paths and states in Java

Matsumura, Toshinori; Ishio, Takashi; Kashima, Yu; Inoue, Katsuro

doi:10.1145/2597008.2597803

Cited by 12 publications

(7 citation statements)

References 18 publications

(13 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It then performs trace summarization, as described in the previous section. To weave logging codes into the target system, our tool uses SELogger which is a part of REMViewer [35]. SELogger takes *.class files as its input, then performs byte-code processing to insert logging codes into the *.class files.…”

Section: Methodsmentioning

confidence: 99%

Identifying Core Objects for Trace Summarization by Analyzing Reference Relations and Dynamic Properties

Noda

Kobayashi

Atsumi

2018

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

Kunihiro NODA†a) , Nonmember, Takashi KOBAYASHI †b) , and Noritoshi ATSUMI † †c) , Members SUMMARY Behaviors of an object-oriented system can be visualized as reverse-engineered sequence diagrams from execution traces. This approach is a valuable tool for program comprehension tasks. However, owing to the massiveness of information contained in an execution trace, a reverse-engineered sequence diagram is often afflicted by a scalability issue. To address this issue, many trace summarization techniques have been proposed. Most of the previous techniques focused on reducing the vertical size of the diagram. To cope with the scalability issue, decreasing the horizontal size of the diagram is also very important. Nonetheless, few studies have addressed this point; thus, there is a lot of needs for further development of horizontal summarization techniques. We present in this paper a method for identifying core objects for trace summarization by analyzing reference relations and dynamic properties. Visualizing only interactions related to core objects, we can obtain a horizontally compactified reverseengineered sequence diagram that contains system's key behaviors. To identify core objects, first, we detect and eliminate temporary objects that are trivial for a system by analyzing reference relations and lifetimes of objects. Then, estimating the importance of each non-trivial object based on their dynamic properties, we identify highly important ones (i.e., core objects). We implemented our technique in our tool and evaluated it by using traces from various open-source software systems. The results showed that our technique was much more effective in terms of the horizontal reduction of a reverse-engineered sequence diagram, compared with the state-of-theart trace summarization technique. The horizontal compression ratio of our technique was 134.6 on average, whereas that of the state-of-the-art technique was 11.5. The runtime overhead imposed by our technique was 167.6% on average. This overhead is relatively small compared with recent scalable dynamic analysis techniques, which shows the practicality of our technique. Overall, our technique can achieve a significant reduction of the horizontal size of a reverse-engineered sequence diagram with a small overhead and is expected to be a valuable tool for program comprehension.

show abstract

Section: Methodsmentioning

confidence: 99%

Identifying Core Objects for Trace Summarization by Analyzing Reference Relations and Dynamic Properties

Noda

Kobayashi

Atsumi

2018

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

show abstract

“…If a method invokes the hook methods, the caller method is treated as a template method, and a meta pattern consisting of the template method and the invoked hook methods is detected (ll. [16][17][18][19][20][21][22][23][24][25][26].…”

Section: Meta Pattern Detectionmentioning

confidence: 99%

“…For the recursive patterns, if the template and hook methods have the same name, the template object is inserted into the resulting group (ll. [23][24]. The function calleeObj(e) returns the callee object of the specified entry event e. Then, callee objects in a chain of template/hook method calls are added into the resulting group; that is, if all the invoked methods in the call stack cs are the template/hook methods, all the callee objects are added into the resulting group (ll.…”

Section: Overall Algorithm Of Object Groupingmentioning

confidence: 99%

See 1 more Smart Citation

Constructing Object Groups Corresponding to Concepts for Recovery of a Summarized Sequence Diagram

Noda

Kobayashi

Agusa

2021

Journal of Information Processing

View full text Add to dashboard Cite

Comprehending the behavior of an object-oriented system solely from its source code is troublesome owing to its dynamism. To aid comprehension, visualizing program behavior through reverse-engineered sequence diagrams from execution traces is a promising approach. However, because of the massiveness of traces, recovered diagrams tend to become very large causing scalability issues. To address these issues, we propose an object grouping technique that horizontally summarizes a reverse-engineered sequence diagram. Our technique constructs object groups based on Pree's meta patterns in which each group corresponds to a concept in the domain of a subject system. By visualizing interactions only among important groups, we generate a summarized sequence diagram depicting a behavioral overview of the system. Our experiment showed that our technique outperformed the state-of-the-art trace summarization technique in terms of reducing the horizontal size of reverse-engineered sequence diagrams. Regarding the quality of object grouping, our technique achieved an F-score of 0.670 and a Recall of 0.793 on average under the condition of #lifelines (i.e., the horizontal size of a sequence diagram) < 30, whereas those of the state-of-the-art technique were 0.421 and 0.670, respectively. The runtime overhead imposed by our technique was 129.2% on average, which is relatively smaller than other figures found in the reference literature.

show abstract

“…The function calleeObj(e) returns the callee object of the specified entry event e. Then, callee objects in a chain of template/hook method calls are added into the resulting group; that is, if all the invoked methods in the call stack cs are the template/hook methods, all the callee objects are added into the resulting group (ll. [21][22][23][24][25][26][27][28][29][30][31][32]. Note that some code fragments in the template/hook methods might be extracted as private-methods whose names are different from those of the template/hook methods.…”

Section: Overall Algorithm Of Object Groupingmentioning

confidence: 99%

Constructing Object Groups Corresponding to Concepts for Recovery of a Summarized Sequence Diagram

Noda,

Kobayashi,

Agusa

2020

Preprint

View full text Add to dashboard Cite

Comprehending the behavior of an object-oriented system solely from its source code is troublesome, owing to its dynamism. To aid comprehension, visualizing program behavior through reverse-engineered sequence diagrams from execution traces is a promising approach. However, because of the massiveness of traces, recovered diagrams tend to become very large, causing scalability issues. To address the issues, we propose an object grouping technique that horizontally summarizes a reverse-engineered sequence diagram. Our technique constructs object groups based on Pree's meta patterns, in which each group corresponds to a concept in the domain of a subject system. Visualizing interactions only among important groups, we generate a summarized sequence diagram depicting a behavioral overview of the system. Our experiment showed that our technique outperformed the state-of-the-art trace summarization technique in terms of reducing the horizontal size of reverse-engineered sequence diagrams. Regarding the quality of object grouping, our technique achieved an F-score of 0.670 and a Recall of 0.793 on average under the condition of #lifelines (i.e., the horizontal size of a sequence diagram) < 30, whereas those of the state-of-the-art technique were 0.421 and 0.670, respectively. The runtime overhead imposed by our technique was 129.2 % on average, which is relatively smaller in the literature.

show abstract

Repeatedly-executed-method viewer for efficient visualization of execution paths and states in Java

Cited by 12 publications

References 18 publications

Identifying Core Objects for Trace Summarization by Analyzing Reference Relations and Dynamic Properties

Identifying Core Objects for Trace Summarization by Analyzing Reference Relations and Dynamic Properties

Constructing Object Groups Corresponding to Concepts for Recovery of a Summarized Sequence Diagram

Constructing Object Groups Corresponding to Concepts for Recovery of a Summarized Sequence Diagram

Contact Info

Product

Resources

About