Term
| Information visualization |
|
Definition
| the use f interactive visual presentations of abstract data to amplify cognition |
|
|
Term
|
Definition
| linear data types are one dimentional; include text, dictionaries, alphabets |
|
|
Term
|
Definition
| Overview task, zoom task, filter task, details on demand task, relate task, history task, extract task, |
|
|
Term
|
Definition
| users gain an overview of entire collection |
|
|
Term
|
Definition
| users can zoom in on items of interest, important for applications with small display |
|
|
Term
|
Definition
| users can filter out uninteresting items |
|
|
Term
|
Definition
| users can select items or groups to get detaisl |
|
|
Term
|
Definition
| Users can relate items or groups within collection |
|
|
Term
|
Definition
| users can keep a history of actions to support undo, replay, and progressive refinement |
|
|
Term
|
Definition
| users can allow extraction of subcollections and of the query parameters |
|
|
Term
| Challenges for information visualization |
|
Definition
| Importing and cleaning data, combining visual representations with textual labels, finding related information, viewing large volumes of data, integrating data mining, integrating with analytical reasoning techniques, collaborating with others, achieving universal usability, evaluation |
|
|
Term
| Importing and cleaning data |
|
Definition
| deciding how to input data to achieve desired task is difficult and getting the data into the correct format can also be burdensome |
|
|
Term
| Combining visual representations with textual labels |
|
Definition
| labels should be visible without overwhelming the display or confusing users |
|
|
Term
| Finding related information |
|
Definition
| multiple sources of info are often needed to make meaningful judgements, |
|
|
Term
| Viewing large volumes of data |
|
Definition
| simply handling large values of data in dynamic visualization |
|
|
Term
|
Definition
| can provide useful information |
|
|
Term
| Integrating with analytical reasoning tecniques |
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
| real world objects. abstract data need to select xyz bindings |
|
|
Term
|
Definition
| map time to spatial dimension, often involves overlapping events |
|
|
Term
|
Definition
| Parallel coordinates, n variables represented n parallel axis |
|
|
Term
|
Definition
| parent child relationships, large number of children |
|
|
Term
|
Definition
| arbitrary directed graph, arbitrary size, typed linsk |
|
|
Term
|
Definition
| one hand, example using a mouse |
|
|
Term
|
Definition
| Two handed, Symmetric- in phase (jump rope) out of phase (rope climb). Asymmetric -musical instrument |
|
|
Term
| Visibility of system status |
|
Definition
| The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. |
|
|
Term
| Match between system and the real world |
|
Definition
| The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order. |
|
|
Term
|
Definition
| Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo. |
|
|
Term
| Consistency and standards |
|
Definition
| Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. |
|
|
Term
|
Definition
| Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action. |
|
|
Term
| Recognition rather than recall |
|
Definition
| Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. |
|
|
Term
| Flexibility and efficiency of use |
|
Definition
| Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. |
|
|
Term
| Aesthetic and minimalist design |
|
Definition
| Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility. |
|
|
Term
| Help users recognize, diagnose, and recover from errors |
|
Definition
| Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution. |
|
|
Term
|
Definition
| Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large. |
|
|
