Loading...
Please wait, while we are loading the content...
JavaMod : An Integrated Java Model for Java Software Visualization
| Content Provider | Semantic Scholar |
|---|---|
| Author | Gallego-Carrillo, Micael Gortázar-Bellas, Francisco Velázquez-Iturbide, J. Ángel |
| Abstract | Given the practical importance and complexity of object-oriented programming, there are many software visualization systems (VSs) for these languages. These systems use different forms of visualization to assist in understanding object-oriented applications. In particular, some VSs are designed to visualize programs written in the Java programming language (and they are often implemented in such a language, too). Java is an attractive language for visualization developers, because it is a ”comfortable” language and it is simple to build visualizations in Java. In the particular case of Java VSs implemented in Java itself, there is an additional advantage: the Java Virtual Machine provides an interface to debug programs written in Java, namely JPDA (JPDA). This interface avoids the need of using external debuggers or of generating program traces. The former often involves obscure interfaces; the latter requires to introduce additional code within the target program in order to extract information at run-time. Our ultimate goal is to build a infrastructure adequate to the comprehensive, flexible and systematic design of Java visualizations. Many Java VSs have been developed using different Java program representations, for instance, Evolve (Wang, 2002) based on Step (Brown, 2003), Jeliot (Myller, 2004) based on a Java interpreter, and JIVE (Gestwicki and Jayaraman, 2002) based on JPDA. Our proposal provides an architecture to support three models of Java programs: source code, execution and trace. The final result is a set of APIs that allows working with a comprehensive model of any Java application in a uniform and homogeneous way. Note that we use the term ”model” as synonymous for representation; it is inherited from the software engineering community, where representing entities is named modeling. In the following sections, we briefly describe such an architecture. The second section outlines our three models: source code, execution and tracing. The third section sketches the construction of a debugger based on these models. The fourth section gives a comparison with VSs and tools. Finally, we summarize our future work. |
| File Format | PDF HTM / HTML |
| Alternate Webpage(s) | http://www.dcs.warwick.ac.uk/pvw04/p15.pdf |
| Language | English |
| Access Restriction | Open |
| Content Type | Text |
| Resource Type | Article |
