Space-Filling Software Visualization by Marla J. Baker and Stephen G. Eick Presented by: Brian Phillips February

SeeSys System Background AT&T Bell Labortories AT&T Bell Labortories Large Scale Software Applications/Projects Large Scale Software Applications/Projects Really Implements Treemaps Really Implements Treemaps

Introduction A way to visualize a large scale software application and its sub-parts for statistical research A way to visualize a large scale software application and its sub-parts for statistical research - WOW BACK UP!!!!

Favorite Sentence “This technique can display the relative sizes of the location of new functionality, and the location of error-prone code with many bug fixes.”

Demonstration An Example An Example Makes No Sense yet Makes No Sense yet

Bottom Line Large Software Projects Many Sub Parts/Systems Many Files Many Programmers Why? = Analysis

Metrics for Measurement Errors in code Errors in code System Evolution System Evolution Recurrence of Errors Recurrence of Errors

An Example: Assume: Assume: We Create: We Create: New Release New Release A Database: A Database: - Contains certain Metrics

What we want to know? 1. L argest? Activity? 2. S tructure? – allocation 3. E rrors? – location 4. W here we focus effort? 5. G rowth Rate?

USER INTERACTION? Mouse Mouse

Legacies of the Project 1. Color 2. Spatial Utilization 3. Zoom in and Zoom out capabilities

Resources References mostly stuff about graphs and visualization References mostly stuff about graphs and visualization Lots of IEEE Articles Lots of IEEE Articles

Critiques - Strengths Addresses the heart of the issue Doesn’t try to conquer too much Makes Project Management very easy Don’t need to know much about a project

Critiques - Weaknesses Speaks about only one system Speaks about only one system No under the hood details No under the hood details Questions about the implementation Questions about the implementation