InfoVis:Wiki - User contributions [en]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 4

2010-01-07T21:29:02Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

=Description of application area, data, user, task and target=

==Description of Application Area and Given Dataset==
-------------------------------------------------------------------

===Application Area and Dataset Analysis===

It is a matter of social visualization, more precisely a family tree visualization. The descendants of Lisa and Bart Simpson will be presented
in two family trees - one for Lisa and one for Bart. The visualization is a interactiv chart e.g. a click on a family member show you individually data about this person.

Following information will be display:

* sur- and first name
* relationships (blood relationship, related by marriage, parent-child relationship)
* date of birth/death
* life time of every family member
* gender
* important events (e.g. official announcement, prison stay, school days etc.)
* satisfaction of the family members

Description of Datasets

* The family tree is a hierarchical data structure presented in a graphical form. The starting node in our example is Lisa or Bart. These nodes are also called root nodes. The lower-level node is called ancestor. Sibling nodes share the same parent node. The edge demonstrate the realtionship among people.
* The sur- and first name is a nominal data type.
* The birthday and date of death are ordinal data types.
* The life time (age) is a discrete numerical data type.
* The gender is a nominl data type.
* The important events are nominal data types.
* The satisfaction of a family member is a discrete ordinal data type (e.g. scala between 1 - 4 for very low to very high)

===Target Group Analysis===

Generally is a family tree for people who may want to know more about their own family relationship. This visualization should be create from every family member.
The Simpsons familiy tree is for people who are interested in the animated television sitcom "The Simpsons".

===Purpose of Visualization===

The visualization must be clearly and structured. It should be possible for the viewer at the first view to distinguish the gender of the people, the relationship among people (parent - child)
and the blood realtionship vs. related by marriage. To get more information (e.g. birthday, day of death, school days etc.) about a familiy member, the user click on this person.
In the second frame will be detailed all further information.

==Concept==
----------------------------------------------------------------------

The family tree is a interactive visualization.

The family tree gives the onlooker an overview making it easy recognizing the relationship between the individuals.

[[Image:Bart_Stammbaum.jpg|500px|Barts Family Tree]]
[[Image:Lisa_Stammbaum.jpg|500px|Lisas Family Tree]]

Moving the mouse over a specific person gives the viewer detailed information about this person.

[[Image:Bart_Stammbaum_Detail.jpg|500px|Barts Family Tree Detail]]

The detail view contains multiple datasets related to the person’s curriculum vitae.

[[Image:Bart_Detail.jpg|500px|Detail View]]

By selecting multiple datasets (dataset = person) from the family tree, the viewer might switch to the compare view to oppose specific attributes (can be selected by the viewer).

