InfoVis:Wiki - User contributions [en]

Prefuse

2011-10-16T03:51:06Z

Mahfujalubna:

= Summary =

'''Author''': Jeffrey Heer / UC Berkeley 
'''Project Webpage''': http://prefuse.org 
'''Current Version''': beta, 21 October 2007 
'''Requirements''': Java 1.4 
'''Overview:''' using Java2D graphics library; pipeline architecture; animation and rendering support 
'''Base data structures''': Table, Graph, Tree 
'''Included visualization techniques (''[http://prefuse.org/gallery/ prefuse gallery]''):''' [http://prefuse.org/gallery/fisheyemenu/ Fisheye Menu], [http://prefuse.org/gallery/radialgraphview/ Radial Graph], [http://prefuse.org/gallery/treemap/ Treemap], [http://prefuse.org/gallery/congress/ Scatterplot], [http://prefuse.org/gallery/zipdecode/ zipdecode], [http://prefuse.org/gallery/treeview/ DOITree], [http://prefuse.org/gallery/graphview/ Graph View], [http://prefuse.org/gallery/datamountain/ Data Mountain] 
'''Supported File Formats''': GraphML (XML), TreeML (XML), Tab-delimited Text, CSV 

'''prefuse''' is an interactive graphical open source toolkit written in Java. It is thought to support the development of sophisticated, highly interactive, and flexible [[Information Visualization]]s. The architecture of '''prefuse''' considers the [[Visualization Pipeline]], a recommendation on how to implement a visualization. To provide flexibility, a [[polylithic design]] was chosen which enables developers to implement only needed functionality and customize these to meet the own requirements. But, in contrast to a [[monolithic design]], this design needs more time to conceive and influences the architecture of the own application heavily (which is not a disadvantage as '''prefuse''' is very elaborate).

Typically, '''prefuse''' is designed to visualize interrelated information so it can be stored in a graph or tree structure, but, also not related data can be used which is stored within a data table. Even if the structure is hierarchical, the resulting tree or graph structure must not be considered in the proper graphical representation as layout algorithms are not restricted in any way. The painting of visual items is done by using a renderer which has access to the respective item itself and the Graphics2D context of the view. This approach enables to use the whole range of available painting methods of Java, therefore, all painting issues are completely independent of the toolkit itself.

Besides providing a large set of predefined elements to visualize data, most attention was set toward usability of the visualization. This is obtained by applying several interaction techniques like tooltips or dragging visual elements. But also more sophisticated techniques like [[zoom]]ing, [[pan]]ning, or [[semantic zoom]]ing are supported or partially even provided by the toolkit itself. Further, '''prefuse''' clearly distinguishes between absolute and view coordinates. This separation helps users to place all visual elements in a logical way without consideration of later applied visualization techniques that changes the entire view.

=== Pros ===

* flexible
* versatile pipeline approach
* clear and well thought architecture
* many layout and distortion algorithms included
* algorithms for force-based physics simulation included
* custom animations (smooth transitions)
* color maps
* query language to navigate within abstract data
* demos and examples included
* bounding management
* open source
* documentation of code and general guidance available
* active developer community
* [http://www.diamondlinks.net/link building]

=== Cons ===

* [[polylithic design]] takes up more time to conceive and see first results
* special requirements of a visualization enforce a lot of adapting work

=General Approach=

Going along with the step-wise recommendation of the [[Visualization Pipeline]], a '''prefuse''' application consists of different states of data:

[[Image:prefuse_visualization_pipeline.gif|600px]]

'''prefuse''' uses a centralized object called ''Visualization'' (former ''ItemRegistry'') which maintains and manages the whole visualization. This object has to fulfil several tasks. It stores the abstract data as well as visual analogous of these in two different tables. All transformation routines like filtering or rendering are managed and executed by the ''Visualization'' too. Further, it refers to at least one ''Display'', a graphical component which can represent visual elements of the ''Visualization''.

Transformation routines are defined as ''Actions'' which are combined in ''ActionLists''. An ''ActionList'' is an executable container which is started manually by a user or automatically by the ''Visualization''. Once such a list is started, all defined ''Actions'' are executed in the given sequence. Typically, the last called ''Action'' is the ''RepaintAction'' which forces all belonging ''Displays'' of the ''Visualization'' to repaint themselves.

The ''Display'' is the view of '''prefuse'''. It can be embedded in each Java Swing application. The main task of a ''Display'' is the painting of visual structures which are defined in the respective ''Visualization''. Whenever the ''Display'' performs a repaint, it requests all visual items and checks all bounds of them (bounding management). If an item is within the own area the respective rendering mechanism is called.

The ''Display'' also provides navigation techniques like [[zoom]]ing or [[pan]]ning which change the view. The view itself refers to a separate coordinate system. View coordinates are described through an affine transformation matrix. Any navigation technique applied to the view only concerns the view coordinate system. The most important functionalities to work with this coordinate system are already predefined. Typically, users just have to apply whished techniques without considering technical details like the view coordinate system.

Furthermore, a ''Display'' also maintains a set of ''ControlListener'' which are used to process user interactions (mouse or keyboard events). Whenever such an event occurs the respective listener is called. A listener already differs on where the event happened (e.g., blank area or a certain item). Further, a ''ControlListener'' may also start an ''ActionList'' again.

==Source Data==

Raw data is the base of the application. Typically, the source of raw data is a file, but also other sources like a database or web content are thinkable. However, '''prefuse''' provides several file readers for different formats (CSV, Tab-Delimitated, etc.) that can be transformed into a data table. Further, some readers also support the reading of SQL-Databases. If another source is needed, a reader can be written manually.

Once the raw data is read, it is transformed into abstract data and stored within a data table of the ''Visualization''.

==Data Table==

The data table which is used to store abstract data works with data types and a definition schema which maps relations between data-type and table. That means, each row contains a data record, and each column contains values for a named data field with a specific data-type. Each record of the table is referred as a ''Tuple''.

Furthermore, instead of the table, also a graph or tree may be used to store interrelated data. Instead of ''Tuples'', records are referred as ''Nodes'' which are connected to others with ''Edges''. Additionally, a tree has one defined root ''Node''.

Abstract data does not contain any visual information like assignment attributes or color settings. Instead, own visual analogous are created. Visual attributes of them are extracted out of the abstract data following a defined logic.

==Visual Abstraction==

Visual structures are created when filtering the data container which contains the abstract data. In case of a visualization that displays all items from the beginning on, the filtering routine must only executed once at initializing time. If the visual content changes dynamically, the filtering is executed on certain user interactions by calling a defined filtering ''ActionList''.

A visual structure is referred as ''VisualItem'' which may be distinguished as ''VisualNode'', ''VisualEdge'', or an aggregated item which consists of several other items. However, as a ''VisualItem'' is extended of the respective abstract entity, it has full access to all abstract information too.

The filtering routine which transforms the abstract data to visual analogues typically consists of following ''Actions'':

* '''Filter''': This ''Action'' is responsible to transform the abstract data of the backing table to visual analogues. If no special conditions are defined, the filter creates for each ''Tuple'' a visual instance and stores them in a second table. Additionally, a filter also performs a garbage collection and may set visibility attributes of the created items.
* '''Layout''': A layout takes care about placing the ''VisualItems''. Several common algorithms for graphs or trees are already predefined (e.g., ''ForceDirectedLayout'' or ''RadialTreeLayout'').
* '''Assignment''': Besides layouting, also other assignments may be performed during the filtering process. Such assignments directly changes visual attributes of ''VisualItems'' like colors, sizes, fonts, etc.

A visual structure may also contain a paint routine, but, as all painting jobs are initialized or performed by separated renderers, these issues may also be executed by the renderer itself or any other object.

==View==

Typically, the rendered visual structure is not stored, instead, they are re-rendered whenever needed.[http://www.gallbladderdetox.com/gall-bladder-symptoms/ gall bladder symptoms] However, in case of very complex but constant visual representations it makes sense to hold items in an offscreen image.

Each ''VisualItem'' has got one or more associated ''Renderers'' which are maintained by a factory of the ''Visualization''. A ''Renderer'' has to perform two tasks:

* Providing a bounding box of the item. This box is used to determine if the item must actually be painted or if it would not be visible anyway.
* Providing the painting routine of the item. Paintings may be executed by the ''Renderer'' itself or delegated to other objects which are accessible of the ''Renderer''. The painting routines are not restricted in any way, but the proper representation should not exceed the bounding box of the item.

Rendering is always performed on a repaint of the ''Display''. A repaint can be requested by the ''Visualization'', on user interaction, and on events like resizing the component, getting the focus, or changing the coordinate system of the view. However, as repaints may occur very often, developers have to ascertain that rendering jobs are performed fast, otherwise, the performance of the whole visualization would suffer.

{{Quotation|The central class is '''Visualization''', which has associated '''VisualTable''', '''Action''', '''Renderer''', and '''Display''' objects. '''VisualTable''' objects represent the visual structures to be rendered. They are backed up by data tables ('''Table''' objects) using the cascaded table pattern describes in [8]. '''VisualTable''' objects extend the data tables by additional columns for visual properties such as color, shape, size, position, etc. Each row of a '''VisualTable''' represents one '''VisualItem''' object. A '''VisualItem''' is rendered to one or more '''Display''' instances using an associated '''Renderer'''. '''Actions''' are used for data transformations (e.g. for filtering), visual mappings (e.g. for defining the color, size or shape), and for view transformations (e.g. zooming or animation). An important concept is the concept of visual groups. Groups are identifies for sets of '''VisualItems'''. '''Actions''' can be assigned for each such set. An example for an action is the layout of items. A '''Layout''' action computes the location of all items of a certain group in terms of (x,y)-coordinates. '''EncoderActions''' use a '''Predicate''' to restrict to certain items of a group, e.g. changing the foreground color only of items that are currently selected. Finally, '''Control'''objects handle user input, e.g. dragging of an item to a new location. '''Controls''' then usually invoke one or more Actions to perform the changes on the data.|[Giereth and Ertl, 2008]}}

=Details=

==Package Structure==

Following picture shows the most important packages of '''prefuse''' regarding to the [[Visualization Pipeline]]:

[[Image:prefuse_package_guide.gif|600px]]

These packages also contain predefined components. Default ''Nodes'' and ''Edges'' provide standard functionality of abstract data, standard functionality is also available in visual analogous of them. A default filter transforms all defined abstract entities to visual ones. Further, also some special functionalities to fulfil common requirements are provided by own components:

* '''Renderers''': ''EdgeRenderer'' to render edges between graph or tree nodes, a ''LableRenderer'' to render text items, and a ''PolygoneRenderer'' to render geometrical items.
* '''Layouts''': ''RandomLayout'', ''GridLayout'', and some more to place non related data, ''ForceDirectedLayout'', ''TreeLayout'', ''RadialTreeLayout'' and others to layout trees and graphs.
* '''Controls''': ''DragControl'', ''ZoomControl'', ''PanControl'', ''ToolTipControl'' and several others to react on user interactions.

In simple visualizations the predefined functionality will meet most requirements. If special requirements are needed the default functionality supports a step-wise developing as results can be communicated by predefined components until the own functionality is implemented.

==Coordinates in prefuse==

'''prefuse''' works with two different coordinate systems. Absolute coordinates are device-independent logical coordinates. All visual attributes like positions or sizes are defined in absolute coordinates. In contrast, view coordinates are device-depended (screen). Transformations between absolute and view coordinates are done automatically by Java painting routines. View coordinates are influenced by the system and device driver (e.g., the absolute point (0,0) is the topmost left point of the actual graphical component which may be on any position at the screen). Further, view coordinates may also be manipulated manually by using an affine transformation matrix which applies linear transformations on absolute coordinates before device-dependent routines convert them to screen coordinates.

A '''prefuse''' ''Display'' provides the most important manipulating methods of this matrix. [[Zoom]]ing, [[pan]]ning, and rotation of the whole view are only done by changing the view coordinates. So, as absolute coordinates are never concerned of such transformations and translations, a user must never consider the actual view in layout, assignment, or painting routines.

There are several different ways on how to apply such transformations, additionally, the ''Display'' also supports animated transformations.

==User Interactions==

Mouse or keyboard events are treated by ''ControlListener''. Whenever an event occurs which is handled by a ''ControlListener'', the ''Display'' delegates the event to the respective routine. A ''ControlListener'' disdinguishes automatically which visual element is concerned of the event (the view itself or a ''VisualItem'').

A ''ControlListener'' may just perform simple tasks like changing the mouse cursor or editing the label of an item. But, in more sophisticated applications, also tasks like loading new data or dragging items on the view may be handled. Therefore, a ''ControlListener'' may also start ''ActionLists'' to execute such tasks. Further, a ''ControlListener'' has also access to the ''Display''. Thus, it is able to call methods like zooming or panning. Typically, each ''ControlListener'' forces a repaint when its job is done.

Most of standard functionality is already predefined in ''prefuse'' and the wanted listeners just have to be assigned to the ''Display''. However, the ''Display'' can handle a countless of different listener. Hence, typically only a few listeners must be defined manually as they can be mixed with default ones.

=Conclusion=

'''prefuse''' is a very powerful toolkit, providing a large set of components and methods a developer needs to build an [[Information Visualization]]. The [[polylithic design]] is not that easy to understand in the beginning of a development, but [http://www.kidney-stones-symptoms-cure.com/ symptoms of kidney stones] once conceived, a visualization is easy to realize even if really special demands have to be fulfilled. Furthermore, using Prefuse forces a clear and well designed architecture of own applications.

'''prefuse''' was created with most attention paid to developers who will finally work with the toolkit. In an evaluation study this goal was approved too. In the meanwhile, there is also a not so small community using and upgrading the toolkit, which is an argument for its usability.

= External links =
*[http://prefuse.org prefuse Homepage]
*[http://www.kidney-stones-symptoms-cure.com/ symptoms of kidney stones]
*[http://www.gallbladderdetox.com/gall-bladder-symptoms/ gall bladder symptoms]
*[http://www.kidney-stones-symptoms-cure.com/ kidney stones symptoms]
*[http://vw.indiana.edu/ivsi2004/jherr/index.html prefuse Position Paper]
*[http://sourceforge.net/forum/forum.php?forum_id=343013 prefuse Help Forum]
*[http://goosebumps4all.net/34all/bb/forumdisplay.php?fid=18 Unofficial Help Forum]
*[http://www.cs.mun.ca/~hoeber/teaching/cs4767/notes/04-prefuse/ Prefuse Tutorial] by Orland Hoeber
*[http://ike.donau-uni.ac.at/~rind/w/doku.php/java/prefuse-scatterplot prefuse Scatter Plot Tutorial] by Alexander Rind
*[http://prefuse.blogspot.com/ Useful prefuse documentation on blogspot]

= Downloads =
*[[Media:Prefuse-tutorial-20061127-handout.pdf|prefuse Tutorial (pdf, 660kB)]] by [[Aigner, Wolfgang|Wolfgang Aigner]]

= References =
*[Giereth and Ertl, 2008] Giereth, M.; Ertl, T., [http://ieeexplore.ieee.org/iel5/4577907/4577908/04578006.pdf?isnumber=4577908∏=STD&arnumber=4578006&arnumber=4578006&arSt=569&ared=574&arAuthor=Giereth%2C+M.%3B+Ertl%2C+T. Design Patterns for Rapid Visualization Prototyping], Proc. of 12th International Conference on Information Visualisation 2008 (IV'08), pp.569-574, 9-11 July 2008.
*[Heer, 2004] Jeffrey Heer. [http://jheer.org/publications/2004-Heer-prefuse-Masters.pdf prefuse: a software framework for interactive information visualization]. Masters of Science, Computer Science Division, University of California, Berkeley, 2004.
*[Heer, 2005] Jeffrey Heer, Stuart K. Card, and James A. Landay. [http://jheer.org/publications/2005-prefuse-CHI.pdf prefuse: a toolkit for interactive information visualization.] In CHI 2005, Human Factors in Computing Systems, 2005.
*[Heer, 2006a] Jeffrey Heer, prefuse API documentation. Retrieved at: July 06, 2006, http://prefuse.org
*[Heer, 2006b] Jeffrey Heer, prefuse manual. Retrieved at: July 06, 2006, http://prefuse.org
*[Sun Microsystems, 2001] Sun Microsystems, Programmer’s Guide to the Java 2DTM API - Enhanced Graphics and Imaging for Java. Retrieved at: April 20, 2006, http://java.sun.com/j2se/1.4/pdf/j2d-book.pdf

[[Category:Toolkits]]

Information Visualization

2011-10-09T08:20:18Z

Mahfujalubna:

{{Definition|'''Information visualization ''(InfoVis)''''' produces (interactive) visual representations of [[abstract data]] to reinforce human cognition; thus enabling the viewer to gain knowledge about the internal structure of the data and causal relationships in it.}}

{{Definition|'''Information visualization ''(InfoVis)''''' is the communication of [[abstract data]] through the use of interactive visual interfaces. [Keim et al., 2006]}}

== Definitions ==

{{Quotation|Compact graphical presentation and user interface for
*manipulating large numbers of items
*possibly extracted from far larger datasets
Enables users to make
*discoveries,
*decisions, or
*explanations
*[http://www.gather.com/viewArticle.action?articleId=281474979624859 boils]
*[http://www.allgallbladdersymptoms.org/ Gallbladder disease]
about
*patterns (trend, cluster, gap, outlier...),
*groups of items, or
*individual items.|[Plaisant, 2001]}}

{{Quotation|The use of computer-supported, interactive, visual representations of [[abstract data]] to amplify [[cognition]].|[Card et al., 1999]}}

{{Quotation|Information visualization utilizes computer graphics and [[interaction]] to assist humans in solving problems.|[Purchase et al., 2008, p. 58]}}

{{Quotation|Information visualization is a set of technologies that use visual computing to amplify human [[cognition]] with abstract information.|[Card, 2008, p. 542]}}

{{Quotation|Information visualization promises to help us speed our understanding and action in a world of increasing information volumes.|[Card, 2008, p. 542]}}

{{Quotation|The purpose of information visualization is to amplify cognitive performance, not just to create interesting pictures. Information visualizations should do for the mind what automobiles do for the feet.|[Card, 2008, p. 539]}}

{{Quotation|Information visualizations attempt to efficiently map data variables onto visual dimensions in order to create graphic representations.|[Gee et al., 2005]}}

{{Quotation|Information visualization, an increasingly important subdiscipline within [[HCI (Human-Computer Interaction)|HCI]], focuses on graphical mechanisms designed to show the structure of information and improve the cost of access to large data repositories. In printed form, information visualization has included the display of numerical data (e.g., bar charts, plot charts, pie charts), combinatorial relations (e.g., drawings of graphs), and geographic data (e.g., encoded maps). Computer-based systems, such as the information visualizer and [[Dynamic query|dynamic queries]] have added interactivity and new visualization techniques (e.g., 3D, animation).|[Averbuch, 2004]}}

{{Quotation|Visual representations of the semantics, or meaning, of information. In contrast to [[Scientific Visualization|scientific visualization]], information visualization typically deals with nonnumeric, nonspatial, and high-dimensional data.|[Chen, 2005]}}

{{Quotation|A method of presenting data or information in non-traditional, interactive graphical forms. By using 2-D or 3-D color graphics and animation, these visualizations can show the structure of information, allow one to navigate through it, and modify it with graphical interactions.|[UIUC DLI, 1998]}}

{{Quotation|As a subject in computer science, information visualization is the use of interactive, sensory representations, typically visual, of abstract data to reinforce cognition. Information visualization is a complex research area. It builds on theory in [[information design]], computer graphics, human-computer interaction and cognitive science. Practical application of information visualization in computer programs involves selecting, transforming and representing abstract data in a form that facilitates human interaction for exploration and understanding. Important aspects of information visualization are the interactivity and dynamics of the visual representation. Strong techniques enable the user to modify the visualization in real-time, thus affording unparalleled perception of patterns and structural relations in the abstract data in question. 
Although much work in information visualization regards to visual forms, auditory and other sensory representations are also of concern.|[Wikipedia, 2005]}}
<center>''Read full article on [http://www.susanlimsurgery.com/news_trinity_college_trinitys_first_singaporean_and_youngest_fellow.html Dr Susan Lim] [http://www.diamondlinks.net link building service]

[http://www.thegallbladdersymptoms.org/ Symptoms of Gall Bladder Disease]
[http://wikinstructions.com/ online instructions]
[http://www.bedbugbitesguide.com/ Bed Bug Bites Blog]
[http://seoph2.cafe24.com/wordpress seo blog] [[wikipedia:Information visualization|Wikipedia]]''</center>

{{Quotation|The study of how to effectively present information visually. Much of the work in this field focuses on creating innovative graphical displays for complicated datasets, such as census results, scientific data, and databases. An example problem would be deciding how to display the pages on a website or the files on a hard disk. Visualization techniques include selective hiding of data, layering data, taking advantage of 3-dimensional space, using scaling techniques to provide more space for more important information (e.g. Fisheye views), and taking advantage of psychological principles of layout, such as proximity, alignment, and shared visual properties (e.g. color).|[Usability First, 2003]}}

{{Quotation|'''Information visualization''', sometimes called InfoVis, is a special kind of visualization. Visualization is a part of computer graphics, which is in turn a subset of computer science. Visualization is defined as follows [Card et al., 1998]: Visualization is the use of interactive visual representations of data to amplify cognition. This means that the data is transformed into an image, it is mapped to screen space. The image can be changed by users as they proceed working with it. This interaction is important as it allows for constant redefinition of goals when new insight into the data has been gained. Visualization makes use of what is called external [[cognition]] [Card et al., 1998]. External resources are used for thinking. People are relieved from having to imagine everything. Instead they can just look at an image. This is only possible because human vision has a very large bandwidth, the largest of all senses [Card et al., 1998]. Information visualization is visualization of [[abstract data]]. This is data that has no inherent mapping to space. Examples for abstract data are the results of a survey or a database of the staff of a company containing names, addresses, salary and other attributes. Information visualization should be seen in contrast to [[Scientific Visualization|scientific visualization]], which deals with physically-based data. This kind of data is defined in reference to space coordinates, which makes it relatively easy to visualize in an intuitive way. The space coordinates in the dataset are mapped to screen coordinates. Examples are geographic data and computer tomography data of a body. Visualization of abstract data is not straightforward. One has to find a good way to map data values to screen space. It makes a difference whether the data is structured or unstructured. Examples for structured data are networks, software, and algorithms. This kind of data does not play a role in this thesis, only unstructured data is used here. Unstructured data is a collection of records with a number of different criteria in each record. The records can be, for instance, the individual fish in a fish-catch. Of each fish the following criteria can be recorded: species, weight, sex, and different measurements of length [...]. The records are arranged in rows, the criteria make up the columns of a table. The records are also called observations. The criteria are sometimes called variables, and sometimes dimensions. [...]|[Voigt, 2002]}}

{{Quotation|involves abstract, nonspatial data|[Tory and Möller, 2004]}}

{{Quotation|In [[Information Visualization|information visualization]], the graphical models may represent [[Abstract data|abstract]] concepts and relationships that do not necessarily have a counterpart in the physical world, e.g., information describing user accesses to pages of an Internet portal or records describing selected properties of different car brands and models. Typically, each data unity describes multiple related attributes (usually more than four) that are not of a spatial or temporal nature. Although spatial and temporal attributes may occur, the data exists in an abstract (conceptual) data space.|[Ferreira and Levkowitz, 2003]}}

== Overview ==

Application of information visualization on the computer involves providing [http://www.url.vn/2.html/ thiet ke web] means to transform and represent data in a form that allows and encourages human interaction. Data can therefore be analyzed by [[exploratory data analysis|''exploration'']] rather than pure reasoning; users [http://www.vitaminddeficiencyonline.com/ Vitamin D] [http://www.seo.url.vn/2.html/ dich vu seo] can develop understanding for structures and connections in the data by observing the immediate effects their interaction has upon the visualization.

[[Image:zook_large.gif|right|thumb|250px|Information Visualization Example]][[Image:boom.gif|right|thumb|250px|Visualization of a directory structure using a botanical model]]

== Examples ==

Information visualization is applied in countless areas covering every industry [http://www.vietnamairlinestickets.com/2.html/ Vietnam Airlines] and all tasks where understanding of the intrinsic structure in data is crucial.

Some prominent examples are:
*Economical/financial analysis
*Representation of large hierarchies
*Medical training/assistance
*Engineering/Physics

== See also ==
*[[Visualization]]
*[[Scientific Visualization]]

== References ==

*[Averbuch, 2004] Michael Averbuch, ''As you Like It: Tailorable Information Visualization'', Database Visualization Research Group, Tufts University, 2004.
*[Card, 2008] Stuart Card, Information visualization, in A. Sears and J.A. Jacko (eds.), The Human-Computer Interaction Handbook: Fundamentals, Evolving Technologies, and Emerging Applications, Lawrence Erlbaum Assoc Inc, 2007.
*[Card et al., 1999] Card, S. and Mackinlay, J. and Shneiderman, B., Readings in Information Visualization: Using Vision to Think, Morgan Kaufmann Publishers, 1999.
*[Chen, 2005] Chen, C. [http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=31454&arnumber=1463074&count=14&index=3 Top 10 Unsolved Information Visualization Problems], IEEE Computer Graphics and Applications, 25(4):12-16, July-Aug. 2005.
* [Ferreira and Levkowitz, 2003] Maria Cristina Ferreira de Oliveira, Haim Levkowitz, [http://doi.ieeecomputersociety.org/10.1109/TVCG.2003.1207445 From Visual Data Exploration to Visual Data Mining: A Survey], IEEE Transactions on Visualization and Computer Graphics, vol. 9, no. 3, pp. 378-394, July-September, 2003.
*[Gee et al., 2005] Gee, A.G., Yu, M., and Grinstein, G.G., Dynamic and Interactive Dimensional Anchors for Spring-Based Visualizations. Technical Report, Computer Science, University of Massachussetts Lowell.
*[Keim et al., 2006] Keim, D.A.; Mansmann, F. and Schneidewind, J. and Ziegler, H., Challenges in Visual Data Analysis, Proceedings of Information Visualization (IV 2006), IEEE, p. 9-16, 2006.
*[Plaisant, 2001] Plaisant, C., Information Visualization - Lecture Notes, Created at: November 2001.
*[Purchase et al., 2008] Purchase, H. C., Andrienko, N., Jankun-Kelly, T. J., and Ward, M. 2008. Theoretical Foundations of Information Visualization. In information Visualization: Human-Centered Issues and Perspectives, A. Kerren, J. T. Stasko, J. Fekete, and C. North, Eds. Lecture Notes In Computer Science, vol. 4950. Springer-Verlag, Berlin, Heidelberg, 46-64. DOI= http://dx.doi.org/10.1007/978-3-540-70956-5_3
*[Tory and Möller, 2004] Melanie Tory and Torsten Möller, Human Factors in Visualization Research, ''IEEEE Transactions on Visualization and Computer Graphics'', 10(1):72-84, January/February 2004.
*[UIUC DLI, 1998] University of Illinois at Urbana-Champaign Digital Libraries Initiative, UIUC DLI Glossary. Created: November 23, 1998. http://dli.grainger.uiuc.edu/glossary.htm
*[Usability First, 2003] Usability First, Usability Glossary. Retrieved at: 2003. http://www.usabilityfirst.com/glossary/main.cgi?function=display_term&term_id=5
*[Voigt, 2002]: Robert Voigt, [http://www.vrvis.at/via/resources/DA-RVoigt/masterthesis.html An Extended Scatterplot Matrix and Case Studies in Information Visualization], Master's thesis, Hochschule Magdeburg-Stendal, 2002, [http://www.vrvis.at/vis/resources/DA-RVoigt/node4.html ''Classification and Definition of Terms'']
*[Wikipedia, 2005] Wikipedia, Information visualization. Retrieved at: July 19, 2005. http://en.wikipedia.org/wiki/Information_visualization

== External links ==

*http://www.math.yorku.ca/SCS/Gallery/ has a lot of (positive and negative) examples including historical milestones.
*[http://www.kidney-stones-symptoms-cure.com/ kidney stones symptoms]
*[http://www.gallbladderdetox.com/gall-bladder-symptoms/ gallbladder symptoms]
*[http://uvc-thanhlapcongty.com thanh lap cong ty]
*[http://uvc-thanhlapcongty.com thanh lap cty]
*[http://uvc-thanhlapcongty.com thành lập công ty]
*[http://uvc-thanhlapcongty.com/dang-ky-online/dang-ky-thanh-lap-doanh-nghiep.html thanh lap doanh nghiep]
*[http://uvc-thanhlapcongty.com/dang-ky-online/dang-ky-thanh-lap-doanh-nghiep.html thành lập doanh nghiệp]
*[http://uvc-thanhlapcongty.com/van-ban-phap-quy/dang-ky-kinh-doanh.html dang ky kinh doanh]
*[http://www.gallbladderdetox.com/gall-bladder-symptoms/ gallbladder disease symptoms]
*[http://uvc-thanhlapcongty.com/cung-cap-dich-vu/dich-vu-ke-toan.html dich vu ke toan]
*[http://uvc-thanhlapcongty.com/cung-cap-dich-vu/dich-vu-ke-toan.html dịch vụ kế toán]
*[http://uvc-thanhlapcongty.com/cung-cap-dich-vu/dai-ly-bao-cao-thue.html bao cao thue]
*[http://www.nhakhoavietgiao.com.vn/list2.php?cid=49 nha khoa]
*[http://namthaibinhduong.edu.vn tu van du hoc]

[[Category:Glossary]]