The Goal: To develop visualizations for large data sets which help users explore for items of interest.
The Scenario: An important way in which computers can enhance our productivity in certain tasks is by presenting numeric data, as well as other kinds of information, in alternative forms which are easier for us, as people, to deal with. In scientific visualization the objective is to help users detect patterns in the data; in information visualization the goal is to help users understand the structure of the data. Because in real world applications the quantity of data can be so large that it becomes impossible to display the entire data structure on the screen all at once without losing detail, a successful visualization will embody techniques that (a) help users acquire an overall (global) picture of the data they are exploring, and at the same time (b) help them retain a (local) sense of context as they navigate through the data, so they always know where they are and how they got there. In this exercise, we will focus on two important special cases of the information visualization task:
What To Do: Can you come up with a pair of good techniques, one for visualizing hierarchical data and the other for visualizing linear data as described above, on today's conventional high end PCs? Divide up into small teams of 4-6 members each, and rearrange seating as necessary so as to facilitate interaction among team members. Feel free to discuss whatever you wish with me during the period, if your team encounters issues or problems you're unsure how to resolve. Towards the end of the session, I will call for volunteers from the various teams so we can compare the different designs we've come up with as a group. Finally, we will view a short video of some experimental designs implemented about a decade ago at Xerox Corporation's Palo Alto Research Center (PARC), to see how these professionals and seasoned researchers approached the same problem.
As usual, after the conclusion of the in-class part of the exercise your
team should summarize its designs and the lessons learned in a written
report which includes diagrams and illustrations as needed. Discuss what
you perceive to be the advantages of your designs, and also possible
problems. The report (one copy with all team member names listed) is due
ten days after the in-class phase of the exercise is completed.