[[Image:Compare.jpg|500px|Compare View]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 4

2010-01-07T21:22:04Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

=Description of application area, data, user, task and target=

==Description of Application Area and Given Dataset==
-------------------------------------------------------------------

===Application Area and Dataset Analysis===

It is a matter of social visualization, more precisely a family tree visualization. The descendants of Lisa and Bart Simpson will be presented
in two family trees - one for Lisa and one for Bart. The visualization is a interactiv chart e.g. a click on a family member show you individually data about this person.

Following information will be display:

* sur- and first name
* relationships (blood relationship, related by marriage, parent-child relationship)
* date of birth/death
* life time of every family member
* gender
* important events (e.g. official announcement, prison stay, school days etc.)
* satisfaction of the family members

Description of Datasets

* The family tree is a hierarchical data structure presented in a graphical form. The starting node in our example is Lisa or Bart. These nodes are also called root nodes. The lower-level node is called ancestor. Sibling nodes share the same parent node. The edge demonstrate the realtionship among people.
* The sur- and first name is a nominal data type.
* The birthday and date of death are ordinal data types.
* The life time (age) is a discrete numerical data type.
* The gender is a nominl data type.
* The important events are nominal data types.
* The satisfaction of a family member is a discrete ordinal data type (e.g. scala between 1 - 4 for very low to very high)

===Target Group Analysis===

Generally is a family tree for people who may want to know more about their own family relationship. This visualization should be create from every family member.
The Simpsons familiy tree is for people who are interested in the animated television sitcom "The Simpsons".

===Purpose of Visualization===

The visualization must be clearly and structured. It should be possible for the viewer at the first view to distinguish the gender of the people, the relationship among people (parent - child)
and the blood realtionship vs. related by marriage. To get more information (e.g. birthday, day of death, school days etc.) about a familiy member, the user click on this person.
In the second frame will be detailed all further information.

==Concept==
----------------------------------------------------------------------

The family tree is a interactive visualization.

The family tree gives the onlooker an overview making it easy recognizing the relationship between the individuals.
[[Image:Bart_Stammbaum.jpg|500px|Barts Family Tree]]
[[Image:Lisa_Stammbaum.jpg|500px|Lisas Family Tree]]

Moving the mouse over a specific person gives the viewer detailed information about this person.

[[Image:Bart_Stammbaum_Detail.jpg|500px|Barts Family Tree Detail]]

The detail view contains multiple datasets related to the person’s curriculum vitae.

[[Image:Bart_Detail.jpg|500px|Detail View]]

By selecting multiple datasets (dataset = person) from the family tree, the viewer might switch to the compare view to oppose specific attributes (can be selected by the viewer).
[[Image:Compare.jpg|500px|Compare View]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 4

2010-01-07T21:21:16Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

=Description of application area, data, user, task and target=

==Description of Application Area and Given Dataset==
-------------------------------------------------------------------

===Application Area and Dataset Analysis===

It is a matter of social visualization, more precisely a family tree visualization. The descendants of Lisa and Bart Simpson will be presented
in two family trees - one for Lisa and one for Bart. The visualization is a interactiv chart e.g. a click on a family member show you individually data about this person.

Following information will be display:

* sur- and first name
* relationships (blood relationship, related by marriage, parent-child relationship)
* date of birth/death
* life time of every family member
* gender
* important events (e.g. official announcement, prison stay, school days etc.)
* satisfaction of the family members

Description of Datasets

* The family tree is a hierarchical data structure presented in a graphical form. The starting node in our example is Lisa or Bart. These nodes are also called root nodes. The lower-level node is called ancestor. Sibling nodes share the same parent node. The edge demonstrate the realtionship among people.
* The sur- and first name is a nominal data type.
* The birthday and date of death are ordinal data types.
* The life time (age) is a discrete numerical data type.
* The gender is a nominl data type.
* The important events are nominal data types.
* The satisfaction of a family member is a discrete ordinal data type (e.g. scala between 1 - 4 for very low to very high)

===Target Group Analysis===

Generally is a family tree for people who may want to know more about their own family relationship. This visualization should be create from every family member.
The Simpsons familiy tree is for people who are interested in the animated television sitcom "The Simpsons".

===Purpose of Visualization===

The visualization must be clearly and structured. It should be possible for the viewer at the first view to distinguish the gender of the people, the relationship among people (parent - child)
and the blood realtionship vs. related by marriage. To get more information (e.g. birthday, day of death, school days etc.) about a familiy member, the user click on this person.
In the second frame will be detailed all further information.

==Concept==
----------------------------------------------------------------------

The family tree is a interactive visualization.

The family tree gives the onlooker an overview making it easy recognizing the relationship between the individuals.
[[Image:Bart_Stammbaum.jpg|500px|Barts Family Tree]]
[[Image:Lisa_Stammbaum.jpg|500px|Lisas Family Tree]]

Moving the mouse over a specific person gives the viewer detailed information about this person.
[[Image:Bart_Stammbaum_Detail.jpg|500px|Barts Family Tree Detail]]

The detail view contains multiple datasets related to the person’s curriculum vitae.
[[Image:Bart_Detail.jpg|500px|Detail View]]

By selecting multiple datasets (dataset = person) from the family tree, the viewer might switch to the compare view to oppose specific attributes (can be selected by the viewer).
[[Image:Compare.jpg|500px|Compare View]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 4

2010-01-07T21:20:12Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

=Description of application area, data, user, task and target=

==Description of Application Area and Given Dataset==
-------------------------------------------------------------------

===Application Area and Dataset Analysis===

It is a matter of social visualization, more precisely a family tree visualization. The descendants of Lisa and Bart Simpson will be presented
in two family trees - one for Lisa and one for Bart. The visualization is a interactiv chart e.g. a click on a family member show you individually data about this person.

Following information will be display:

* sur- and first name
* relationships (blood relationship, related by marriage, parent-child relationship)
* date of birth/death
* life time of every family member
* gender
* important events (e.g. official announcement, prison stay, school days etc.)
* satisfaction of the family members

Description of Datasets

* The family tree is a hierarchical data structure presented in a graphical form. The starting node in our example is Lisa or Bart. These nodes are also called root nodes. The lower-level node is called ancestor. Sibling nodes share the same parent node. The edge demonstrate the realtionship among people.
* The sur- and first name is a nominal data type.
* The birthday and date of death are ordinal data types.
* The life time (age) is a discrete numerical data type.
* The gender is a nominl data type.
* The important events are nominal data types.
* The satisfaction of a family member is a discrete ordinal data type (e.g. scala between 1 - 4 for very low to very high)

===Target Group Analysis===

Generally is a family tree for people who may want to know more about their own family relationship. This visualization should be create from every family member.
The Simpsons familiy tree is for people who are interested in the animated television sitcom "The Simpsons".

===Purpose of Visualization===

The visualization must be clearly and structured. It should be possible for the viewer at the first view to distinguish the gender of the people, the relationship among people (parent - child)
and the blood realtionship vs. related by marriage. To get more information (e.g. birthday, day of death, school days etc.) about a familiy member, the user click on this person.
In the second frame will be detailed all further information.

==Concept==
----------------------------------------------------------------------

The family tree is a interactive visualization.

The family tree gives the onlooker an overview making it easy recognizing the relationship between the individuals.
[[Image:Bart_Stammbaum.jpg|300px|Barts Family Tree]]
[[Image:Lisa_Stammbaum.jpg|300px|Lisas Family Tree]]

Moving the mouse over a specific person gives the viewer detailed information about this person.
[[Image:Bart_Stammbaum_Detail.jpg|300px|Barts Family Tree Detail]]

The detail view contains multiple datasets related to the person’s curriculum vitae.
[[Image:Bart_Detail.jpg|300px|Detail View]]

By selecting multiple datasets (dataset = person) from the family tree, the viewer might switch to the compare view to oppose specific attributes (can be selected by the viewer).
[[Image:Compare.jpg|300px|Compare View]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 4

2010-01-07T21:16:58Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

=Description of application area, data, user, task and target=

==Description of Application Area and Given Dataset==
-------------------------------------------------------------------

===Application Area and Dataset Analysis===

It is a matter of social visualization, more precisely a family tree visualization. The descendants of Lisa and Bart Simpson will be presented
in two family trees - one for Lisa and one for Bart. The visualization is a interactiv chart e.g. a click on a family member show you individually data about this person.

Following information will be display:

* sur- and first name
* relationships (blood relationship, related by marriage, parent-child relationship)
* date of birth/death
* life time of every family member
* gender
* important events (e.g. official announcement, prison stay, school days etc.)
* satisfaction of the family members

Description of Datasets

* The family tree is a hierarchical data structure presented in a graphical form. The starting node in our example is Lisa or Bart. These nodes are also called root nodes. The lower-level node is called ancestor. Sibling nodes share the same parent node. The edge demonstrate the realtionship among people.
* The sur- and first name is a nominal data type.
* The birthday and date of death are ordinal data types.
* The life time (age) is a discrete numerical data type.
* The gender is a nominl data type.
* The important events are nominal data types.
* The satisfaction of a family member is a discrete ordinal data type (e.g. scala between 1 - 4 for very low to very high)

===Target Group Analysis===

Generally is a family tree for people who may want to know more about their own family relationship. This visualization should be create from every family member.
The Simpsons familiy tree is for people who are interested in the animated television sitcom "The Simpsons".

===Purpose of Visualization===

The visualization must be clearly and structured. It should be possible for the viewer at the first view to distinguish the gender of the people, the relationship among people (parent - child)
and the blood realtionship vs. related by marriage. To get more information (e.g. birthday, day of death, school days etc.) about a familiy member, the user click on this person.
In the second frame will be detailed all further information.

==Concept==
----------------------------------------------------------------------

The family tree is a interactive visualization.

The family tree gives the onlooker an overview making it easy recognizing the relationship between the individuals.
[[Image:Bart_Stammbaum.jpg|700px|Barts Family Tree]]
[[Image:Lisa_Stammbaum.jpg|700px|Lisas Family Tree]]

Moving the mouse over a specific person gives the viewer detailed information about this person.
[[Image:Bart_Stammbaum_Detail.jpg|700px|Barts Family Tree Detail]]

The detail view contains multiple datasets related to the person’s curriculum vitae.
[[Image:Bart_Detail.jpg|700px|Detail View]]

By selecting multiple datasets (dataset = person) from the family tree, the viewer might switch to the compare view to oppose specific attributes (can be selected by the viewer).
[[Image:Compare.jpg|700px|Compare View]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05|Gruppe 05]]

File:Lisa Stammbaum.jpg

2010-01-07T20:55:28Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Compare.jpg

2010-01-07T20:55:06Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Bart Stammbaum Detail.jpg

2010-01-07T20:54:55Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Bart Stammbaum.jpg

2010-01-07T20:54:35Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Bart Detail.jpg

2010-01-07T20:54:02Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

User:UE-InfoVis0910 0402536

2009-12-20T16:29:44Z

UE-InfoVis0910 0402536:

Paizoni, Markus<br/>
[[image:Pic32373.jpg|Teufel|300px]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-03T21:02:37Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]
=== Zu verbessernde Grafik ===
------------------------------- <br> <br>
[[Image:geo2.jpg]]
===Kritik===
*Begründung unter Berücksichtigung der behandelten Designprinzipien (Data-Ink-Ratio, Visual Clutter, ...)

The given graph lacks of a few design principles. The first one is the background. It is non-data ink, because the visual information of world map is unnecessary for readers. The important information in this graph, the so called data ink, should be waste management of different countries.
The loupe attracts the attention of the reader. The data in this visual cue becomes more important than the outside data, which gives the outside data less visual weight, though the information outside the loupe is as important as the inside information. Cutting of the border around the legend could save unnecessary data ink.
The font used for labeling the four possibilities of waste disposal is also used for the data. This case makes the importance of the legend equal to the main data.
Another disadvantage in the original graph is the bars. It is hard for the reader to get the raw numbers or even to compare the data.

------------------------------- <br> <br>
=== Redesign ===
[[Image:uebung3_1.png|700px|Waste Disposal]]
===Vorgenommene Verbesserungen===
First we reduce the non-data ink, which means that we remove the background and the loupe. Second we estimate the percentages of each waste disposal type for every country. The results are four colored bars, which present the different opportunities of waste management for each country. We sorted the countries by name in a descending order.
These bars we drew in a table. The exactly percentages we organized in a second table positioned just under the main table. At least we modified the title. The new title is short and precise.
Our redesign of the given graph is clearly arranged and leads the reader´s eyes to what is important. The comparison of countries is quite simply. In the first table it is easy to estimate the percentages with the help of the horizontal lines and their labels. From the second table the reader is able to get the exact data.
We created a clear and powerful message with our redesigned graph.

------------------------------- <br> <br>

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-03T21:01:21Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]
=== Zu verbessernde Grafik ===
------------------------------- <br> <br>
[[Image:geo2.jpg]]
===Kritik===
*Begründung unter Berücksichtigung der behandelten Designprinzipien (Data-Ink-Ratio, Visual Clutter, ...)

The given graph lacks of a few design principles. The first one is the background. It is non-data ink, because the visual information of world map is unnecessary for readers. The important information in this graph, the so called data ink, should be waste management of different countries.
The loupe attracts the attention of the reader. The data in this visual cue becomes more important than the outside data, which gives the outside data less visual weight, though the information outside the loupe is as important as the inside information. Cutting of the border around the legend could save unnecessary data ink.
The font used for labeling the four possibilities of waste disposal is also used for the data. This case makes the importance of the legend equal to the main data.
Another disadvantage in the original graph is the bars. It is hard for the reader to get the raw numbers or even to compare the data.

------------------------------- <br> <br>
=== Redesign ===
[[Image:uebung3_1.png|500px|Waste Disposal]]
===Vorgenommene Verbesserungen===
First we reduce the non-data ink, which means that we remove the background and the loupe. Second we estimate the percentages of each waste disposal type for every country. The results are four colored bars, which present the different opportunities of waste management for each country. We sorted the countries by name in a descending order.
These bars we drew in a table. The exactly percentages we organized in a second table positioned just under the main table. At least we modified the title. The new title is short and precise.
Our redesign of the given graph is clearly arranged and leads the reader´s eyes to what is important. The comparison of countries is quite simply. In the first table it is easy to estimate the percentages with the help of the horizontal lines and their labels. From the second table the reader is able to get the exact data.
We created a clear and powerful message with our redesigned graph.

------------------------------- <br> <br>

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-03T21:00:35Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]
=== Zu verbessernde Grafik ===
------------------------------- <br> <br>
[[Image:geo2.jpg]]
===Kritik===
*Begründung unter Berücksichtigung der behandelten Designprinzipien (Data-Ink-Ratio, Visual Clutter, ...)

The given graph lacks of a few design principles. The first one is the background. It is non-data ink, because the visual information of world map is unnecessary for readers. The important information in this graph, the so called data ink, should be waste management of different countries.
The loupe attracts the attention of the reader. The data in this visual cue becomes more important than the outside data, which gives the outside data less visual weight, though the information outside the loupe is as important as the inside information. Cutting of the border around the legend could save unnecessary data ink.
The font used for labeling the four possibilities of waste disposal is also used for the data. This case makes the importance of the legend equal to the main data.
Another disadvantage in the original graph is the bars. It is hard for the reader to get the raw numbers or even to compare the data.

------------------------------- <br> <br>
=== Redesign ===
[[Image:uebung3_1.png|500px|thumb|Waste Disposal]]
===Vorgenommene Verbesserungen===
First we reduce the non-data ink, which means that we remove the background and the loupe. Second we estimate the percentages of each waste disposal type for every country. The results are four colored bars, which present the different opportunities of waste management for each country. We sorted the countries by name in a descending order.
These bars we drew in a table. The exactly percentages we organized in a second table positioned just under the main table. At least we modified the title. The new title is short and precise.
Our redesign of the given graph is clearly arranged and leads the reader´s eyes to what is important. The comparison of countries is quite simply. In the first table it is easy to estimate the percentages with the help of the horizontal lines and their labels. From the second table the reader is able to get the exact data.
We created a clear and powerful message with our redesigned graph.

------------------------------- <br> <br>

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-03T20:59:24Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]
=== Zu verbessernde Grafik ===
------------------------------- <br> <br>
[[Image:geo2.jpg]]
===Kritik===
*Begründung unter Berücksichtigung der behandelten Designprinzipien (Data-Ink-Ratio, Visual Clutter, ...)

