Software by Night
Wednesday, April 21st, 2010
In this post I’ll present an idea from unpublished work that uses light effects to visualize dynamic information in Software Cartography. (If you are unfamiliar with spatial-representation of software please refer to “A Software cartographer’s Vision” previously featured on this blog.)
“Software is not just structural, but behavioral; so the next thing I would like to see is traffic and people walking.” — Rob Deline, in the question session of Frank Steinbrückner’s presentation at MSA 2010
Software visualizations typically convey a static view of software systems. Software maps are no different. On a software map all code of a system is shown—no matter whether it is used at runtime or dead code. This is just the same as with Earth when seen from space: at day you see all land masses but only at night it is revealed where human activity takes place and where not. So my idea is to realize the same for software maps.
- use static information to group the software artifacts into structural clusters, visualized as land masses.
- use dynamic information to embellish the visualization with behavior activity, visualized as sources of lights.
Light effects, such as flares and glow, make the execution of software visible. What we actually do is to add more dimensions to a two-dimensional visualization, just as Michele Lanza did with his seminal polymetric views. There seem to be three promising dimensions for light effects
- brightness of light source,
- blurriness of surrounding glow,
- intensity of flares that flash up,
that are possibly best used in combination to visualize one or two behavioral properties.
When modelling animated visualization the notion of change is essential. Ben Fry’s work on organic visualization is a good source of inspiration to model time-dependent values, In his work he proposed intergrators as a new numerical data-type with first-class support for continuously changing values (as eg ease-in and ease-out).
Other than static numericals, integrators continuously change their value over time. Integrator values are in the continuous rather than discrete domain, they grow and decay rather than increment and decrement.
Fry associates each visual component with a set of set of static and changing values, using the data-types Numerical and Integrator. He describes an integrator as “a continuously changing value” and defines the following operations on integrators:
set()explicitly set the current value of the Integrator. Normally, this is only used to set an initial value for the Integrator.impulse()adds a specified amount of force to the Integrator. Equivalent to
incrementing a Numeric value, but executed in the continuous domain,
i.e. the amount added attenuates over time.decay()the opposite of an impulse. This is a decrease in the continuous domain. Often used to atrophy values over time.attract()apply a force to move the Integrator towards a particular value. Instead of setting the Integrator to a particular value, a target value is set for the Integrator that it will reach over time. Enables smooth
transitions if the target is changing.repel()the opposite of attract, moves the value of the Integrator away from a particular numeric value. If the value being avoided is greater, the
Integrator is decreased further. If less, the Integrator is increased.update()this is used internally to update the Integrator’s current value on each time step, after calculating a new velocity based on the forces
that have been applied to the Integrator by the rules that affect it.reset()after each the current value is updated, the forces are cleared. New forces are added on each time step by re-applying the rules.
To implement software by night integrators are best used in order to add light effects to the still view of a static software map. Currently we formalized two light dimensions, flare and glow. So when a software artifact is used then it flashes up with a sudden impuls to attract the users attention and then decays in a slowly disappearing glow. Calls are visualized by sparks that jump from call-site to call-site. So users can se where current action is taking place, but also where past action has been taking place and how often it has been doing so.
Please note that “Software at Night” is not yet available in the downloadable Codemap plug-in. I am working on an external prototype for an upcoming publication, thought. The missing integration in Eclipse is mainly due to the lack of an easy accessible source of dynamic information within Eclipse.
To learn about new Codemap releases, follow http://twitter.com/codemap
Happy Hacking!
