Software Visualization


Enter Abstract Here


  • Page 3: "It is beyond human ability to assimilate the sheer volume of information in many software systems in its textual form."
  • Page 4: references B.A. Price, R.M. Baeker, I.S. Small. A Principled Taxonomy of Software Visualization. Journal of Visual Languages and Computing, 4(3):211-266 September 1993
  • Page 4: Mapping models of understanding: Initial mental model - (programmer's control) -> Static Model - (runtime control) -> Dynamic Model - (traditional and visualization tools) -> Programmer's Execution mental model <- correspondence searching -> Initial model…
  • Page 4: Important to map dynamic model to execution model: allows actions like debugging because the execution model and initial understanding can be super-imposed (see W. DePauw, et. al. "Modellng Objectd-Oriented Program Execution. ECOOP 1994)
  • Page 4: dynamic->execution mapping is through testing, RE, and possibly visualizations
  • Idea: if debugging is supported visually and top-down, can it aid in the dynamic->execution mapping?
  • Page 5: Pictorial information augments traditional methods-does not replace them.
  • Page 7: Mentions XPVM for visualizing traces of Parallel Virtual Machine Programs. See J.A. Kohl G.A. Geist. The PVM 3.4 Tracing Facility and XPVM 1.1. Hawaii International Conference on System Sciences. Traces are visualized in real-time.
  • Page 11-12: Several purposes for visualization including Understanding, Debugging, and Performance. Personal note: Debuggers can be used for understanding as well
  • Page 12-23: Ideals: Scalability, Extendibility, Portability; Minimal disturbance to end-program, Little or no Programmer Intervention, Real-world problems, Present the "Right Things" (most important aspects of the program—multiple views, allow the user to discover details)
  • Look up GraphTrace and Ovation
  • Page 18-22: Provides a taxonomy of software visualization based on hardware (single vs. multiple processor computation), and software (based on ideas of system software and language paradigms). The taxonomy, honestly, doesn't look useful.
  • Page 35: Language independence is important. The authors' solution is to use a custom markup language to annotate programs. Seems a little heavy-weight.
  • Page 46-56: Introduces VCC (visual C) which animates debugging sessions using call trees, and statistical charts for data (such as graphs and histograms). Users can set a time for each frame of animation, or add breakpoints.

BibTeX Reference

@book {
title="Software Visualization"
author="Eades, Peter, Zhang, Kang"
publisher="World Scientific Publishing Co. Pte. Ltd"
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License