The given graph lacks of a few design principles. The first one is the background. It is non-data ink, because the visual information of world map is unnecessary for readers. The important information in this graph, the so called data ink, should be waste management of different countries.
The loupe attracts the attention of the reader. The data in this visual cue becomes more important than the outside data, which gives the outside data less visual weight, though the information outside the loupe is as important as the inside information. Cutting of the border around the legend could save unnecessary data ink.
The font used for labeling the four possibilities of waste disposal is also used for the data. This case makes the importance of the legend equal to the main data.
Another disadvantage in the original graph is the bars. It is hard for the reader to get the raw numbers or even to compare the data.

------------------------------- <br> <br>
=== Redesign ===
[[Image:uebung3_1.png|150px|thumb|Waste Disposal]]
===Vorgenommene Verbesserungen===
First we reduce the non-data ink, which means that we remove the background and the loupe. Second we estimate the percentages of each waste disposal type for every country. The results are four colored bars, which present the different opportunities of waste management for each country. We sorted the countries by name in a descending order.
These bars we drew in a table. The exactly percentages we organized in a second table positioned just under the main table. At least we modified the title. The new title is short and precise.
Our redesign of the given graph is clearly arranged and leads the reader´s eyes to what is important. The comparison of countries is quite simply. In the first table it is easy to estimate the percentages with the help of the horizontal lines and their labels. From the second table the reader is able to get the exact data.
We created a clear and powerful message with our redesigned graph.

