Extracting Sequence Diagram from Execution Trace of Java Program

Taniguchi, Kenichi; Ishio, Takashi; Kamiya, T.; Kusumoto, Shoichi; Inoue, Katsuro

doi:10.1109/iwpse.2005.19

Cited by 33 publications

(42 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some approaches are expected to be effective in this challenge, for example using the method for compressing a sequence diagram [6] together, introducing interactive representation of a sequence diagram like [15], and improving and refining our slicing algorithm by introducing new dependencies. Moreover, filtering out useless and unwanted information before tracing like [21] is also expected to be effective in improving the readability of the diagram and time-efficient analysis.…”

Section: Discussionmentioning

confidence: 99%

“…Taniguchi et al propose a method of compressing a sequence diagram and improving its readability [6]. If repetitions and recursive method calls exist in a program, same or similar method invocation patterns are expected to appear in a reverse-engineered sequence diagram.…”

Section: Related Workmentioning

confidence: 99%

“…Several methods and tools [6]- [9] have been proposed to provide sequence diagrams with easy-to-understand focused behavior by reducing the amount of execution information to be visualized. These methods visualize abstracted execution information by compressing control structure, or grouping and filtering visual elements.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Reticella: An Execution Trace Slicing and Visualization Tool Based on a Behavior Model

Noda

Kobayashi

Yamamoto

et al. 2012

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYProgram comprehension using dynamic information is one of key tasks of software maintenance. Software visualization with sequence diagrams is a promising technique to help developer comprehend the behavior of object-oriented systems effectively. There are many tools that can support automatic generation of a sequence diagram from execution traces. However it is still difficult to understand the behavior because the size of automatically generated sequence diagrams from the massive amounts of execution traces tends to be beyond developer's capacity. In this paper, we propose an execution trace slicing and visualization method. Our proposed method is capable of slice calculation based on a behavior model which can treat dependencies based on static and dynamic analysis and supports for various programs including exceptions and multi-threading. We also introduce our tool that perform our proposed slice calculation on the Eclipse platform. We show the applicability of our proposed method by applying the tool to two Java programs as case studies. As a result, we confirm effectiveness of our proposed method for understanding the behavior of object-oriented systems.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Reticella: An Execution Trace Slicing and Visualization Tool Based on a Behavior Model

Noda

Kobayashi

Yamamoto

et al. 2012

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

show abstract

“…Dynamic traces were defined for individual languages such as UML sequence diagrams [28], UML Activity Diagrams [29].…”

Section: Implementation Detailsmentioning

confidence: 99%

Back-annotation of Simulation Traces with Change-Driven Model Transformations

Hegedüs

Bergmann

Ráth

et al. 2010

2010 8th IEEE International Conference on Software Engineering and Formal Methods

View full text Add to dashboard Cite

Abstract-Model-driven analysis aims at detecting design flaws early in high-level design models by automatically deriving mathematical models. These analysis models are subsequently investigated by formal verification and validation (V&V) tools, which may retrieve traces violating a certain requirement. Back-annotation aims at mapping back the results of V&V tools to the design model in order to highlight the real source of the fault, to ease making necessary amendments.Here we propose a technique for the back-annotation of simulation traces based on change-driven model transformations. Simulation traces of analysis models will be persisted as a change model with high-level change commands representing macro steps of a trace. This trace is back-annotated to the design model using change-driven transformation rules, which bridge the conceptual differences between macro steps in the analysis and design traces. Our concepts will be demonstrated on the back-annotation problem for analyzing BPEL processes using a Petri net simulator.

show abstract

“…Because a centralized application runs on one single VM, these profiling tools can collect all the related profiles and scale to larger distributed applications. Finally, visualization tools [11], [18] are useful for understanding the runtime behavior of applications. They extract call graphs of distributed applications automatically, which helps to understand how its multiple components interact.…”

Section: Introductionmentioning

confidence: 99%

Improving Automatic Centralization by Version Separation

Ма

Artho²,

Satō

2014

IPSJ Online Transactions

View full text Add to dashboard Cite

With today's importance of distributed applications, their verification and analysis are still challenging. They involve large combinational states, interactive network communications between peers, and concurrency. Although there are some dynamic analysis tools for analyzing the runtime behavior of a single-process application, they do not provide methods to analyze distributed applications as a whole, where multiple processes run simultaneously. Centralization is a general solution which transforms multi-process applications into a single-process one that can be directly analyzed by existing tools. In this paper, we improve the accuracy of centralization. Moreover, we extend it as a general framework for analyzing distributed applications with multiple versions. First, we formalize the version conflict problem and present a simple solution, and further propose an optimized solution to resolving class version conflicts during centralization. Our techniques enable sharing common code whenever possible while keeping the version space of each component application separate. Centralization issues like startup semantics and static field transformation are improved and discussed. We implement and apply our centralization tool to some network benchmarks. Experiments, where existing tools are used on the centralized application, prove the usefulness of our automatic centralization tool, showing that centralization enables these tools to analyze distributed applications with multiple versions.

show abstract

Extracting Sequence Diagram from Execution Trace of Java Program

Cited by 33 publications

References 2 publications

Reticella: An Execution Trace Slicing and Visualization Tool Based on a Behavior Model

Reticella: An Execution Trace Slicing and Visualization Tool Based on a Behavior Model

Back-annotation of Simulation Traces with Change-Driven Model Transformations

Improving Automatic Centralization by Version Separation

Contact Info

Product

Resources

About