Software Visualization

1
Software Visualization

• CS 7450 - Information Visualization
• April 2, 2002
• John Stasko

2
Software Visualization

• Definition

The use of the crafts of typography, graphic
design, animation, and cinematography with modern
human- computer interaction and computer graphics
technology to facilitate both the human
understanding and effective use of computer
software.Price, Baecker and Small, 98
3
Challenge

• Software clearly is abstract data
• Unlike much information visualization, however,
  software is often dynamic, thus requiring our
  visualizations reflect the time dimension
• History views
• Animation
• ...

4
Subdomains

• Two main subareas of software visualization
• Program visualization - Use of visualization to
  help programmers, coders, developers. Software
  engineering focus
• Algorithm visualization - Use of visualization to
  help teach algorithms and data structures.
  Pedagogy focus

5
Subareas

• Program Visualization
• Software engineering
• Debugging
• Program analysis
• Systems

• Algorithm Visualization
• Pedagogy
• Systems
• Use in classroom
• Empirical study

6
Todays Talk

• This is a very big area, so talk will just give a
  flavor of the kinds of techniques and systems
  that have been created
• Lots of figures
• Some demos and videos

7
Program Visualization

• Can be as simple as enhanced views of program
  source
• Can be as complex as views of the execution of a
  highly parallel program, its data structures,
  run-time heap, etc.

8
Enhanced Code Views
Primarily used as a documentation aid
9
SeeSoft System

• Pulled-back, far away view of source code
• Map one line of source to one line of pixels
• Can indicate line indentation, etc.
• Like taping your source code to the wall, walking
  far away, then looking back at it

Eick, Steffen and Sumner IEEE ToSE92
10
System View
15,000 lines of code in 52 files
Video
11
Use

• Tracking (typically means mapping this data
  attribute to color)
• Code modification (when, by whom)
• Bug fixes
• Code coverage or hotspots
• Interactive, can change color mappings, can brush
  views, and so on

12
Tarantula

• New system that were working on here
• Utilizes SeeSoft code view methodology
• Takes results of test suite run and helps
  developer find program faults
• Clever color mapping is the key

Eagan, Harrold, Jones Stasko InfoVis 01
13
TarantulaView
Demo
14
Step Up

• Next step in program visualization is to help
  debugging and performance optimization by
  visualizing program executions
• Data, data structures, run-time heap, memory,
  control flow, data flow, hot spots, ...

15
Graph Visualization

• Area that weve already studied which is very
  important to SV
• Graphs pop up everywhere in software
• Common use Visualize a call graph, visualize a
  flow chart, ...

16
Sample CallGraph View
17
FIELD

• Program development and analysis environment with
  a wide assortment of different program views
• Integrated a variety of UNIX tools
• Utilized central message server architecture in
  which tools communicated through message passing

Reiss Software Pract Exp 90
18
FIELD Interface
19
Dynamic Call Graph View
On call stack
Currently active
20
Class Browser
21
Heap View
Color could be When allocated Block size Where
allocated
22
3D Call Graph
Selected file
Groups of calls
Collapsed file
23
PV System

• Used for understanding application and system
  behavior for purposes of debugging and tuning
• Users look for trends, anomalies, and
  correlations
• Ran on RISC/6000 workstations using AIX
• Trace-driven, can be viewed on-line or off

Kimelman, Rosenburg and Roth Visualization 94
24
Different Views

• Hardware-level performance info
• Instruction execution rates, cache utilization,
  processor utilization
• Operating system level activity
• Context switches, system calls, address space
  activity
• Communication library level activity
• Message passing, interprocessor communication
• Language run-time activity
• Dynamic memory allocation, parallel loop
  scheduling
• Application-level activity
• Data structure accesses, algorithm phase
  transitions

25
Accumulated process times
Call tree
Process run history
Kernel performance stats
26
Memory view
Code views
27
Utility

• Papers about PV provide a number of specific
  examples of how tool was used to help find and
  diagnose performance problems
• Authors say that one negative is just limitations
  of workstation display---need to open and align
  lots of windows and that becomes difficult

28
Commercial Systems

• A number of commercial program development
  environments have begun to incorporate program
  visualization tools such as these
• Majority are PC-based
• Has not become as wide-spread as I would have
  anticipated

29
Other Languages

• Can use program visualization techniques to
  depict software in other languages