------------------------------- <br> <br>

File:Uebung3 1.png

2009-12-03T20:56:46Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-03T20:51:18Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]
=== Zu verbessernde Grafik ===
------------------------------- <br> <br>
[[Image:geo2.jpg]]
===Kritik===
*Begründung unter Berücksichtigung der behandelten Designprinzipien (Data-Ink-Ratio, Visual Clutter, ...)

The given graph lacks of a few design principles. The first one is the background. It is non-data ink, because the visual information of world map is unnecessary for readers. The important information in this graph, the so called data ink, should be waste management of different countries.
The loupe attracts the attention of the reader. The data in this visual cue becomes more important than the outside data, which gives the outside data less visual weight, though the information outside the loupe is as important as the inside information. Cutting of the border around the legend could save unnecessary data ink.
The font used for labeling the four possibilities of waste disposal is also used for the data. This case makes the importance of the legend equal to the main data.
Another disadvantage in the original graph is the bars. It is hard for the reader to get the raw numbers or even to compare the data.

------------------------------- <br> <br>
=== Redesign ===
[[Image:graph_01.png]]
===Vorgenommene Verbesserungen===
First we reduce the non-data ink, which means that we remove the background and the loupe. Second we estimate the percentages of each waste disposal type for every country. The results are four colored bars, which present the different opportunities of waste management for each country. We sorted the countries by name in a descending order.
These bars we drew in a table. The exactly percentages we organized in a second table positioned just under the main table. At least we modified the title. The new title is short and precise.
Our redesign of the given graph is clearly arranged and leads the reader´s eyes to what is important. The comparison of countries is quite simply. In the first table it is easy to estimate the percentages with the help of the horizontal lines and their labels. From the second table the reader is able to get the exact data.
We created a clear and powerful message with our redesigned graph.

