Visualization Design Patterns: Difference between revisions

From InfoVis:Wiki
Jump to navigation Jump to search
← Older editNewer edit →
http://www.buckprod.com
removed spam
Line 1: Line 1:
Elkhart-born and raised Ursulina is entirely hooked on <a href="http://www.howtofindipaddress.info">ヴィトン バッグ</a> winter sports, backgammon. Nearly all her stimulus is obtained from checking out new towns, cities for example to Kisumu, Kenya.
{| align="right" | __TOC__ |}
== Overview ==
For any design discipline, including Information and Scientific Visualization, there are design problems within the domain that tend to arise time and again. Although effective solutions may be known, they are not helpful unless that knowledge is coherently structured and communicated to colleagues. Without good structure, design knowledge may be disparate and disjointed, and relationships among solutions may not be apparent.  Without good communication, designers who are unaware of solutions may be forced to ‘reinvent the wheel’, wasting unnecessary effort on a problem that has already been solved by others. Some means of capturing and codifying solutions to Information Visualisation design problems [http://tdschool.co.uk/driving-schools-stevenage/ driving schools stevenage] would be useful for those engaged in practice. The Visualization Design Patterns described here have been proposed for this purpose.
 
== Foundational Patterns ==
 
These patterns are the building blocks of Visualizations. They are more "reference patterns" than true "design patterns". Visualization designers will assume they are a given component of visualization design. The patterns are included to provide a common technical lexicon, to build a ''lingua franca'' used throughout the language, to encourage communications between novices and experts, and to facilitate a discussion of pros and cons.
 
 
 
=== '''Visualization Architecture''' ===
* [[Patterns:Visualization|Visualization]]
 
 
=== '''Interaction Patterns''' ===
User intent-based categories of interaction techniques <ref>Yi, J. S., Kang, Y. A., Stasko, J., & Jacko, J. A. (2007). [ Toward a Deeper Understanding of the Role of Interaction in Information Visualization.] IEEE Transactions on <span class="plainlinks">[http://driveways-som.com/driving-lessons-ilford/  <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">driving lessons ilford</span>] Visualization and Computer Graphics (TVCG), 13(6). Presented in InfoVis 2007, Sacramento, California, October 28 - November 1, 1224-1231.  (see also [ Toward a Deeper Understanding of the Role of Interaction in Information Visualization (presentation)])</ref>
* Reconfigure: show me a different arrangement
* Encode: show me a different representation
* Filter: show me something conditionally
** [[Patterns:Filter|Filter]]
** [[Patterns:Dynamic Queries|Dynamic Queries]]
** [[Patterns:Context-maintained Filter|Context-maintained Filter]]
** [[Patterns:Reduction Filter|Reduction Filter]]
* Abstract/Elaborate: show me more or less detail
** [[Patterns:Overview|Overview]]
** [[Patterns:Details-on-demand| Details-on-demand]]
* Connect: show me related items
** [[Patterns:Brushing|Brushing]]
* Explore: show me something else
** [[Patterns:Navigation|Navigation]]
** [[Patterns:Navigation Box|Navigation Box]]
** [[Patterns:Spatial Navigation|Spatial Navigation]]
** [[Patterns:Click-n-Drag|Click-n-Drag]]
** [[Patterns:Teleportation|Teleportation]]
* Select: mark something as interesting
** [[Patterns:Single Direct Selection|Single Direct Selection]]
** [[Patterns:Multiple Direct Selection|Multiple Direct Selection]]
** [[Patterns:Bounding Box|Bounding Box]]
** [[Patterns:Single Direct Selection+Keyboard|Single Direct Selection+Keyboard]]
** [[Patterns:Bounding Box+Keyboard|Bounding Box+Keyboard]]
* Other
** [[Patterns:Direct Manipulation|Direct Manipulation]]
** [[Patterns:Smooth Transitions|Smooth Transitions]]
** [[Patterns:2D Navigational Model|2D Navigational Model]]
** [[Patterns:3D Navigational Model|3D Navigational Model]]
** [[Patterns:NAFS Model|NAFS Model]]
 
See also: [http://en.wikipedia.org/wiki/Interaction_design_pattern Interaction Design Patterns (wikipedia article)]
 
=== '''Display Rendering Patterns''' ===
 
* [[Patterns:Appropriate Visual Objects|Appropriate Visual Objects]]
* [[Patterns:Level of Detail|Level of Detail]]
* [[Patterns:2d Representation|2d Representation]]
 
* [[Patterns:3d Representation|3d Representation]]
* [[Patterns:Reference Context|Reference Context]]
* [[Patterns:Redundant Encoding|Redundant Encoding]]
* [[Patterns:Small Multiples|Small Multiples]]
* [[Patterns:Datatips|Datatips]]
* [[Patterns:Legends|Legends]]
* [[Patterns:Visual Separation|Visual Separation]]
* [[Patterns:Familiar Organizational Device|Familiar Organizational Device]]
* [[Patterns:Non-Familiar Organizational Device|Non-Familiar Organizational Device]]
 
== Programming Patterns ==
These are patterns related to the backend programming of visualization systems. They are organised according to the Model-View-Controller approach, though other organizational systems may also be appropriate.
 
Heer and Agrawala's paper ''Software Design Patterns for Information Visualization''<ref>see Heer, J. & Agrawala, M., 2006. [Software Design Patterns for Information Visualization]. IEEE TRANSACTIONS ON VISUALIZATION AND COMPUTER GRAPHICS, 12(5), p.853.</ref> provides a useful overview of software design patterns specific to infovis tasks.
 
 
 
=== Data Modelling and Management ===
* [[Patterns:Reference Model|Reference Model]]
* [[Patterns:Data Column|Data Column]]
* [[Patterns:Cascaded Table|Cascaded Table]]
* [[Patterns:Relational Graph|Relational Graph]]
* [[Patterns:Proxy Tuple|Proxy Tuple]]
* [[Patterns:Expression|Expression]]
=== View ===
* [[Patterns:Camera|Camera]]
* [[Patterns:Dynamic Query Binding|Dynamic Query Binding]]
 
=== Controller ===
* [[Patterns:Scheduler|Scheduler]]
* [[Patterns:Operator|Operator]]
* [[Renderer]]
* [[Production Rule]]
 
== Development Patterns ==
These patterns relate to the systems development lifecycle and to the activities involved in implementing and testing software.
=== Diagnosis ===
For techniques used during the design process to evaluate coding and design-time decisions.
=== Evaluation and Testing ===
Quality Assurance, Evaluation, and Usability testing methods to close the feedback loop during the development lifecycle.
 
== References ==
<div class="references-small"> <references/> </div>
 
[[Category:Patterns]]

Revision as of 18:27, 1 August 2013

Overview

For any design discipline, including Information and Scientific Visualization, there are design problems within the domain that tend to arise time and again. Although effective solutions may be known, they are not helpful unless that knowledge is coherently structured and communicated to colleagues. Without good structure, design knowledge may be disparate and disjointed, and relationships among solutions may not be apparent. Without good communication, designers who are unaware of solutions may be forced to ‘reinvent the wheel’, wasting unnecessary effort on a problem that has already been solved by others. Some means of capturing and codifying solutions to Information Visualisation design problems driving schools stevenage would be useful for those engaged in practice. The Visualization Design Patterns described here have been proposed for this purpose.

Foundational Patterns

These patterns are the building blocks of Visualizations. They are more "reference patterns" than true "design patterns". Visualization designers will assume they are a given component of visualization design. The patterns are included to provide a common technical lexicon, to build a lingua franca used throughout the language, to encourage communications between novices and experts, and to facilitate a discussion of pros and cons.


Visualization Architecture


Interaction Patterns

User intent-based categories of interaction techniques [1]

See also: Interaction Design Patterns (wikipedia article)

Display Rendering Patterns

Programming Patterns

These are patterns related to the backend programming of visualization systems. They are organised according to the Model-View-Controller approach, though other organizational systems may also be appropriate.

Heer and Agrawala's paper Software Design Patterns for Information Visualization[2] provides a useful overview of software design patterns specific to infovis tasks.


Data Modelling and Management

View

Controller

Development Patterns

These patterns relate to the systems development lifecycle and to the activities involved in implementing and testing software.

Diagnosis

For techniques used during the design process to evaluate coding and design-time decisions.

Evaluation and Testing

Quality Assurance, Evaluation, and Usability testing methods to close the feedback loop during the development lifecycle.

References

  1. ↑ Yi, J. S., Kang, Y. A., Stasko, J., & Jacko, J. A. (2007). [ Toward a Deeper Understanding of the Role of Interaction in Information Visualization.] IEEE Transactions on driving lessons ilford Visualization and Computer Graphics (TVCG), 13(6). Presented in InfoVis 2007, Sacramento, California, October 28 - November 1, 1224-1231. (see also [ Toward a Deeper Understanding of the Role of Interaction in Information Visualization (presentation)])
  2. ↑ see Heer, J. & Agrawala, M., 2006. [Software Design Patterns for Information Visualization]. IEEE TRANSACTIONS ON VISUALIZATION AND COMPUTER GRAPHICS, 12(5), p.853.
Retrieved from "https://infovis-wiki.net/w/index.php?title=Visualization_Design_Patterns&oldid=157061"