Skip to main navigation Skip to search Skip to main content

Methodology and architecture of JIVE

  • SUNY Buffalo

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

58 Scopus citations

Abstract

A novel approach to the runtime visualization and analysis of object-oriented programs is presented and illustrated through a prototype system called JIVE: Java /nteractive Visualization Environment. The main contributions of JIVE are: multiple concurrent representations of program state and execution history; support for forward and reverse execution; and graphical queries over program execution. This model facilitates program understanding and interactive debugging. Our visualization of runtime states clarifies the important point that objects are environments of execution. The history of object interaction is displayed via sequence diagrams, and in this way we help close the loop between design-time and run-time representations. Interactive execution is made possible by maintaining a runtime history database, which may be queried for information on variable behavior, method executions, and object interactions. We illustrate the capabilities of this system through examples. JIVE is implemented using the Java Platform Debugger Architecture and supports the Java language and libraries, including multithreaded and GUI applications.

Original languageEnglish
Title of host publicationProceedings SoftVis '05 - ACM Symposium on Software Visualization
EditorsS.N. Spencer
Pages95-104
Number of pages10
DOIs
StatePublished - 2005
EventSoftVis '05 - ACM Symposium on Software Visualization - St. Louis, MO, United States
Duration: May 14 2005May 15 2005

Publication series

NameProceedings SoftVis '05 - ACM Symposium on Software Visualization

Conference

ConferenceSoftVis '05 - ACM Symposium on Software Visualization
Country/TerritoryUnited States
CitySt. Louis, MO
Period05/14/0505/15/05

Fingerprint

Dive into the research topics of 'Methodology and architecture of JIVE'. Together they form a unique fingerprint.

Cite this