------------------------------- <br> <br>

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-02T21:05:10Z

UE-InfoVis0910 0402536:

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-02T21:04:36Z

UE-InfoVis0910 0402536:

File:Graph 01.png

2009-12-02T21:03:42Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 3

2009-12-01T20:57:32Z

UE-InfoVis0910 0402536:

File:Uebung3.png

2009-12-01T20:47:41Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 2

2009-11-18T21:17:16Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]
=== Zu beurteilende Tabelle ===
[[Image:paik_tab5.jpg]]

===Kritik der vorliegenden Tabelle===
The given table lacks grouping and white areas for spacing of any kind, making it difficult to sort through the list.The table number is above the title. The table number should always be in the same line as the tiltel.For table notes it´s best practice to use an asterisk (*) for the first note, two (**) for the 2nd, three (***) for the 3rd or a stacked cross. The given table uses letters to refer to table notes. Table notes should start with the initial word ''Note:'' under the table. The stubhead ''Method'' is to close to the column spanner and column heads, making it hard to see where it belongs. The given table uses too much digits of decimal precision.

===Verbesserte Tabelle===
[[Image:new_Table_1.jpg]]

===Vorgenommene Verbesserungen===
To accomplish the task of ease and speed, our table uses new grouping and white areas for spacing between the data in order to break the list apart and make it easy to follow. We switched the stub header + stubs with the column spanner and column heads to get a new table grouping to make it easy on the eyes. We adjusted the tilte and the table number in the understanding of best practice. We rounded the numbers to a maximum of three decimal places.

File:New Table 1.jpg

2009-11-18T21:16:42Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 2

2009-11-18T21:08:53Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]
=== Zu beurteilende Tabelle ===
[[Image:paik_tab5.jpg]]

===Kritik der vorliegenden Tabelle===
The given table lacks grouping and white areas for spacing of any kind, making it difficult to sort through the list.The table number is above the title. The table number should always be in the same line as the tiltel.For table notes it´s best practice to use an asterisk (*) for the first note, two (**) for the 2nd, three (***) for the 3rd or a stacked cross. The given table uses letters to refer to table notes. Table notes should start with the initial word ''Note:'' under the table. The stubhead ''Method'' is to close to the column spanner and column heads, making it hard to see where it belongs. The given table uses too much digits of decimal precision.

===Verbesserte Tabelle===
[[Image:new_Table123.jpg]]

===Vorgenommene Verbesserungen===
To accomplish the task of ease and speed, our table uses new grouping and white areas for spacing between the data in order to break the list apart and make it easy to follow. We switched the stub header + stubs with the column spanner and column heads to get a new table grouping to make it easy on the eyes. We adjusted the tilte and the table number in the understanding of best practice. We rounded the numbers to a maximum of three decimal places.

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05 - Aufgabe 2

2009-11-18T20:27:51Z

UE-InfoVis0910 0402536:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]
=== Zu beurteilende Tabelle ===
[[Image:paik_tab5.jpg]]

===Kritik der vorliegenden Tabelle===

===Verbesserte Tabelle===
[[Image:new_Table123.jpg]]

===Vorgenommene Verbesserungen===

File:New Table123.jpg

2009-11-18T20:26:11Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:New Table.jpg

2009-11-18T20:04:15Z

UE-InfoVis0910 0402536: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:45:47Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system which uses two or more views to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offers a variety of benefits. For example improved user performance or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design. They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==
Designers of multiple view systems necessarily begin by establishing a clear understanding of the user´s task. The following rules present a guideline for designers to fulfill the user´s needs.

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:RuleOfAttention.jpg|150px|thumb|Multiple views of Internet service data. The view in the upper left draws the user attention to priority events]]

==Using a Multiple View System in a Virtual Environment==
A '''dataset''' can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
Each of the views is used to extract different types of information hidden in the data. It is possible to switch between these views and tools can be selected to interpret the data set. <ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany.</ref>

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:43:47Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system which uses two or more views to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offers a variety of benefits. For example improved user performance or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design. They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system. Designers of multiple view systems necessarily begin by establishing a clear understanding of the user´s task. The following rules present a guideline for designers to fulfill the user´s needs.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:RuleOfAttention.jpg|150px|thumb|Multiple views of Internet service data. The view in the upper left draws the user attention to priority events]]

==Using a Multiple View System in a Virtual Environment==
A '''dataset''' can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
Each of the views is used to extract different types of information hidden in the data. It is possible to switch between these views and tools can be selected to interpret the data set. <ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany.</ref>

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:40:08Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system which uses two or more views to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offers a variety of benefits. For example improved user performance or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design. They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views. Designers of multiple view systems necessarily begin by establishing a clear understanding of the user´s task. The following rules present a guideline for designers to fulfill the user´s needs.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:RuleOfAttention.jpg|150px|thumb|Multiple views of Internet service data. The view in the upper left draws the user attention to priority events]]

==Using a Multiple View System in a Virtual Environment==
A '''dataset''' can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
Each of the views is used to extract different types of information hidden in the data. It is possible to switch between these views and tools can be selected to interpret the data set. <ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany.</ref>

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:24:04Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system which uses two or more views to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:RuleOfAttention.jpg|150px|thumb|Multiple views of Internet service data. The view in the upper left draws the user attention to priority events]]