• Functional Lisp
• Logical Prolog
• Object-oriented C

30
Concurrent Programs

• Understanding parallel programs is even more
  difficult than serial
• Visualization and animation seem naturals for
  illustrating concurrency
• Temporal mapping of program execution to
  animation becomes critical

Kraemer Stasko JPDC 93
31
POLKA

• We developed a system, POLKA, that was designed
  to help people build visualizations of concurrent
  programs
• Used for both program and algorithm visualization
• Used for different programming models message
  passing, shared memory threads, ...

Stasko Kraemer JPDC 93
32
Message Passing Systems
PVM/Conch
Topol, Stasko, Sunderam IJPDSN 98

33
Shared Memory Threads
Pthreads
Zhao Stasko TR 95
34
PVaniM

• Visualizing PVM programs on-line
• Must use sampling, not tracing due to sheer
  number of events
• Shows machine loads, host utilization, memory
  used, messages sent, communication patterns, etc.

Topol, Stasko Sunderam Concurr Pract Exper 98
35
PVaniM
Basic system UI
36
Algorithm Visualization

• Learning about algorithms is one of the most
  difficult things for computer science students
• Very abstract, complex, difficult to grasp
• Idea Can we make the data and operations of
  algorithms more concrete to help people
  understand them?

37
Algorithm Animation

• Common name for area
• Dynamic visualizations of the operations and data
  of computer algorithm as it executes
• Abstraction is key concept

38
Sorting Out Sorting

• Seminal work in area
• 30 minute video produced by Ron Baecker at
  Toronto in 1981
• Illustrates and compares nine sorting algorithms
  as they run on different data sets

39
SoS Views
Video
40
Balsa

• First main system in area
• Used in electronic classroom at Brown
• Introduced use of multiple views and interesting
  event model

Brown Computer 88
41
Example Animation
42
Tango

• Added smooth animation to algorithm animation
• Simplification of the design/programming process
  (easier programming model and framework)
• Formal model of the animation, the
  Path-Transition Paradigm

Stasko Computer 90
43
Tango
Multiple frames from bubblesort
44
POLKA

• Improved animation design model
• Object-oriented paradigm
• Multiple animation windows
• Much richer visualization/animation capabilities

Stasko Kraemer JPDC 93
45
POLKA
Demo
46
POLKA Model

• Location, AnimObject, Action
• Introduce explicit animation time (frame)

0 1 2 3 4 5 6 7 8 9
t
47
Semantic Zooming
Sorting 5000 elements
View all data
Zoom to first 10
Zoom further
48
Polka-3D

• 3-D and VR version of Polka
• Same animation model
• Use third dimension to
• Enhance visual aesthetics
• Portray 3-D data
• Encode more program attributes
• Not sure appropriate for algorithm animation

Stasko Wehrli VL 93
49
POLKA-3D
Quicksort side view Blue dots are as in 2-d
view Colored planes represent exhanges
50
Zeus

• Successor to Balsa
• Utilized sound and provided 3D version
• Provided visualizations of many computational
  geometry algorithms

Brown VL 91
51
Zeus Animations
Video
52
Evaluating Effectiveness

• Do algorithm animations actually help students
  learn?
• Thats the claim, but unproven
• Conducted a number of empirical studies to answer
  question
• Compare learning with animation to learning
  without
• Measuring understanding is difficult

53
Results

• Somewhat mixed, but some studies do show benefits
• - Potential for pedagogical aid is there, but
  just cant throw animation at algorithm and
  expect it to help
• Interaction is a key
• Blindly watching algorithm animation not really
  helpful
• Student must interact with animation and be
  engaged
• Animations help motivation, can make algorithm
  less intimidating

54
Current State of SV

• Research continues
• Some use of algorithm animations as pedagogical
  aids
• Program visualization trickling into commercial
  tools

55
Whats Needed? (PV)

• Better analysis of what software developers want
  and need
• Flexible displays providing overview and detail
• Improved tracing/monitoring/analysis capabilities

56
Whats Needed? (AA)

• Focus on interactive tools
• Simpler animation construction
• Empirical validation of value

57
Project Mid-way Reports

• Status
• Comments

58
References

• All referred to papers
• Software Visualization, MIT Press, 1998

59
Upcoming

• Evaluation
• Automating visualization design