|
|
|
|
 |
|
Summer 2004, Volume 3, Number 2, Pages 65-79
|
|
|
|
|
Table of contents Previous Full text Next PDF
|
|
|
|
| Original Article |
|
| Design choices when architecting visualizations† |
|
| Diane Tang1, Chris Stolte2 and Robert Bosch3 |
|
1Google Inc., Mountain View, CA, U.S.A.
2Tableau Software, Seattle, CA, U.S.A.
3VMware, Palo Atto, CA, U.S.A.
|
Correspondence to: Diane Tang, Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, U.S.A. Tel: +1 650 623 5245; E-mail: diane@google.com |
†Portions reprinted, with permission from Tang et al.30 Ó 2003 IEEE.
|
|
|
| Abstract |
| In this paper, we focus on some of the key design decisions we faced during the process of architecting a visualization system and present some possible choices, with their associated advantages and disadvantages. We frame this discussion within the context of Rivet, our general visualization environment designed for rapidly prototyping interactive, exploratory visualization tools for analysis. As we designed increasingly sophisticated visualizations, we needed to refine Rivet in order to be able to create these richer displays for larger and more complex data sets. The design decisions we discuss in this paper include the internal data model, data access, semantic meta-data information the visualization can use to create effective visual encodings, the need for data transformations in a visualization tool, modular objects for flexibility, and the tradeoff between simplicity and expressiveness when providing methods for creating visualizations.
Information Visualization (2004) 3, 65-79. doi:10.1057/palgrave.ivs.9500067
Published online 22 April 2004 |
|
| Keywords |
| Information visualization design; infrastructure |
| Received 19 November 2003; revised 30 January 2004; accepted 20 February 2004; published online 22 April 2004 |
|
|
Table of contents Previous Full text Next PDF
|
|
|
|
|