==Using a Multiple View System in a Virtual Environment==
<ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany; Andre.Hinkenjann@gmd.de</ref>

A '''dataset''' can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
It is possible to switch between these views and tools can be selected to interpret the data set.

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:22:39Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system which uses two or more views to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:RuleOfAttention.jpg|150px|thumb|Multiple views of Internet service data. The view in the upper left draws the user attention to priority events]]

==Using a Multiple View System in a Virtual Environment==
<ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany; Andre.Hinkenjann@gmd.de</ref>

A '''dataset''' can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
It is possible to switch between these views and tools can be selected to interpret the data set.

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:11:17Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:RuleOfAttention.jpg|150px|thumb|Multiple views of Internet service data. The view in the upper left draws the user attention to priority events]]

==Using a Multiple View System in a Virtual Environment==
<ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany; Andre.Hinkenjann@gmd.de</ref>

A '''dataset''' can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
It is possible to switch between these views and tools can be selected to interpret the data set.

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:10:01Z

UE-InfoVis0910 0402536:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:08:17Z

UE-InfoVis0910 0402536:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T18:04:00Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:RuleOfAttention.jpg|150px|thumb|Multiple views of Internet service data. The view in the upper left draws the user attention to priority events]]

==Using a Multiple View System in a Virtual Environment== <ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany; Andre.Hinkenjann@gmd.de</ref>

A dataset can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
It is possible to switch between these views and tools can be selected to interpret the data set.

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T17:57:33Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

==Using a Multiple View System in a Virtual Environment==
<ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany; Andre.Hinkenjann@gmd.de</ref>

A dataset can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
It is possible to switch between these views and tools can be selected to interpret the data set.

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T17:56:14Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

==Using a Multiple View System in a Virtual Environment== <ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany; Andre.Hinkenjann@gmd.de</ref>

A dataset can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
It is possible to switch between these views and tools can be selected to interpret the data set.

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-05T17:52:16Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}
==Using a Multiple View System in a Virtual Environment== <ref> Andre Hinkenjann; Using a Multiple View System in a Virtual Environment to Explore and Interpret Communication Data Sets; GMD, Department of Virtual Environments, Sankt Augustin, Germany; Andre.Hinkenjann@gmd.de</ref>
A dataset can be viewed with multiple viewing options:
*''Spatial Mode'' for an overview of the spatial relationship of the transmitters.
*''Abstract Mode'' to recognize patterns in communication relation.
*''Hierarchical Mode'' for viewing the structural organization of the participating communicators.
It is possible to switch between these views and tools can be selected to interpret the data set.

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T22:08:43Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T22:07:03Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

==Model==
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

==Design Rules==

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

==References==
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T22:05:05Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

===Model===
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

*====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

*====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

*====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

===Design Rules===

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T22:03:38Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Definitions===
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

===Model===
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagated to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

===Design Rules===

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T21:19:35Z

UE-InfoVis0910 0402536:

{{definition|'''The Relationship between Views''' in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Model===
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Definitions====
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagates to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

===Design Rules===

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T21:11:20Z

UE-InfoVis0910 0402536:

{{Definition|The relationship between views in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Model===
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Definitions====
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagates to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

===Design Rules===

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent.| <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time.|<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T21:06:18Z

UE-InfoVis0910 0402536:

{{Definition|The relationship between views in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Model===
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Definitions====
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagates to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

===Design Rules===

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

Quotation|Use perceptual cues to make relationships among views more apparent to the user. <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent. <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time. <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - View Relationships

2009-11-04T21:04:22Z

UE-InfoVis0910 0402536:

{{Definition|The relationship between views in a multiple view system to form a single conceptual entity.}}

A multiple view system uses two or more distinct views to support the investigation of a single conceptual entity. Many such systems exist, ranging from computer-aided design (CAD) systems to overview-plus-detail systems that show both and overview for context and a zoomed-in-view for detail.

Multiple view system offer a variety of benefits. For example improved user performance, or discovery of unforeseen relationships. In general, they can help in performing ''Visual Information Seeking Tasks'' as defined by Ben Shneiderman in his ''Task by Data Type Taxonomy'' <ref>Ben Shneiderman, The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In ''Proceedings of the IEEE Symposium on Visual Languages'', pages 336-343, Washington. IEEE Computer Society Press, 1996. http://citeseer.ist.psu.edu/409647.html</ref> like gaining an overview of a collection, viewing details on demand, or viewing relationships among items.

However, multiple view systems are highly challenging to design, They often use sophisticated coordination mechanisms and layout. In addition, subtle interactions among the many dimensions of the design space complicate design decisions.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>

===Model===
Multiple view systems are based on three dimensions: ''selection'' of views, ''presentation'' of views, and ''interaction'' among views.

====Definitions====
*A ''single view'' of a conceptual entity is a set of data plus a specification of how to display that data visually.
*Views are ''distinct'' if they allow the user to learn about different aspects of the conceptual entity.
*A ''multiple view system'' uses two or more such distinct views to support the investigation of a given conceptual entity.

====Selection====
The first phase in the design process is to choose a set of views to be used in a coordinated fashion.

====Presentation====
Once a set of views has been chosen, the designer needs to decide how the views will be presented, e.g., sequentially or simultaneously. If the views appear at once, there are many possible combinations of these views on the screen.

====Interaction====
Each view may have independent affordances, e.g., selection or navigation capabilities. There are several common interaction techniques concerning the relationship between multiple views:
*''Navigational Slaving:'' Movements in one view are automatically propagates to other views.
*''Linking:'' Data in one view is connected to data in another view. A specific type of linking is ''brushing'', in which the user highlights items in one view and the corresponding items in another view are highlighted by the system.

[[Image:omniplan.png|150px|thumb|Brushing in OmniPlan]]

Both, slaving and linking are typically governed by a ''coupling function'' that specifies a mapping from objects or navigational position in one view to objects or navigational position in another view.

===Design Rules===

====Space/Time Resource Optimization====
Presenting multiple views sequentially can save display space, but presenting multiple views at once can save time when comparing views, therefore:

{{Quotation|Balance the spatial and temporal costs of presenting multiple views with the spatial and temporal benefits of using the views.<ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_maps.png|150px|thumb|Overlapping Views in Google Maps]]

====Self Evidence====
Perceptual cues can move view registration/alignment from the realm of cognition to the realm of perception, so users can learn more quickly, therefore:

{{Quotation|Use perceptual cues to make relationships among views more apparent to the user. <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

[[Image:google_finance.png|150px|thumb|Self Evident Relationship between Overview and Detail in Google Finance]]

====Consistency====
The additional complexity introduced by multiple views must be balanced by ease of learning, which is facilitated by consistency and can make comparisons easier, therefore:

{{Quotation|Make the interface for multiple views consistent, and make the states of multiple views consistent. <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

====Attention Management====
When events occur which require the user's attention, perceptual techniques can direct the user to a salient view, therefore:

{{Quotation|Use perceptual techniques to focus the user's attention on the right view at the right time. <ref> Michelle Q. Wang Baldonado, Allison Woodruff, and Allan Kuchinsky.: Guidelines for Using Multiple Views in Information Visualization. ''Advanced Visual Interfaces (AVI2000)'', pages 110–119, Palermo, Italy, May 2000. ACM Press.</ref>}}

===References===
<div class="references-small"> <references/> </div>
See also: [[Linking and Brushing]]

Visual Variables

2009-11-04T20:45:02Z

UE-InfoVis0910 0402536:

{{definition|'''Visual Variables''' are a specified set of symbols that can be applied to data in order to translate information.}}

== Purpose and Development ==
Our usual way of communicating is with words. Written words consist of single symbols (letters), gaining meaning when arranged in certain combinations. The question is: If there are basic visual symbols arranged in a particular way, can they be used to convey information in a similar manner?
All of those developments were primarily made for cartographic purposes. With the computerization of information these '''visual variables''' were adapted and used for information visualization.
The concept of information visualization began in the 1930's, but after the 1950's became more developed by cartographers. Since the development of computers has revolutionized all aspects of information visualization. <ref> http://en.wikipedia.org/wiki/Animated_mapping#Visual_variables </ref>
Mapmaking with pan and paper become unnecessary. Map making software such as CAD, GIS and specialized map illustration software became very important.<ref> Skupin, A: ''From Metaphor to Method: Cartographic Perspectives on Information Visualization'', IEEE Symposium on Information Visualization. Salt Lake City, 2000</ref>

==Jaques Bertin==
Jaques Bertin<ref> Bertin, J.: ''Sémiologie Graphique''. Paris: Editions Gauthier-Villars. Deutsche Übersetzung von Jensch, G.; Schade, D.; Scharfe, W.: Graphische Semiologie.Diagramme – Netze - Karten. Berlin: Walter de Gruyter, 1974.</ref>described '''marks''' as these basic units and also developed a given number of methods these units can be modified with, such as position, size, shape, or color. These predefined modifications are called '''visual variables'''. Each of these variables can have certain '''characteristics'''. Sometimes visual variables are also called '''visual attributes'''.

=== Marks ===
A mark is made to represent some information other than itself. It is also referred to as a sign.

Marks can be
* '''Points''' are dimensionless locations on the plane, represented by signs that obviously need to have some size, shape or color for visualization.
* '''Lines''' represent information with a certain length, but no area and therefore no width. Again lines are visualized by signs of some thickness.
* '''Areas''' have a length and a width and therefore a two-dimensional size.
* '''Surfaces''' are areas in a three-dimensional space, but with no thickness.
* '''Volumes''' have a length, a width and a depth. They are thus truly three-dimensional.

=== Visual Variables ===
Jaques Bertin defined seven '''Visual Variables''' consisting of:

[[Image:visualVariables.png]]

==Jock D. Mackinley==
Jock D. Mackinlay invented a number of Information Visualization techniques such as the information visualization reference model.<ref> http://en.wikipedia.org/wiki/Jock_D._Mackinlay</ref>

=== Visual Variables ===
The list of visual variables was later expanded by [[Mackinlay%2C_Jock_D.|Jock D. Mackinlay]]. He also provided different sorting for their accuracy, based on the task.

===== Sorted by Accuracy for Quantitive Tasks =====
[[Image:Mackinlay_PerceptualTask.jpg]]

=== Recent work ===
The list was further expanded by several later publications. Most of them are also grouping
the visual variables, e.g. combining ''length'', ''area'' and ''repetition'' to ''shape'' or breaking down
''position'' in the three dimensions of space and one time dimension.

Since nowadays information is presented by computers, the addition of '''motion''' as a new visual variable becomes important. Changes in motion can include direction, speed, frequency, rhythm, flicker, trails, and style.<ref> Carpendale, M. S. T.: ''Considering Visual Variables as a Basis for Information Visualisation'', University of Calgary, Department of Computer Science, 2001-693-16, 2003</ref>

=== Characteristics ===
The choice of the variable, which would be most appropriate to represent each aspect of information depends on its characteristics.

* '''Selective:''' If a mark changes in this variable and as an effect can be selected from the other marks easily the visual variable is said to be selective.
* '''Associative:''' Several marks can be grouped across changes in other visual variables.
* '''Quantitative:''' If the difference between two marks in this variable can be interpreted numerically, the visual variable is quantitative.
* '''Order:''' If the variable supports ordered reading it is an ordered visual variable. This means that a change could be read as more or less (e.g. in size you can order marks according to their area).
* '''Length:''' The length defines how many values the variable features. For example how many shades of grey can be recognized?

== Usage ==
The process of mapping data to visual variables is called [[visual mapping]].
Choosing different visual variables for representing different aspects of the same information can greatly influence the perception and understanding of the presented information. It is therefore important to know and appropriately use the characteristics of visual variables when creating ''any'' visual data representation.

== References ==

<div class="references-small"> <references/> </div>
[[Category:Glossary]]

Visual Variables

2009-11-04T20:44:20Z

UE-InfoVis0910 0402536:

{{definition|'''Visual Variables''' are a specified set of symbols that can be applied to data in order to translate information.}}

== Purpose and Development ==
Our usual way of communicating is with words. Written words consist of single symbols (letters), gaining meaning when arranged in certain combinations. The question is: If there are basic visual symbols arranged in a particular way, can they be used to convey information in a similar manner?
All of those developments were primarily made for cartographic purposes. With the computerization of information these '''visual variables''' were adapted and used for information visualization.
The concept of information visualization began in the 1930's, but after the 1950's became more developed by cartographers. Since the development of computers has revolutionized all aspects of information visualization. <ref> http://en.wikipedia.org/wiki/Animated_mapping#Visual_variables </ref>
Mapmaking with pan and paper become unnecessary. Map making software such as CAD, GIS and specialized map illustration software became very important.<ref> Skupin, A: ''From Metaphor to Method: Cartographic Perspectives on Information Visualization'', IEEE Symposium on Information Visualization. Salt Lake City, 2000</ref>

==Jaques Bertin==
Jaques Bertin<ref> Bertin, J.: ''Sémiologie Graphique''. Paris: Editions Gauthier-Villars. Deutsche Übersetzung von Jensch, G.; Schade, D.; Scharfe, W.: Graphische Semiologie.Diagramme – Netze - Karten. Berlin: Walter de Gruyter, 1974.</ref>described '''marks''' as these basic units and also developed a given number of methods these units can be modified with, such as position, size, shape, or color. These predefined modifications are called '''visual variables'''. Each of these variables can have certain '''characteristics'''. Sometimes visual variables are also called '''visual attributes'''.

=== Marks ===
A mark is made to represent some information other than itself. It is also referred to as a sign.

Marks can be
* '''Points''' are dimensionless locations on the plane, represented by signs that obviously need to have some size, shape or color for visualization.
* '''Lines''' represent information with a certain length, but no area and therefore no width. Again lines are visualized by signs of some thickness.
* '''Areas''' have a length and a width and therefore a two-dimensional size.
* '''Surfaces''' are areas in a three-dimensional space, but with no thickness.
* '''Volumes''' have a length, a width and a depth. They are thus truly three-dimensional.

=== Visual Variables ===
Jaques Bertin defined seven '''Visual Variables''' consisting of:

[[Image:visualVariables.png]]

==Jock D. Mackinley==
Jock D. Mackinlay invented a number of Information Visualization techniques such as the information visualization reference model.<ref> http://en.wikipedia.org/wiki/Jock_D._Mackinlay</ref>

=== Visual Variables ===
The list of visual variables was later expanded by [[Mackinlay%2C_Jock_D.|Jock D. Mackinlay]]. He also provided different sorting for their accuracy, based on the task.

===== Sorted by Accuracy for Quantitive Tasks =====
[[Image:Mackinlay_PerceptualTask.jpg]]

=== Recent work ===
The list was further expanded by several later publications. Most of them are also grouping
the visual variables, e.g. combining ''length'', ''area'' and ''repetition'' to ''shape'' or breaking down
''position'' in the three dimensions of space and one time dimension.

Since nowadays information is presented by computers, the addition of '''motion''' as a new visual variable becomes important. Changes in motion can include direction, speed, frequency, rhythm, flicker, trails, and style.<ref> Carpendale, M. S. T.: ''Considering Visual Variables as a Basis for Information Visualisation'', University of Calgary, Department of Computer Science, 2001-693-16, 2003</ref>

=== Characteristics ===
The choice of the variable, which would be most appropriate to represent each aspect of information depends on its characteristics.

* '''Selective:''' If a mark changes in this variable and as an effect can be selected from the other marks easily the visual variable is said to be selective.
* '''Associative:''' Several marks can be grouped across changes in other visual variables.
* '''Quantitative:''' If the difference between two marks in this variable can be interpreted numerically, the visual variable is quantitative.
* '''Order:''' If the variable supports ordered reading it is an ordered visual variable. This means that a change could be read as more or less (e.g. in size you can order marks according to their area).
* '''Length:''' The length defines how many values the variable features. For example how many shades of grey can be recognized?

== Usage ==
The process of mapping data to visual variables is called [[visual mapping]].
Choosing different visual variables for representing different aspects of the same information can greatly influence the perception and understanding of the presented information. It is therefore important to know and appropriately use the characteristics of visual variables when creating ''any'' visual data representation.

== References ==
* '''Proceedings'''
<div class="references-small"> <references/> </div>
[[Category:Glossary]]