<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://infovis-wiki.net/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=UE-InfoVis0708+0225966</id>
	<title>InfoVis:Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://infovis-wiki.net/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=UE-InfoVis0708+0225966"/>
	<link rel="alternate" type="text/html" href="https://infovis-wiki.net/wiki/Special:Contributions/UE-InfoVis0708_0225966"/>
	<updated>2026-04-07T14:39:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.42.6</generator>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching_talk:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18775</id>
		<title>Teaching talk:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching_talk:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18775"/>
		<updated>2008-02-05T15:05:13Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Bewertung ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Punkte: 21 von 25&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Begründung:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
siehe Kommentare (kursiv) bei [[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3|Aufgabe 3]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Ihr habt die Möglichkeit, die angegebenen Dinge noch bis einschließlich 15.01.2008 zu verbessern - &amp;lt;br&amp;gt;dann wird natürlich eure Punkteanzahl aufgewertet!&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
-- [[User:ASchratt|Alexander Schratt]] 17:31, 20 December 2007 (CEST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Keine Änderungen vorgenommen. Daher bleibt es beim alten Punktestand.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
-- [[User:ASchratt|Alexander Schratt]] 15:50, 05 February 2008 (CEST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Die Graphik wurde doch verbessert !&#039;&#039;&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching_talk:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18772</id>
		<title>Teaching talk:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching_talk:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18772"/>
		<updated>2008-02-05T14:55:08Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Bewertung ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Punkte: 21 von 25&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Begründung:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
siehe Kommentare (kursiv) bei [[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3|Aufgabe 3]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Ihr habt die Möglichkeit, die angegebenen Dinge noch bis einschließlich 15.01.2008 zu verbessern - &amp;lt;br&amp;gt;dann wird natürlich eure Punkteanzahl aufgewertet!&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
-- [[User:ASchratt|Alexander Schratt]] 17:31, 20 December 2007 (CEST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Keine Änderungen vorgenommen. Daher bleibt es beim alten Punktestand.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
-- [[User:ASchratt|Alexander Schratt]] 15:50, 05 February 2008 (CEST)&lt;br /&gt;
&lt;br /&gt;
-- Die Graphik wurde doch verbessert !&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_4&amp;diff=18649</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 4</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_4&amp;diff=18649"/>
		<updated>2008-01-04T22:04:39Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Aufgabenstellung ==&lt;br /&gt;
&lt;br /&gt;
Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration &amp;lt;br&amp;gt;(des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. &amp;lt;br&amp;gt;sollen von Euch selbst festgelegt und beschrieben werden.&lt;br /&gt;
&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]&lt;br /&gt;
&lt;br /&gt;
=== Beispiele für derartige Datensätze ===&lt;br /&gt;
&lt;br /&gt;
[[Image:20061115_blutuntersuchung.jpg]]&lt;br /&gt;
&lt;br /&gt;
[[Image:20070920_blutuntersuchung.jpg]]&lt;br /&gt;
&lt;br /&gt;
= ABGABE =&lt;br /&gt;
&lt;br /&gt;
== Analysis of the application area ==&lt;br /&gt;
&lt;br /&gt;
=== Application Area Analysis ===&lt;br /&gt;
&lt;br /&gt;
Laboratory Values of blood tests should be visualized, in order to make an exploration, for a point in time as well in a chronological sequence, possible. This Application Area is highly sensible with high expectance towards accuracy. Furthermore the development of blood test results over time is of special interest. For the interpretation of the values and a diagnosis based on these values, the available reference values are of central relevance.&lt;br /&gt;
&lt;br /&gt;
One special characteristic is that the results are within known ranges. The scale can therefore be adjusted towards these ranges.&lt;br /&gt;
&lt;br /&gt;
=== Dataset Analysis ===&lt;br /&gt;
Theoretically the values of the blood tests are continuous. From a practical point of view the values will not undercut or exceed some certain borders. Therefore the data can be considered as steady and finite. The borders will be set obviously ample to be able to visualize the most unlikely values as well. &lt;br /&gt;
&lt;br /&gt;
The data is two dimensional. One dimension is the value, the second dimension shows the point in time (the date of the blood test) for which this value is valid.&lt;br /&gt;
It has to be analyzed whether certain test results could be gathered together from a thematic point of view, in order to create structures and groups.&lt;br /&gt;
&lt;br /&gt;
=== Target Group Analysis ===&lt;br /&gt;
The doctor needs a fast overview of the test results to be able to create a diagnosis. First and foremost the visualization should therefore help doctors to get an overview of the test results. The second target group should be patients. It should be possible to explain them in an easy way the test results.&lt;br /&gt;
&lt;br /&gt;
=== Target Group Specifics ===&lt;br /&gt;
Doctors often lack time and are under performance pressure. To avoid misinterpretations and to support the doctor in creating a diagnosis, the doctors’ attention should be drawn to the values outside the reference range. Furthermore an overview should show whether the results are ok or not.&lt;br /&gt;
Patients should be able to understand easily the visualized values. It is of high importance that the patient gets support in reaching clarity in this sensible topic.&lt;br /&gt;
&lt;br /&gt;
=== Well known Visualization Techniques for this area ===&lt;br /&gt;
Icon-based techniques would be a possible approach for visualizing this kind of data. There are some tools like the VIE-VISU-system [Horn et al., 1998] for example that use glyphs to visualize medical data.  The drawback of most icon-based techniques is that they cannot visualize data that changes its values continuously over time. In most cases only specific points in time are visualized separately by one glyph. The VIE-VISU-system for example uses 24 glyphs to represent one 24-hour-cycle of measurements. &lt;br /&gt;
Purpose of the Visualization&lt;br /&gt;
&lt;br /&gt;
The visualization should provide an overview over the blood test results both for a concrete test and in variation in time.&lt;br /&gt;
An outstanding task is the elevated focus on values which exceed or undercut the predefined borders. Not only these values need special attention, but as well the values near these borders should be focused in some way.&lt;br /&gt;
The visualization should answer questions like whether the blood values are in the normal range, whether some tendencies exist and whether one or more values should be drawn more attention to.&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
As mentioned above, the tool is mainly intended for doctors, therefore one should be able to use it intuitively.&lt;br /&gt;
The information to emphasize would be :&lt;br /&gt;
&lt;br /&gt;
* the change of a specific blood feature over time&lt;br /&gt;
* when the value of a blood feature goes outside of its reference interval&lt;br /&gt;
&lt;br /&gt;
We also want to keep the table format, because of its convenience when looking up specific values [Few, 2006]. Also, our values have more than one unit of measure, which makes it useless to compare them amongst each other [Few, 2006]. A graph is used for visualizing the values of a specific blood feature over time.&lt;br /&gt;
&lt;br /&gt;
=== Design ===&lt;br /&gt;
&lt;br /&gt;
The design is was intentionally kept simple, not to distract the user from the main task. It only offers the most important information.&lt;br /&gt;
&lt;br /&gt;
==== Header ====&lt;br /&gt;
&lt;br /&gt;
All screens have a common header with the name of the patient and a time line. The time line shows the dates when blood tests were taken. The user may click on each date and the corresponding data will be shown. It is also possible to drag the time line in order to shift the view port if there are too many dates to fit on the screen.&lt;br /&gt;
&lt;br /&gt;
==== Outline Screen ====&lt;br /&gt;
&lt;br /&gt;
[[Image:screen1.png | 250px | Outline screen]]&lt;br /&gt;
&lt;br /&gt;
The initial screen shows the data in tabular form. Values which are outside the reference interval are shown on top of the list, colored red and in alphabetical order.This makes it easy for the doctor to immediately spot dangerous values. Other values are colored green, also in alphabetical order. Upon clicking on the triangle next to a blood feature we get to the detailed screen.&lt;br /&gt;
&lt;br /&gt;
==== Detailed Screen ====&lt;br /&gt;
&lt;br /&gt;
[[Image:screen2.png | 250px | Detailed screen]]&lt;br /&gt;
 &lt;br /&gt;
This screen has a graph showing the various measurements of the selected feature over time. The area of the reference interval is colored green, everything outside of it is red. The selected value has a enlarged dot and is centered on the screen. It is also possible to use the time line to select a different date.&lt;br /&gt;
&lt;br /&gt;
=== Discussion ===&lt;br /&gt;
&lt;br /&gt;
One of the main goals of the design was to keep it simple, so that the user does not have to go through a manual to figure out how things work (doctors are usually not technical people). The sorted table supports the user in locating irregularities in the blood sample as fast as possible. The detailed view gives an insight about the history of selected blood feature and therewith assists in discovering recidivism. A possible improvement would be to use different shades of green/red to indicate how close a value is to the border of the reference interval. Whether or not this information would really be useful has to be discussed with a doctor.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* [Horn et al., 1998] Werner Horn, Christian Popow, and Lukas Unterasinger. Metaphor Graphics to Visualize ICU Data over Time, In Proceedings of Intelligent Data Analysis in Medicine and Pharmacology (IDAMAP-98), Workshop Notes of the ECAI-98 Workshop, 1998.&lt;br /&gt;
* [Few, 2006] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Appendix A - Table and Graph Design at a Glance.&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_4&amp;diff=18648</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 4</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_4&amp;diff=18648"/>
		<updated>2008-01-04T21:38:01Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Aufgabenstellung ==&lt;br /&gt;
&lt;br /&gt;
Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration &amp;lt;br&amp;gt;(des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. &amp;lt;br&amp;gt;sollen von Euch selbst festgelegt und beschrieben werden.&lt;br /&gt;
&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]&lt;br /&gt;
&lt;br /&gt;
=== Beispiele für derartige Datensätze ===&lt;br /&gt;
&lt;br /&gt;
[[Image:20061115_blutuntersuchung.jpg]]&lt;br /&gt;
&lt;br /&gt;
[[Image:20070920_blutuntersuchung.jpg]]&lt;br /&gt;
&lt;br /&gt;
= ABGABE =&lt;br /&gt;
&lt;br /&gt;
== Analysis of the application area ==&lt;br /&gt;
&lt;br /&gt;
=== Application Area Analysis ===&lt;br /&gt;
&lt;br /&gt;
Laboratory Values of blood tests should be visualized, in order to make an exploration, for a point in time as well in a chronological sequence, possible. This Application Area is highly sensible with high expectance towards accuracy. Furthermore the development of blood test results over time is of special interest. For the interpretation of the values and a diagnosis based on these values, the available reference values are of central relevance.&lt;br /&gt;
&lt;br /&gt;
One special characteristic is that the results are within known ranges. The scale can therefore be adjusted towards these ranges.&lt;br /&gt;
&lt;br /&gt;
=== Dataset Analysis ===&lt;br /&gt;
Theoretically the values of the blood tests are continuous. From a practical point of view the values will not undercut or exceed some certain borders. Therefore the data can be considered as steady and finite. The borders will be set obviously ample to be able to visualize the most unlikely values as well. &lt;br /&gt;
&lt;br /&gt;
The data is two dimensional. One dimension is the value, the second dimension shows the point in time (the date of the blood test) for which this value is valid.&lt;br /&gt;
It has to be analyzed whether certain test results could be gathered together from a thematic point of view, in order to create structures and groups.&lt;br /&gt;
&lt;br /&gt;
=== Target Group Analysis ===&lt;br /&gt;
The doctor needs a fast overview of the test results to be able to create a diagnosis. First and foremost the visualization should therefore help doctors to get an overview of the test results. The second target group should be patients. It should be possible to explain them in an easy way the test results.&lt;br /&gt;
&lt;br /&gt;
=== Target Group Specifics ===&lt;br /&gt;
Doctors often lack time and are under performance pressure. To avoid misinterpretations and to support the doctor in creating a diagnosis, the doctors’ attention should be drawn to the values outside the reference range. Furthermore an overview should show whether the results are ok or not.&lt;br /&gt;
Patients should be able to understand easily the visualized values. It is of high importance that the patient gets support in reaching clarity in this sensible topic.&lt;br /&gt;
&lt;br /&gt;
=== Well known Visualization Techniques for this area ===&lt;br /&gt;
Icon-based techniques would be a possible approach for visualizing this kind of data. There are some tools like the VIE-VISU-system [Horn et al., 1998] for example that use glyphs to visualize medical data.  The drawback of most icon-based techniques is that they cannot visualize data that changes its values continuously over time. In most cases only specific points in time are visualized separately by one glyph. The VIE-VISU-system for example uses 24 glyphs to represent one 24-hour-cycle of measurements. &lt;br /&gt;
Purpose of the Visualization&lt;br /&gt;
&lt;br /&gt;
The visualization should provide an overview over the blood test results both for a concrete test and in variation in time.&lt;br /&gt;
An outstanding task is the elevated focus on values which exceed or undercut the predefined borders. Not only these values need special attention, but as well the values near these borders should be focused in some way.&lt;br /&gt;
The visualization should answer questions like whether the blood values are in the normal range, whether some tendencies exist and whether one or more values should be drawn more attention to.&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
As mentioned above, the tool is mainly intended for doctors, therefore one should be able to use it intuitively.&lt;br /&gt;
The information to emphasize would be :&lt;br /&gt;
&lt;br /&gt;
* the change of a specific blood feature over time&lt;br /&gt;
* when the value of a blood feature goes outside of its reference interval&lt;br /&gt;
&lt;br /&gt;
We also want to keep the table format, because of its convenience when looking up specific values [Few, 2006]. Also, our values have more than one unit of measure, which makes it useless to compare them amongst each other [Few, 2006]. A graph is used for visualizing the values of a specific blood feature over time.&lt;br /&gt;
&lt;br /&gt;
=== Design ===&lt;br /&gt;
&lt;br /&gt;
The design is was intentionally kept simple, not to distract the user from the main task.&lt;br /&gt;
&lt;br /&gt;
==== Header ====&lt;br /&gt;
&lt;br /&gt;
All screens have a common header with the name of the patient and a time line. The time line shows the dates when blood tests were taken. The user may click on each date and the corresponding data will be shown. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Outline Screen ====&lt;br /&gt;
&lt;br /&gt;
[[Image:screen1.png | 250px | Outline screen]]&lt;br /&gt;
&lt;br /&gt;
The initial screen shows the data in tabular form. Values which are outside the reference interval are shown on top of the list, colored red and in alphabetical order.This makes it easy for the doctor to immediately spot dangerous values. Other values are colored green, also in alphabetical order. Upon clicking on the triangle next to a blood feature we get to the next screen.&lt;br /&gt;
&lt;br /&gt;
==== Detailed Screen ====&lt;br /&gt;
&lt;br /&gt;
[[Image:screen2.png | 250px | Detailed screen]]&lt;br /&gt;
 &lt;br /&gt;
This screen has a graph showing the various measurements of the selected feature over time. The area of the reference interval is colored green, everything outside of it is red. The selected value has a enlarged dot and is centered on the screen. It is also possible to use the time line to select a different date.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* [Horn et al., 1998] Werner Horn, Christian Popow, and Lukas Unterasinger. Metaphor Graphics to Visualize ICU Data over Time, In Proceedings of Intelligent Data Analysis in Medicine and Pharmacology (IDAMAP-98), Workshop Notes of the ECAI-98 Workshop, 1998.&lt;br /&gt;
* [Few, 2006] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Appendix A - Table and Graph Design at a Glance.&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Screen2.png&amp;diff=18647</id>
		<title>File:Screen2.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Screen2.png&amp;diff=18647"/>
		<updated>2008-01-04T21:08:06Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: == Summary ==  == Copyright status ==  == Source ==&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Screen1.png&amp;diff=18646</id>
		<title>File:Screen1.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Screen1.png&amp;diff=18646"/>
		<updated>2008-01-04T21:07:31Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: == Summary ==  == Copyright status ==  == Source ==&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_4&amp;diff=18619</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 4</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_4&amp;diff=18619"/>
		<updated>2008-01-04T16:56:02Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Aufgabenstellung ==&lt;br /&gt;
&lt;br /&gt;
Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration &amp;lt;br&amp;gt;(des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. &amp;lt;br&amp;gt;sollen von Euch selbst festgelegt und beschrieben werden.&lt;br /&gt;
&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]&lt;br /&gt;
&lt;br /&gt;
=== Beispiele für derartige Datensätze ===&lt;br /&gt;
&lt;br /&gt;
[[Image:20061115_blutuntersuchung.jpg]]&lt;br /&gt;
&lt;br /&gt;
[[Image:20070920_blutuntersuchung.jpg]]&lt;br /&gt;
&lt;br /&gt;
= ABGABE =&lt;br /&gt;
&lt;br /&gt;
== Analysis of the application area ==&lt;br /&gt;
&lt;br /&gt;
=== Application Area Analysis ===&lt;br /&gt;
&lt;br /&gt;
Laboratory Values of blood tests should be visualized, in order to make an exploration, for a point in time as well in a chronological sequence, possible. This Application Area is highly sensible with high expectance towards accuracy. Furthermore the development of blood test results over time is of special interest. For the interpretation of the values and a diagnosis based on these values, the available reference values are of central relevance.&lt;br /&gt;
&lt;br /&gt;
One special characteristic is that the results are within known ranges. The scale can therefore be adjusted towards these ranges.&lt;br /&gt;
&lt;br /&gt;
=== Dataset Analysis ===&lt;br /&gt;
Theoretically the values of the blood tests are continuous. From a practical point of view the values will not undercut or exceed some certain borders. Therefore the data can be considered as steady and finite. The borders will be set obviously ample to be able to visualize the most unlikely values as well. &lt;br /&gt;
&lt;br /&gt;
The data is two dimensional. One dimension is the value, the second dimension shows the point in time (the date of the blood test) for which this value is valid.&lt;br /&gt;
It has to be analyzed whether certain test results could be gathered together from a thematic point of view, in order to create structures and groups.&lt;br /&gt;
&lt;br /&gt;
=== Target Group Analysis ===&lt;br /&gt;
The doctor needs a fast overview of the test results to be able to create a diagnosis. First and foremost the visualization should therefore help doctors to get an overview of the test results. The second target group should be patients. It should be possible to explain them in an easy way the test results.&lt;br /&gt;
&lt;br /&gt;
=== Target Group Specifics ===&lt;br /&gt;
Doctors often lack time and are under performance pressure. To avoid misinterpretations and to support the doctor in creating a diagnosis, the doctors’ attention should be drawn to the values outside the reference range. Furthermore an overview should show whether the results are ok or not.&lt;br /&gt;
Patients should be able to understand easily the visualized values. It is of high importance that the patient gets support in reaching clarity in this sensible topic.&lt;br /&gt;
&lt;br /&gt;
=== Well known Visualization Techniques for this area ===&lt;br /&gt;
Icon-based techniques would be a possible approach for visualizing this kind of data. There are some tools like the VIE-VISU-system [Horn et al., 1998] for example that use glyphs to visualize medical data.  The drawback of most icon-based techniques is that they cannot visualize data that changes its values continuously over time. In most cases only specific points in time are visualized separately by one glyph. The VIE-VISU-system for example uses 24 glyphs to represent one 24-hour-cycle of measurements. &lt;br /&gt;
Purpose of the Visualization&lt;br /&gt;
&lt;br /&gt;
The visualization should provide an overview over the blood test results both for a concrete test and in variation in time.&lt;br /&gt;
An outstanding task is the elevated focus on values which exceed or undercut the predefined borders. Not only these values need special attention, but as well the values near these borders should be focused in some way.&lt;br /&gt;
The visualization should answer questions like whether the blood values are in the normal range, whether some tendencies exist and whether one or more values should be drawn more attention to.&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
As mentioned above, the tool is mainly intended for doctors, therefore one should be able to use it intuitively.&lt;br /&gt;
The information to emphasize would be :&lt;br /&gt;
&lt;br /&gt;
* the change of a specific blood feature over time&lt;br /&gt;
* when the value of a blood feature goes outside of its reference interval&lt;br /&gt;
&lt;br /&gt;
We also want to keep the table format, because of its convenience when looking up specific values [Few, 2006]. Also, our values have more than one unit of measure, which makes it useless to compare them amongst each other [Few, 2006]. A graph is used for visualizing the values of a specific blood feature over time.&lt;br /&gt;
&lt;br /&gt;
=== Header ===&lt;br /&gt;
&lt;br /&gt;
All screens have a common header with the name of the patient and a time line. The time line shows the dates when blood tests were taken. The user may click on each date and the corresponding data will be shown. &lt;br /&gt;
&lt;br /&gt;
=== Screen 1 ===&lt;br /&gt;
The initial screen shows the data in tabular form. Values which are outside the reference interval are shown on top of the list, colored red and in alphabetical order.&lt;br /&gt;
This makes it easy for the doctor to immediately spot dangerous values. Other values are colored green, also in alphabetical order.&lt;br /&gt;
Upon clicking on the triangle next to a blood feature we get to the next screen.&lt;br /&gt;
&lt;br /&gt;
=== Screen 2 ===&lt;br /&gt;
This screen has a graph showing the various measurements of the selected feature over time. The area of the reference interval is colored green, everything outside of it is red. The selected value has a enlarged dot and is centered on the screen. It is also possible to use the time line to select a different date.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* [Horn et al., 1998] Werner Horn, Christian Popow, and Lukas Unterasinger. Metaphor Graphics to Visualize ICU Data over Time, In Proceedings of Intelligent Data Analysis in Medicine and Pharmacology (IDAMAP-98), Workshop Notes of the ECAI-98 Workshop, 1998.&lt;br /&gt;
* [Few, 2006] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Appendix A - Table and Graph Design at a Glance.&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18361</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18361"/>
		<updated>2007-12-08T07:33:00Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Poor Graphic  ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]&lt;br /&gt;
&lt;br /&gt;
[[Image:Traeume.jpg]] &lt;br /&gt;
&lt;br /&gt;
Frauen träumen sanfter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Data-Ink Ratio ===&lt;br /&gt;
{{Quotation| The goal is to design a display that has the highest possible data-ink ratio (that is, as close to the total of 1.0 or 100% as possible), without eliminating something that is necessary for effective communication. |[Few Article, 2004]}}&lt;br /&gt;
Following this principle unnecessary non-data ink will be removed. Therefore the background picture and the unnecessary graphics will be removed. Furthermore unnecessary data ink will be removed or replaced.&lt;br /&gt;
&lt;br /&gt;
In the next step the most important data should be emphasized. Since the attention of the reader should be drawn on the information that men more often dream about violence and conflicts, whereas women lead in having depressive dreams, this information should be emphasized with some special markup. For example, the bars, which having the dreams of the men ahead, could be colored with a more saturated color.&lt;br /&gt;
&lt;br /&gt;
=== Visual Means to Highlight Data ===&lt;br /&gt;
{{Quotation|  A contrasting version of any visual attribute, rendered differently from the norm — whatever the norm — demands attention. …  Anything different catches our eyes and begs us to assign meaning, to understand the significance of that difference. |[Few Article, 2004]}}&lt;br /&gt;
As mentioned above we want to draw the reader’s attention to the difference between women and men’s dreams. As the most important data in the graphic is that men dream more about violence, this part should be emphasized. Therefore the men’s violence bars could be drawn with a darker color. &lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
{{Quotation|  Non-data ink, consistent with its supporting role, should stand out just enough from the background to serve its purpose but not so much that it draws attention. This can be achieved through the use of thin lines and soft, neutral colors (e.g. light gray). | [Few, 2004]}}&lt;br /&gt;
Following this rule, all the background pictures should be erased, and replaced with some background that does not draw much attention, but serves the purpose of a background.&lt;br /&gt;
&lt;br /&gt;
=== Emphasize the most important data ink ===&lt;br /&gt;
{{Quotation| Regardless of the encoding method, certain visual attributes of objects, words, and numbers stand out more than others.| [Few, 2004]}}&lt;br /&gt;
Hue, Enclosure, Size, Line width and more are attributes which can be used to emphasize the most important data ink. The most important data in our graphic is the relationship between men and women´s dreams. So this part of the graphic should be emphasized.&lt;br /&gt;
&lt;br /&gt;
{{Quotation| Your message may require multiple tables, multiple graphs, or a combination of both, along with additional text in the form of bullet points, sentences, or even whole paragraphs. When you arrange this information on the page or screen, you must do so consciously to tell a story. What should I say first? What should I save for last? … The answers to these questions take on the form of visual attributes designed to accomplish the following:&lt;br /&gt;
* Group the data (i.e., segment the data into meaningful subsets)&lt;br /&gt;
* Prioritize the data (i.e., rank the data by importance)&lt;br /&gt;
* Sequence the data (i.e., give direction for the order in which the data&lt;br /&gt;
.| [Few, 2004]}}&lt;br /&gt;
Since we want to draw the attention to the data which shows the violence data, the order of the data could be changed. That the reader begins at the left, subsequently follows the graph to the right and that his look at the graphic ends with a ‘wow’ effect.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Prioritize the Data ===&lt;br /&gt;
{{Quotation| Whenever you communicate quantitative information, it is imperative that you step back from it and ask yourself, “What are the important numbers here?” Once you´ve established a clear sense of what´s important, you should make that information stand out clearly from the rest.| [Few, 2004]}}&lt;br /&gt;
As mentioned already we want to draw the reader’s attention to the violence dreams. But the data shows as well the interesting point that depressive dreams are underrepresented, at least concerning this survey, in dreams. &lt;br /&gt;
There are some ways to prioritize the data. For this example we think it is useful to concentrate on the hue or a lesser saturation of the depressive bar color.&lt;br /&gt;
&lt;br /&gt;
=== Sequence the Data ===&lt;br /&gt;
The contents of a graphic should be clearly divided into columns, since readers will first scan the left-most column from top-to-bottom, then move to the top of the next column [Few, 2004]. Therefore the 3-dimensional view of the bar chart in the given grapic is unnecessary and even obstructive for the viewer. It should be replaced by a normal 2-dimensional bar chartwith proper labeling. &lt;br /&gt;
&lt;br /&gt;
=== Text ===&lt;br /&gt;
Most of the text in the given graphic satisfies the rules of [Few, 2007]. The labeling of the bars is ok accept that the &amp;quot;%&amp;quot;-sign should be put directly next to the values of each bar. Furthermore the color of the &amp;quot;male&amp;quot;-bar hasn&#039;t been chosen very well since it has not enough contrast to the background. The title of the graphic could be improved also. It doesnt give very much information about the contains of the grapic. &amp;quot;Häufigkeit von Träumen nach Geschlecht&amp;quot; would be a more informative title for example. &lt;br /&gt;
&lt;br /&gt;
==Revised Graphic==&lt;br /&gt;
[[Image:traum.png]] &lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
The following changes were made to fix the issues criticized in previous sections: &lt;br /&gt;
&lt;br /&gt;
* The title was changed. It now gives a more accurate description of the graphic.&lt;br /&gt;
* Unessential and partially disturbing background graphics was removed. The overall image is now much clearer and more readable.&lt;br /&gt;
* The labeling was improved. Unit of the values is now immediately clear.&lt;br /&gt;
* Switched the model from 3D to 2D. Now the graphic can be read off more accurately.&lt;br /&gt;
* Changed the coloring to be distinguishable and still easily readable.&lt;br /&gt;
* Added grid and axis for better orientation.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few Article, 2004] Stephen Few, Elegance Through Simplicity, Article about redesigning graphs, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920, accessed 29.11.2007.&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 7 - General Design for Communication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18358</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18358"/>
		<updated>2007-12-07T22:27:13Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Poor Graphic  ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]&lt;br /&gt;
&lt;br /&gt;
[[Image:Traeume.jpg]] &lt;br /&gt;
&lt;br /&gt;
Frauen träumen sanfter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Data-Ink Ratio ===&lt;br /&gt;
{{Quotation| The goal is to design a display that has the highest possible data-ink ratio (that is, as close to the total of 1.0 or 100% as possible), without eliminating something that is necessary for effective communication. |[Few Article, 2004]}}&lt;br /&gt;
Following this principle unnecessary non-data ink will be removed. Therefore the background picture and the unnecessary graphics will be removed. Furthermore unnecessary data ink will be removed or replaced.&lt;br /&gt;
&lt;br /&gt;
In the next step the most important data should be emphasized. Since the attention of the reader should be drawn on the information that men more often dream about violence and conflicts, whereas women lead in having depressive dreams, this information should be emphasized with some special markup. For example, the bars, which having the dreams of the men ahead, could be colored with a more saturated color.&lt;br /&gt;
&lt;br /&gt;
=== Visual Means to Highlight Data ===&lt;br /&gt;
{{Quotation|  A contrasting version of any visual attribute, rendered differently from the norm — whatever the norm — demands attention. …  Anything different catches our eyes and begs us to assign meaning, to understand the significance of that difference. |[Few Article, 2004]}}&lt;br /&gt;
As mentioned above we want to draw the reader’s attention to the difference between women and men’s dreams. As the most important data in the graphic is that men dream more about violence, this part should be emphasized. Therefore the men’s violence bars could be drawn with a darker color. &lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
{{Quotation|  Non-data ink, consistent with its supporting role, should stand out just enough from the background to serve its purpose but not so much that it draws attention. This can be achieved through the use of thin lines and soft, neutral colors (e.g. light gray). | [Few, 2004]}}&lt;br /&gt;
Following this rule, all the background pictures should be erased, and replaced with some background that does not draw much attention, but serves the purpose of a background.&lt;br /&gt;
&lt;br /&gt;
=== Emphasize the most important data ink ===&lt;br /&gt;
{{Quotation| Regardless of the encoding method, certain visual attributes of objects, words, and numbers stand out more than others.| [Few, 2004]}}&lt;br /&gt;
Hue, Enclosure, Size, Line width and more are attributes which can be used to emphasize the most important data ink. The most important data in our graphic is the relationship between men and women´s dreams. So this part of the graphic should be emphasized.&lt;br /&gt;
&lt;br /&gt;
{{Quotation| Your message may require multiple tables, multiple graphs, or a combination of both, along with additional text in the form of bullet points, sentences, or even whole paragraphs. When you arrange this information on the page or screen, you must do so consciously to tell a story. What should I say first? What should I save for last? … The answers to these questions take on the form of visual attributes designed to accomplish the following:&lt;br /&gt;
* Group the data (i.e., segment the data into meaningful subsets)&lt;br /&gt;
* Prioritize the data (i.e., rank the data by importance)&lt;br /&gt;
* Sequence the data (i.e., give direction for the order in which the data&lt;br /&gt;
.| [Few, 2004]}}&lt;br /&gt;
Since we want to draw the attention to the data which shows the violence data, the order of the data could be changed. That the reader begins at the left, subsequently follows the graph to the right and that his look at the graphic ends with a ‘wow’ effect.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Prioritize the Data ===&lt;br /&gt;
{{Quotation| Whenever you communicate quantitative information, it is imperative that you step back from it and ask yourself, “What are the important numbers here?” Once you´ve established a clear sense of what´s important, you should make that information stand out clearly from the rest.| [Few, 2004]}}&lt;br /&gt;
As mentioned already we want to draw the reader’s attention to the violence dreams. But the data shows as well the interesting point that depressive dreams are underrepresented, at least concerning this survey, in dreams. &lt;br /&gt;
There are some ways to prioritize the data. For this example we think it is useful to concentrate on the hue or a lesser saturation of the depressive bar color.&lt;br /&gt;
&lt;br /&gt;
=== Sequence the Data ===&lt;br /&gt;
The contents of a graphic should be clearly divided into columns, since readers will first scan the left-most column from top-to-bottom, then move to the top of the next column [Few, 2004]. Therefore the 3-dimensional view of the bar chart in the given grapic is unnecessary and even obstructive for the viewer. It should be replaced by a normal 2-dimensional bar chartwith proper labeling. &lt;br /&gt;
&lt;br /&gt;
=== Text ===&lt;br /&gt;
Most of the text in the given graphic satisfies the rules of [Few, 2007]. The labeling of the bars is ok accept that the &amp;quot;%&amp;quot;-sign should be put directly next to the values of each bar. Furthermore the color of the &amp;quot;male&amp;quot;-bar hasn&#039;t been chosen very well since it has not enough contrast to the background. The title of the graphic could be improved also. It doesnt give very much information about the contains of the grapic. &amp;quot;Häufigkeit bestimmter Träume bei Frauen und Männern&amp;quot; would be a more informative title for example. &lt;br /&gt;
&lt;br /&gt;
==Revised Graphic==&lt;br /&gt;
[[Image:traum.png]] &lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
The following changes were made to fix the issues criticized in previous sections: &lt;br /&gt;
&lt;br /&gt;
* The title was changed. It now gives a more accurate description of the graphic.&lt;br /&gt;
* Unessential and partially disturbing background graphics was removed. The overall image is now much clearer and more readable.&lt;br /&gt;
* The labeling was improved. Unit of the values is now immediately clear.&lt;br /&gt;
* Switched the model from 3D to 2D. Now the graphic can be read off more accurately.&lt;br /&gt;
* Changed the coloring to be distinguishable and still easily readable.&lt;br /&gt;
* Added grid and axis for better orientation.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few Article, 2004] Stephen Few, Elegance Through Simplicity, Article about redesigning graphs, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920, accessed 29.11.2007.&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 7 - General Design for Communication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18340</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18340"/>
		<updated>2007-12-07T15:53:26Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Poor Graphic  ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]&lt;br /&gt;
&lt;br /&gt;
[[Image:Traeume.jpg]] &lt;br /&gt;
&lt;br /&gt;
Frauen träumen sanfter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Data-Ink Ratio ===&lt;br /&gt;
{{Quotation| The goal is to design a display that has the highest possible data-ink ratio (that is, as close to the total of 1.0 or 100% as possible), without eliminating something that is necessary for effective communication. |[Few Article, 2004]}}&lt;br /&gt;
Following this principle unnecessary non-data ink will be removed. Therefore the background picture and the unnecessary graphics will be removed. Furthermore unnecessary data ink will be removed or replaced.&lt;br /&gt;
&lt;br /&gt;
In the next step the most important data should be emphasized. Since the attention of the reader should be drawn on the information that men more often dream about violence and conflicts, whereas women lead in having depressive dreams, this information should be emphasized with some special markup. For example, the bars, which having the dreams of the men ahead, could be colored with a more saturated color.&lt;br /&gt;
&lt;br /&gt;
=== Visual Means to Highlight Data ===&lt;br /&gt;
{{Quotation|  A contrasting version of any visual attribute, rendered differently from the norm — whatever the norm — demands attention. …  Anything different catches our eyes and begs us to assign meaning, to understand the significance of that difference. |[Few Article, 2004]}}&lt;br /&gt;
As mentioned above we want to draw the reader’s attention to the difference between women and men’s dreams. As the most important data in the graphic is that men dream more about violence, this part should be emphasized. Therefore the men’s violence bars could be drawn with a darker color. &lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
{{Quotation|  Non-data ink, consistent with its supporting role, should stand out just enough from the background to serve its purpose but not so much that it draws attention. This can be achieved through the use of thin lines and soft, neutral colors (e.g. light gray). | [Few, 2004]}}&lt;br /&gt;
Following this rule, all the background pictures should be erased, and replaced with some background that does not draw much attention, but serves the purpose of a background.&lt;br /&gt;
&lt;br /&gt;
=== Emphasize the most important data ink ===&lt;br /&gt;
{{Quotation| Regardless of the encoding method, certain visual attributes of objects, words, and numbers stand out more than others.| [Few, 2004]}}&lt;br /&gt;
Hue, Enclosure, Size, Line width and more are attributes which can be used to emphasize the most important data ink. The most important data in our graphic is the relationship between men and women´s dreams. So this part of the graphic should be emphasized.&lt;br /&gt;
&lt;br /&gt;
{{Quotation| Your message may require multiple tables, multiple graphs, or a combination of both, along with additional text in the form of bullet points, sentences, or even whole paragraphs. When you arrange this information on the page or screen, you must do so consciously to tell a story. What should I say first? What should I save for last? … The answers to these questions take on the form of visual attributes designed to accomplish the following:&lt;br /&gt;
* Group the data (i.e., segment the data into meaningful subsets)&lt;br /&gt;
* Prioritize the data (i.e., rank the data by importance)&lt;br /&gt;
* Sequence the data (i.e., give direction for the order in which the data&lt;br /&gt;
.| [Few, 2004]}}&lt;br /&gt;
Since we want to draw the attention to the data which shows the violence data, the order of the data could be changed. That the reader begins at the left, subsequently follows the graph to the right and that his look at the graphic ends with a ‘wow’ effect.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Prioritize the Data ===&lt;br /&gt;
{{Quotation| Whenever you communicate quantitative information, it is imperative that you step back from it and ask yourself, “What are the important numbers here?” Once you´ve established a clear sense of what´s important, you should make that information stand out clearly from the rest.| [Few, 2004]}}&lt;br /&gt;
As mentioned already we want to draw the reader’s attention to the violence dreams. But the data shows as well the interesting point that depressive dreams are underrepresented, at least concerning this survey, in dreams. &lt;br /&gt;
There are some ways to prioritize the data. For this example we think it is useful to concentrate on the hue or a lesser saturation of the depressive bar color.&lt;br /&gt;
&lt;br /&gt;
=== Sequence the Data ===&lt;br /&gt;
The contents of a graphic should be clearly divided into columns, since readers will first scan the left-most column from top-to-bottom, then move to the top of the next column [Few, 2004]. Therefore the 3-dimensional view of the bar chart in the given grapic is unnecessary and even obstructive for the viewer. It should be replaced by a normal 2-dimensional bar chartwith proper labeling. &lt;br /&gt;
&lt;br /&gt;
=== Text ===&lt;br /&gt;
Most of the text in the given graphic satisfies the rules of [Few, 2007]. The labeling of the bars is ok accept that the &amp;quot;%&amp;quot;-sign should be put directly next to the values of each bar. Furthermore the color of the &amp;quot;male&amp;quot;-bar hasn&#039;t been chosen very well since it has not enough contrast to the background. The title of the graphic could be improved also. It doesnt give very much information about the contains of the grapic. &amp;quot;Häufigkeit bestimmter Träume bei Frauen und Männern&amp;quot; would be a more informative title for example. &lt;br /&gt;
&lt;br /&gt;
==Revised Graphic==&lt;br /&gt;
[[Image:traum.png]] &lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
The following changes were made to fix the issues criticized in previous sections: &lt;br /&gt;
&lt;br /&gt;
* The title was changed. It now gives a more accurate description of the graphic.&lt;br /&gt;
* Unessential and partially disturbing background graphics was removed. The overall image is now much clearer and more readable.&lt;br /&gt;
* The labeling was improved. Unit of the values is now immediately clear.&lt;br /&gt;
* Switched the model from 3D to 2D. Now the graphic can be read off more accurately.&lt;br /&gt;
* Changed the coloring to be distinguishable and still easily readable.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few Article, 2004] Stephen Few, Elegance Through Simplicity, Article about redesigning graphs, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920, accessed 29.11.2007.&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 7 - General Design for Communication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18337</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_3&amp;diff=18337"/>
		<updated>2007-12-07T15:07:18Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Poor Graphic  ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]&lt;br /&gt;
&lt;br /&gt;
[[Image:Traeume.jpg]] &lt;br /&gt;
&lt;br /&gt;
Frauen träumen sanfter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Data-Ink Ratio ===&lt;br /&gt;
{{Quotation| The goal is to design a display that has the highest possible data-ink ratio (that is, as close to the total of 1.0 or 100% as possible), without eliminating something that is necessary for effective communication. |[Few Article, 2004]}}&lt;br /&gt;
Following this principle unnecessary non-data ink will be removed. Therefore the background picture and the unnecessary graphics will be removed. Furthermore unnecessary data ink will be removed or replaced.&lt;br /&gt;
&lt;br /&gt;
In the next step the most important data should be emphasized. Since the attention of the reader should be drawn on the information that men more often dream about violence and conflicts, whereas women lead in having depressive dreams, this information should be emphasized with some special markup. For example, the bars, which having the dreams of the men ahead, could be colored with a more saturated color.&lt;br /&gt;
&lt;br /&gt;
=== Visual Means to Highlight Data ===&lt;br /&gt;
{{Quotation|  A contrasting version of any visual attribute, rendered differently from the norm — whatever the norm — demands attention. …  Anything different catches our eyes and begs us to assign meaning, to understand the significance of that difference. |[Few Article, 2004]}}&lt;br /&gt;
As mentioned above we want to draw the reader’s attention to the difference between women and men’s dreams. As the most important data in the graphic is that men dream more about violence, this part should be emphasized. Therefore the men’s violence bars could be drawn with a darker color. &lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
{{Quotation|  Non-data ink, consistent with its supporting role, should stand out just enough from the background to serve its purpose but not so much that it draws attention. This can be achieved through the use of thin lines and soft, neutral colors (e.g. light gray). | [Few, 2004]}}&lt;br /&gt;
Following this rule, all the background pictures should be erased, and replaced with some background that does not draw much attention, but serves the purpose of a background.&lt;br /&gt;
&lt;br /&gt;
=== Emphasize the most important data ink ===&lt;br /&gt;
{{Quotation| Regardless of the encoding method, certain visual attributes of objects, words, and numbers stand out more than others.| [Few, 2004]}}&lt;br /&gt;
Hue, Enclosure, Size, Line width and more are attributes which can be used to emphasize the most important data ink. The most important data in our graphic is the relationship between men and women´s dreams. So this part of the graphic should be emphasized.&lt;br /&gt;
&lt;br /&gt;
{{Quotation| Your message may require multiple tables, multiple graphs, or a combination of both, along with additional text in the form of bullet points, sentences, or even whole paragraphs. When you arrange this information on the page or screen, you must do so consciously to tell a story. What should I say first? What should I save for last? … The answers to these questions take on the form of visual attributes designed to accomplish the following:&lt;br /&gt;
* Group the data (i.e., segment the data into meaningful subsets)&lt;br /&gt;
* Prioritize the data (i.e., rank the data by importance)&lt;br /&gt;
* Sequence the data (i.e., give direction for the order in which the data&lt;br /&gt;
.| [Few, 2004]}}&lt;br /&gt;
Since we want to draw the attention to the data which shows the violence data, the order of the data could be changed. That the reader begins at the left, subsequently follows the graph to the right and that his look at the graphic ends with a ‘wow’ effect.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Prioritize the Data ===&lt;br /&gt;
{{Quotation| Whenever you communicate quantitative information, it is imperative that you step back from it and ask yourself, “What are the important numbers here?” Once you´ve established a clear sense of what´s important, you should make that information stand out clearly from the rest.| [Few, 2004]}}&lt;br /&gt;
As mentioned already we want to draw the reader’s attention to the violence dreams. But the data shows as well the interesting point that depressive dreams are underrepresented, at least concerning this survey, in dreams. &lt;br /&gt;
There are some ways to prioritize the data. For this example we think it is useful to concentrate on the hue or a lesser saturation of the depressive bar color.&lt;br /&gt;
&lt;br /&gt;
=== Sequence the Data ===&lt;br /&gt;
The contents of a graphic should be clearly divided into columns, since readers will first scan the left-most column from top-to-bottom, then move to the top of the next column [Few, 2004]. Therefore the 3-dimensional view of the bar chart in the given grapic is unnecessary and even obstructive for the viewer. It should be replaced by a normal 2-dimensional bar chartwith proper labeling. &lt;br /&gt;
&lt;br /&gt;
=== Text ===&lt;br /&gt;
Most of the text in the given graphic satisfies the rules of [Few, 2007]. The labeling of the bars is ok accept that the &amp;quot;%&amp;quot;-sign should be put directly next to the values of each bar. Furthermore the color of the &amp;quot;male&amp;quot;-bar hasn&#039;t been chosen very well since it has not enough contrast to the background. The title of the graphic could be improved also. It doesnt give very much information about the contains of the grapic. &amp;quot;Häufigkeit bestimmter Träume bei Frauen und Männern&amp;quot; would be a more informative title for example. &lt;br /&gt;
&lt;br /&gt;
==Revised Graphics==&lt;br /&gt;
[[Image:traum.png]] &lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few Article, 2004] Stephen Few, Elegance Through Simplicity, Article about redesigning graphs, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920, accessed 29.11.2007.&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 7 - General Design for Communication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Traum.png&amp;diff=18333</id>
		<title>File:Traum.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Traum.png&amp;diff=18333"/>
		<updated>2007-12-07T14:52:47Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: == Summary ==  == Copyright status ==  == Source ==&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Whirlwind.jpg&amp;diff=18135</id>
		<title>File:Whirlwind.jpg</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Whirlwind.jpg&amp;diff=18135"/>
		<updated>2007-11-24T19:33:27Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Image of whirlwind display&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;br /&gt;
[Carlsson, 2006] Author Unknown, W. Carlson, A Critical History of Computer Graphics and Animation, Retrieved at: November 8, 2007. http://design.osu.edu/carlson/history/lesson2.html&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=18134</id>
		<title>File:Pov ray.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=18134"/>
		<updated>2007-11-24T19:19:09Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
An image created by using POV-Ray 3.6.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
Public domain&lt;br /&gt;
== Source ==&lt;br /&gt;
[Tran, 2006] G. Tran, English Wikipedia project, Retrieved at: November 8, http://commons.wikimedia.org/wiki/Image:Glasses_800_edit.png&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=18133</id>
		<title>File:Pov ray.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=18133"/>
		<updated>2007-11-24T19:18:18Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
An image created by using POV-Ray 3.6.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
Public domain&lt;br /&gt;
== Source ==&lt;br /&gt;
[Tran, 2005] G. Tran, English Wikipedia project, Retrieved at: November 8, http://commons.wikimedia.org/wiki/Image:Glasses_800_edit.png&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=18132</id>
		<title>File:Utah teapot.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=18132"/>
		<updated>2007-11-24T19:15:08Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
The Utah teapot.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
This image has been released into the public domain by its author, Finlay McWalter at the English Wikipedia project.&lt;br /&gt;
== Source ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[McWalter, 2005] Finlay McWalter, English Wikipedia project, Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Image:Utah_teapot.png&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=18131</id>
		<title>File:Utah teapot.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=18131"/>
		<updated>2007-11-24T19:13:47Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
The Utah teapot.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
This image has been released into the public domain by its author, Finlay McWalter at the English Wikipedia project.&lt;br /&gt;
== Source ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[McWalter, 2005] Finlay McWalter, English Wikipedia project, http://en.wikipedia.org/wiki/Image:Utah_teapot.png&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=18130</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=18130"/>
		<updated>2007-11-24T18:57:19Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Goodchild, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Computer Graphics may be divided into four major categories: &lt;br /&gt;
===Geometry===&lt;br /&gt;
The subfield of Geometry studies ways to represent and process surfaces. Boundary representations are most commonly used, because the appearance of an object depends mainly on its exterior. Although &amp;lt;b&amp;gt;point-based&amp;lt;/b&amp;gt; representations have been getting more and more popular lately, &amp;lt;b&amp;gt;polygonal meshes&amp;lt;/b&amp;gt; are still the most popular form of discrete digital approximation of surfaces. These representations are &amp;lt;b&amp;gt;Lagrangian&amp;lt;/b&amp;gt; (the spatial locations of the samples are independent) as opposed to &amp;lt;b&amp;gt;Eulerian&amp;lt;/b&amp;gt; surface descriptions (i.e., where spatial samples are fixed) which are mainly used for deforming surfaces which undergo many topological changes (e.g. fluids). A subfield of Geometry called &amp;lt;b&amp;gt;Imaging&amp;lt;/b&amp;gt; studies the process of &amp;lt;b&amp;gt;image acquisition&amp;lt;/b&amp;gt; and &amp;lt;b&amp;gt;image editing&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Animation===&lt;br /&gt;
This subfield of Geometry studies ways to represent and manipulate motion. Historically most interest has been focused on &amp;lt;b&amp;gt;parametric&amp;lt;/b&amp;gt; and &amp;lt;b&amp;gt;data-driven models&amp;lt;/b&amp;gt;, but in recent years &amp;lt;b&amp;gt;physical simulation&amp;lt;/b&amp;gt; has experienced a renaissance due to the growing computational capacity of modern machines.&lt;br /&gt;
===Rendering===&lt;br /&gt;
This subfield of Geometry studies algorithms to reproduce light transport. It does so by converting a model into an image by simulating light transport to get physically-based photorealistic images, or by applying a style as in non-photorealistic rendering. Two basic operations in realistic rendering are &amp;lt;b&amp;gt;transport&amp;lt;/b&amp;gt; (how much light gets from one place to another) and &amp;lt;b&amp;gt;scattering&amp;lt;/b&amp;gt; (how surfaces interact with light).&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:whirlwind.jpg |thumb|200px|Whirlwind displays aircraft positions and auxiliary information.]]&lt;br /&gt;
In the &amp;lt;b&amp;gt;60&#039;s&amp;lt;/b&amp;gt;, Jack Bresenham published how to draw lines on a raster device. He later extended this to circles. Larry Roberts pointed out the usefulness of homogeneous coordinates, 4x4 matrices and hidden line detection algorithms. Steve Coons introduced parametric surfaces and developed early computer aided geometric design concepts. The earlier work of Pierre Bézier on parametric curves and surfaces also became public. &lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;70&#039;s&amp;lt;/b&amp;gt;, rendering (shading) was discovered by Gouraud and Phong at the University of Utah. Turned Whitted developed recursive ray tracing which became the standard for photorealism. One of the first displays of computer animation was Futureworld (1976), which included an animation of a human face and hand — produced by Ed Catmull and Fred Parke also at the University of Utah.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;80&#039;s&amp;lt;/b&amp;gt;, Jim Blinn introduced blobby models and texture mapping concepts. Binary space partitioning (BSP) trees were introduced as a data structure. Loren Carpenter started exploring fractals in computer graphics. Postscript was developed by John Warnock.Steve Cook introduced stochastic sampling to ray tracing. Video arcade games took off.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;90&#039;s&amp;lt;/b&amp;gt;, Mosaic, the first graphical Internet browser was written. OpenGL became the standard for graphics APIs.Dynamical systems (physically based modeling) that allowed animation with collisions, gravity, friction, and cause and effects were introduced. Surface subdivision algorithms were rediscovered. Wavelets begin to be used in computer graphics. Image based rendering became the area for research in photo-realistic graphics.&lt;br /&gt;
==Application==&lt;br /&gt;
[[Image:Pov_ray.png|thumb|300px|Glasses (created by using POV-Ray 3.6).]]&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
[http://www.imdb.com/title/tt0074559/ Futureworld at the Internet Movie Database]&amp;lt;br&amp;gt;&lt;br /&gt;
[http://www.siggraph.org/ ACM SIGGRAPH]&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Goodchild, 2007] T. Goodchild, Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=18129</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=18129"/>
		<updated>2007-11-24T18:31:29Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Wikipedia, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Computer Graphics may be divided into four major categories: &lt;br /&gt;
===Geometry===&lt;br /&gt;
The subfield of Geometry studies ways to represent and process surfaces. Boundary representations are most commonly used, because the appearance of an object depends mainly on its exterior. Although &amp;lt;b&amp;gt;point-based&amp;lt;/b&amp;gt; representations have been getting more and more popular lately, &amp;lt;b&amp;gt;polygonal meshes&amp;lt;/b&amp;gt; are still the most popular form of discrete digital approximation of surfaces. These representations are &amp;lt;b&amp;gt;Lagrangian&amp;lt;/b&amp;gt; (the spatial locations of the samples are independent) as opposed to &amp;lt;b&amp;gt;Eulerian&amp;lt;/b&amp;gt; surface descriptions (i.e., where spatial samples are fixed) which are mainly used for deforming surfaces which undergo many topological changes (e.g. fluids). A subfield of Geometry called &amp;lt;b&amp;gt;Imaging&amp;lt;/b&amp;gt; studies the process of &amp;lt;b&amp;gt;image acquisition&amp;lt;/b&amp;gt; and &amp;lt;b&amp;gt;image editing&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Animation===&lt;br /&gt;
This subfield of Geometry studies ways to represent and manipulate motion. Historically most interest has been focused on &amp;lt;b&amp;gt;parametric&amp;lt;/b&amp;gt; and &amp;lt;b&amp;gt;data-driven models&amp;lt;/b&amp;gt;, but in recent years &amp;lt;b&amp;gt;physical simulation&amp;lt;/b&amp;gt; has experienced a renaissance due to the growing computational capacity of modern machines.&lt;br /&gt;
===Rendering===&lt;br /&gt;
This subfield of Geometry studies algorithms to reproduce light transport. It does so by converting a model into an image by simulating light transport to get physically-based photorealistic images, or by applying a style as in non-photorealistic rendering. Two basic operations in realistic rendering are &amp;lt;b&amp;gt;transport&amp;lt;/b&amp;gt; (how much light gets from one place to another) and &amp;lt;b&amp;gt;scattering&amp;lt;/b&amp;gt; (how surfaces interact with light).&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:whirlwind.jpg |thumb|200px|Whirlwind displays aircraft positions and auxiliary information.]]&lt;br /&gt;
In the &amp;lt;b&amp;gt;60&#039;s&amp;lt;/b&amp;gt;, Jack Bresenham published how to draw lines on a raster device. He later extended this to circles. Larry Roberts pointed out the usefulness of homogeneous coordinates, 4x4 matrices and hidden line detection algorithms. Steve Coons introduced parametric surfaces and developed early computer aided geometric design concepts. The earlier work of Pierre Bézier on parametric curves and surfaces also became public. &lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;70&#039;s&amp;lt;/b&amp;gt;, rendering (shading) was discovered by Gouraud and Phong at the University of Utah. Turned Whitted developed recursive ray tracing which became the standard for photorealism. One of the first displays of computer animation was Futureworld (1976), which included an animation of a human face and hand — produced by Ed Catmull and Fred Parke also at the University of Utah.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;80&#039;s&amp;lt;/b&amp;gt;, Jim Blinn introduced blobby models and texture mapping concepts. Binary space partitioning (BSP) trees were introduced as a data structure. Loren Carpenter started exploring fractals in computer graphics. Postscript was developed by John Warnock.Steve Cook introduced stochastic sampling to ray tracing. Video arcade games took off.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;90&#039;s&amp;lt;/b&amp;gt;, Mosaic, the first graphical Internet browser was written. OpenGL became the standard for graphics APIs.Dynamical systems (physically based modeling) that allowed animation with collisions, gravity, friction, and cause and effects were introduced. Surface subdivision algorithms were rediscovered. Wavelets begin to be used in computer graphics. Image based rendering became the area for research in photo-realistic graphics.&lt;br /&gt;
==Application==&lt;br /&gt;
[[Image:Pov_ray.png|thumb|300px|Glasses (created by using POV-Ray 3.6).]]&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
[http://www.imdb.com/title/tt0074559/ Futureworld at the Internet Movie Database]&amp;lt;br&amp;gt;&lt;br /&gt;
[http://www.siggraph.org/ ACM SIGGRAPH]&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18026</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18026"/>
		<updated>2007-11-21T13:30:42Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Aufgabenstellung ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]&lt;br /&gt;
&lt;br /&gt;
=== Zu beurteilende Tabelle ===&lt;br /&gt;
&lt;br /&gt;
[[Image:tufte_2006_beautiful-evidence_funds.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Structural Components of Tables ===&lt;br /&gt;
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Tables generally work best when they also contain additional text that is used to complement the categorical subdivisions and quantitative values in various ways. In Chapter 7, General Design for Communication, we noted that additional text can do the following:&lt;br /&gt;
* Label&lt;br /&gt;
* Introduce&lt;br /&gt;
* Explain&lt;br /&gt;
* Reinforce&lt;br /&gt;
* Highlight&lt;br /&gt;
* Sequence&lt;br /&gt;
* Recommend&lt;br /&gt;
* Inquire&lt;br /&gt;
|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The table tries to explain its data with some text. &lt;br /&gt;
&lt;br /&gt;
The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.&lt;br /&gt;
&lt;br /&gt;
It states labels for the ASSETS and the FUND columns. These column headers label the information below them and should be separated from the data with a horizontal line. &lt;br /&gt;
&lt;br /&gt;
The return values are clearly grouped with the spanner header RETURN.  Maybe it should be stated that this is the return on investment. &lt;br /&gt;
Below the RETURN spanner header we find column headers which state the period for which the data is valid. These should be separated from the data with a horizontal line. Furthermore it is not absolutely clear what there meaning is, and the mixing of so different periods makes it more difficult to understand the table. For example it would be interesting which 3 year period the 3-YR column covers. &lt;br /&gt;
&lt;br /&gt;
The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.&lt;br /&gt;
&lt;br /&gt;
The table does not try to focus my interest to a special area, because no area is specially highlighted. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Delineating columns and rows ===&lt;br /&gt;
{{Quotation|The design process involves several decisions regarding the layout of columns and rows to provide a structure that is easy and efficient to read and understand. Readers should be able to scan quickly through the content to find what they need and perhaps make localized comparisons of related numbers. |[Few, 2004]}}&lt;br /&gt;
{{Definition|Columns and rows are delineated through&lt;br /&gt;
* White space&lt;br /&gt;
*  Rules and grids&lt;br /&gt;
*  Fill color &lt;br /&gt;
.}}&lt;br /&gt;
&lt;br /&gt;
==== White space ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
It is not possible to read the rows without difficulty because the vertical white space between them is pretty small. Therefore it is recommended that the vertical white space between the rows is increased. &lt;br /&gt;
&lt;br /&gt;
As well the horizontal white space between the columns should be increased to ease the reading of the columns. From my point of view, the comparison of the funds is the most interesting information in this table. To lead the reader to scan down the columns, it is advisable to pronounce the white space between the columns more than the one between the rows. &lt;br /&gt;
&lt;br /&gt;
To make a clear distinction between row headers and data, the horizontal white space should be increased between these two parts. As well the horizontal white space between the ASSETS and FUND column should be increased a bit to make a clear distinction.&lt;br /&gt;
&lt;br /&gt;
==== Rules and grids ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Despite the uselessness of grids and the limited usefulness of rules to delineate columns and rows in tables, they are sometimes useful for grouping or highlighting subsets of data. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
In order to make the table more readable it is advisable to draw a line between the column headers and the data.&lt;br /&gt;
&lt;br /&gt;
If the table is in its original context surrounded with some objects where there should be a clear distinction, thin lines could be drawn on each side. Remember to keep the lines as thin and light as possible.   &lt;br /&gt;
&lt;br /&gt;
A combination of horizontal and vertical rules could be used if there is an area of special interest.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Fill color ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When white space alone can´t be used to effectively delineate columns and rows in tables, fill shades and hues work better than grids and rules. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this quotation the rows of the table could be separated with fill shades. It would also be possible to delineate the headers in the table as separate groups of information in using fill colors.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging data ===&lt;br /&gt;
&lt;br /&gt;
==== Columns or rows ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Some sequential relationships are more easily understood when they are arranged in a particular way, either horizontally from left to right or vertically from top to bottom. … We naturally think of time as moving from left to right, rather than down from top to bottom. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.  &lt;br /&gt;
&lt;br /&gt;
The time is illustrated from left to right, but the relations between the columns are not clear at all. &lt;br /&gt;
&lt;br /&gt;
==== Groups and breaks ====&lt;br /&gt;
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.&lt;br /&gt;
&lt;br /&gt;
For example make a table for the year 2003 till 2007. Or make a table showing the quarters in the year 2003. Everything is possible, but it should be consistent. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Columns sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Columns containing sets of quantitative values that you want your readers to compare easily should be placed as close to one another as possible. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this principle the table puts the values near together which should be easily comparable.&lt;br /&gt;
&lt;br /&gt;
The table shows the returns in percentage and the reader can easily compare the percentages. &lt;br /&gt;
&lt;br /&gt;
==== Data sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When you need to sequence numbers, their quantitative order, either ascending or descending, is the only useful way to sequence them. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The funds are listed descending concerning their assets. Since the asset of a fund is one of the most important characteristics and the assets are listed in numbers, it is useful to list the funds in their quantitative order.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Formatting text ===&lt;br /&gt;
&lt;br /&gt;
==== Orientation ====&lt;br /&gt;
{{Quotation|As speakers of English, we are accustomed to reading language from left to right, arranged horizontally. |[Few, 2004]}}&lt;br /&gt;
The orientation of all text in the given table is optimal. &lt;br /&gt;
&lt;br /&gt;
==== Alignment ====&lt;br /&gt;
In most cases convetions are used to determine the alignment of text. Few explains three of them as follows:&lt;br /&gt;
{{Quotation|&lt;br /&gt;
* Numbers that represent quantitative values, as opposed to those that are merely identifiers (e.g., customer numbers), should always be aligned to the right. &lt;br /&gt;
* Dates are best aligned to the left, using a format that keeps the number of characters in each portion of the date (i.e., month, day, and year) constant.&lt;br /&gt;
* Text that expresses neither numbers nor dates works best when aligned to the left. |[Few, 2004]}}&lt;br /&gt;
The given table satisfies the first rule. All numbers that represent quantitive values are aligned to the right, namely the columns &#039;ASSETS&#039; and &#039;RETURN&#039;. Also the thrid rule is satisfied since the text in the &#039;FUND&#039; column is aligned to the left.&lt;br /&gt;
&lt;br /&gt;
==== Number and date format ====&lt;br /&gt;
{{Quotation|&lt;br /&gt;
* Numbers include no unnecessary information (e.g., excessive levels of precision)&lt;br /&gt;
* They express the data using the format that is most familiar to its readers. |[Few, 2004]}}&lt;br /&gt;
The number format of the given table is very good. There is a comma to the left of the first three whole-number digits in the &#039;ASSETS&#039; column. Also in the &#039;RETURN&#039; column alls positive and negative values are tagged by a + or a - sign.&lt;br /&gt;
But there is a small shortcoming: The % and $ sign is only shown once in every column. This should be placed immediately next to every dollar or percentage value.&lt;br /&gt;
&lt;br /&gt;
==== Number and date precision ====&lt;br /&gt;
{{Quotation|The level of precision should not exceed the level needed to server your communication objectives and the needs of your readers. |[Few, 2004]}}&lt;br /&gt;
The level of precision in the &#039;ASSETS&#039; column is a little bit too high. The first two digits do not communicate very important information. When talking about 20- to 70-thousand dollars, fifty dollars more less don&#039;t make a noteworthy difference. &lt;br /&gt;
&lt;br /&gt;
==== Fonts ====&lt;br /&gt;
==== Emphasis ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Summarizing values ===&lt;br /&gt;
{{Quotation|Summary values give your readers an overview in a single glance, and if they wish, they can then dig into the detailed values.&lt;br /&gt;
This is a very powerful path to understanding, moving from general to specific, macroscopic to microscopic, summary to detail.|[Few, 2004]}} &lt;br /&gt;
&lt;br /&gt;
This table currently does not contain any summarizing values.&lt;br /&gt;
&lt;br /&gt;
==== Column summary values ====&lt;br /&gt;
{{Quotation|A value that aggregates an entire column of values is a column summary, which generally appears in a separate row beneath the last row of detailed values.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
For each column under the &#039;RETURN&#039; spanner header it could be useful to provide the median of gain/loss values. It is unclear though, whether this information is desirable at all (due to lack of domain knowledge).&lt;br /&gt;
&lt;br /&gt;
==== Row summary values ====&lt;br /&gt;
{{Quotation|A value that aggregates an entire row of values is a row summary, which generally appears in a separate column to the right of the last column of detailed values.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The detailed values in columns beneath the &#039;RETURN&#039; spanner header seem to be cumulative across a row (Assumption based on the cryptic column titles). That is why there doesn&#039;t seem to be much sense in providing a separate summary values for each row (i.e for each fund).&lt;br /&gt;
==== Group summary values ====&lt;br /&gt;
{{Quotation|Group summary values [..] summarize meaningful subsets of values rather than the entire&lt;br /&gt;
set of values throughout the column or row.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Given only the information provided in the table, there is no plausible grouping possible. The only possible grouping, using only the provided data, would be one by intervals of assets (in Millions of Dollars) or gain/loss percentage intervals. However (possibly due to our lack of domain knowledge) these groupings don&#039;t seem reasonable.&lt;br /&gt;
==== Header versus footers ====&lt;br /&gt;
{{Quotation|When the summary values are more important to your message or to your readers than the details, and placing them below the details would make them&lt;br /&gt;
harder and less efficient to find, it often makes sense to place them in headers even though this is less conventional.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
In our case the summary values denote complementary information, therefore their position in the footer seems appropriate.&lt;br /&gt;
=== Page information ===&lt;br /&gt;
{{Quotation|Because of short-term memory constraints, effective table design requires that certain information be repeated on each new page. Otherwise, your readers may lose track of information that they need to interpret the table as they move from page to page. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Our table is not split into multiple pages, therefore this aspect is not applicable here.&lt;br /&gt;
==== Repeated column headers ====&lt;br /&gt;
{{Quotation|When tables extend onto multiple pages, the columns are no longer labeled after the first page unless you repeat the column headers on each.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The proper way of handling tables spreading across multiple pages would be to copy the table headers on top of each page. However, in our case this is not necessary.&lt;br /&gt;
==== Repeated row headers ====&lt;br /&gt;
{{Quotation|[...] even those of us who are careful to repeat column headers on each page seldom think to repeat the row headers as well, yet the problem is the same.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
This principle is applicable when multiple rows, which spread across multiple pages, are grouped together and have one title column where the title printed only for the first row of the group. The correct way of designing such a table would be to re-print the title on the first row on each page. Again, this is of no concern to our table here.&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 8 - Table Design.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18017</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18017"/>
		<updated>2007-11-20T13:36:29Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Aufgabenstellung ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]&lt;br /&gt;
&lt;br /&gt;
=== Zu beurteilende Tabelle ===&lt;br /&gt;
&lt;br /&gt;
[[Image:tufte_2006_beautiful-evidence_funds.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Structural Components of Tables ===&lt;br /&gt;
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Tables generally work best when they also contain additional text that is used to complement the categorical subdivisions and quantitative values in various ways. In Chapter 7, General Design for Communication, we noted that additional text can do the following:&lt;br /&gt;
* Label&lt;br /&gt;
* Introduce&lt;br /&gt;
* Explain&lt;br /&gt;
* Reinforce&lt;br /&gt;
* Highlight&lt;br /&gt;
* Sequence&lt;br /&gt;
* Recommend&lt;br /&gt;
* Inquire&lt;br /&gt;
|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The table tries to explain its data with some text. &lt;br /&gt;
&lt;br /&gt;
The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.&lt;br /&gt;
&lt;br /&gt;
It states labels for the ASSETS and the FUND columns. These column headers label the information below them and should be separated from the data with a horizontal line. &lt;br /&gt;
&lt;br /&gt;
The return values are clearly grouped with the spanner header RETURN.  Maybe it should be stated that this is the return on investment. &lt;br /&gt;
Below the RETURN spanner header we find column headers which state the period for which the data is valid. These should be separated from the data with a horizontal line. Furthermore it is not absolutely clear what there meaning is, and the mixing of so different periods makes it more difficult to understand the table. For example it would be interesting which 3 year period the 3-YR column covers. &lt;br /&gt;
&lt;br /&gt;
The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.&lt;br /&gt;
&lt;br /&gt;
The table does not try to focus my interest to a special area, because no area is specially highlighted. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Delineating columns and rows ===&lt;br /&gt;
{{Quotation|The design process involves several decisions regarding the layout of columns and rows to provide a structure that is easy and efficient to read and understand. Readers should be able to scan quickly through the content to find what they need and perhaps make localized comparisons of related numbers. |[Few, 2004]}}&lt;br /&gt;
{{Definition|Columns and rows are delineated through&lt;br /&gt;
* White space&lt;br /&gt;
*  Rules and grids&lt;br /&gt;
*  Fill color &lt;br /&gt;
.}}&lt;br /&gt;
&lt;br /&gt;
==== White space ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
It is not possible to read the rows without difficulty because the vertical white space between them is pretty small. Therefore it is recommended that the vertical white space between the rows is increased. &lt;br /&gt;
&lt;br /&gt;
As well the horizontal white space between the columns should be increased to ease the reading of the columns. From my point of view, the comparison of the funds is the most interesting information in this table. To lead the reader to scan down the columns, it is advisable to pronounce the white space between the columns more than the one between the rows. &lt;br /&gt;
&lt;br /&gt;
To make a clear distinction between row headers and data, the horizontal white space should be increased between these two parts. As well the horizontal white space between the ASSETS and FUND column should be increased a bit to make a clear distinction.&lt;br /&gt;
&lt;br /&gt;
==== Rules and grids ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Despite the uselessness of grids and the limited usefulness of rules to delineate columns and rows in tables, they are sometimes useful for grouping or highlighting subsets of data. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
In order to make the table more readable it is advisable to draw a line between the column headers and the data.&lt;br /&gt;
&lt;br /&gt;
If the table is in its original context surrounded with some objects where there should be a clear distinction, thin lines could be drawn on each side. Remember to keep the lines as thin and light as possible.   &lt;br /&gt;
&lt;br /&gt;
A combination of horizontal and vertical rules could be used if there is an area of special interest.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Fill color ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When white space alone can´t be used to effectively delineate columns and rows in tables, fill shades and hues work better than grids and rules. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this quotation the rows of the table could be separated with fill shades. It would also be possible to delineate the headers in the table as separate groups of information in using fill colors.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging data ===&lt;br /&gt;
&lt;br /&gt;
==== Columns or rows ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Some sequential relationships are more easily understood when they are arranged in a particular way, either horizontally from left to right or vertically from top to bottom. … We naturally think of time as moving from left to right, rather than down from top to bottom. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.  &lt;br /&gt;
&lt;br /&gt;
The time is illustrated from left to right, but the relations between the columns are not clear at all. &lt;br /&gt;
&lt;br /&gt;
==== Groups and breaks ====&lt;br /&gt;
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.&lt;br /&gt;
&lt;br /&gt;
For example make a table for the year 2003 till 2007. Or make a table showing the quarters in the year 2003. Everything is possible, but it should be consistent. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Columns sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Columns containing sets of quantitative values that you want your readers to compare easily should be placed as close to one another as possible. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this principle the table puts the values near together which should be easily comparable.&lt;br /&gt;
&lt;br /&gt;
The table shows the returns in percentage and the reader can easily compare the percentages. &lt;br /&gt;
&lt;br /&gt;
==== Data sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When you need to sequence numbers, their quantitative order, either ascending or descending, is the only useful way to sequence them. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The funds are listed descending concerning their assets. Since the asset of a fund is one of the most important characteristics and the assets are listed in numbers, it is useful to list the funds in their quantitative order.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Formatting text ===&lt;br /&gt;
==== Orientation ====&lt;br /&gt;
==== Alignment ====&lt;br /&gt;
==== Number and date format ====&lt;br /&gt;
==== Number and date precision ====&lt;br /&gt;
==== Fonts ====&lt;br /&gt;
==== Emphasis ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Summarizing values ===&lt;br /&gt;
{{Quotation|Summary values give your readers an overview in a single glance, and if they wish, they can then dig into the detailed values.&lt;br /&gt;
This is a very powerful path to understanding, moving from general to specific, macroscopic to microscopic, summary to detail.|[Few, 2004]}} &lt;br /&gt;
&lt;br /&gt;
This table currently does not contain any summarizing values.&lt;br /&gt;
&lt;br /&gt;
==== Column summary values ====&lt;br /&gt;
{{Quotation|A value that aggregates an entire column of values is a column summary, which generally appears in a separate row beneath the last row of detailed values.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
For each column under the &#039;RETURN&#039; spanner header it could be useful to provide an average gain/loss summary in per cent. It is unclear though, whether this information is desirable at all (due to lack of domain knowledge).&lt;br /&gt;
&lt;br /&gt;
==== Row summary values ====&lt;br /&gt;
{{Quotation|A value that aggregates an entire row of values is a row summary, which generally appears in a separate column to the right of the last column of detailed values.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The detailed values in columns beneath the &#039;RETURN&#039; spanner header seem to be cumulative across a row (Assumption based on the cryptic column titles). That is why there doesn&#039;t seem to be much sense in providing a separate summary values for each row (i.e for each fund).&lt;br /&gt;
==== Group summary values ====&lt;br /&gt;
{{Quotation|Group summary values [..] summarize meaningful subsets of values rather than the entire&lt;br /&gt;
set of values throughout the column or row.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Given only the information provided in the table, there is no plausible grouping possible. The only possible grouping, using only the provided data, would be one by intervals of assets (in Millions of Dollars) or gain/loss percentage intervals. However (possibly due to our lack of domain knowledge) these groupings don&#039;t seem reasonable.&lt;br /&gt;
==== Header versus footers ====&lt;br /&gt;
{{Quotation|When the summary values are more important to your message or to your readers than the details, and placing them below the details would make them&lt;br /&gt;
harder and less efficient to find, it often makes sense to place them in headers even though this is less conventional.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
In our case the summary values denote complementary information, therefore their position in the footer seems appropriate.&lt;br /&gt;
=== Page information ===&lt;br /&gt;
{{Quotation|Because of short-term memory constraints, effective table design requires that certain information be repeated on each new page. Otherwise, your readers may lose track of information that they need to interpret the table as they move from page to page. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Our table is not split into multiple pages, therefore this aspect is not applicable here.&lt;br /&gt;
==== Repeated column headers ====&lt;br /&gt;
{{Quotation|When tables extend onto multiple pages, the columns are no longer labeled after the first page unless you repeat the column headers on each.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The proper way of handling tables spreading across multiple pages would be to copy the table headers on top of each page. However, in our case this is not necessary.&lt;br /&gt;
==== Repeated row headers ====&lt;br /&gt;
{{Quotation|[...] even those of us who are careful to repeat column headers on each page seldom think to repeat the row headers as well, yet the problem is the same.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
This principle is applicable when multiple rows, which spread across multiple pages, are grouped together and have one title column where the title printed only for the first row of the group. The correct way of designing such a table would be to re-print the title on the first row on each page. Again, this is of no concern to our table here.&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 8 - Table Design.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18016</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18016"/>
		<updated>2007-11-20T10:57:52Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Aufgabenstellung ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]&lt;br /&gt;
&lt;br /&gt;
=== Zu beurteilende Tabelle ===&lt;br /&gt;
&lt;br /&gt;
[[Image:tufte_2006_beautiful-evidence_funds.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Structural Components of Tables ===&lt;br /&gt;
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Tables generally work best when they also contain additional text that is used to complement the categorical subdivisions and quantitative values in various ways. In Chapter 7, General Design for Communication, we noted that additional text can do the following:&lt;br /&gt;
* Label&lt;br /&gt;
* Introduce&lt;br /&gt;
* Explain&lt;br /&gt;
* Reinforce&lt;br /&gt;
* Highlight&lt;br /&gt;
* Sequence&lt;br /&gt;
* Recommend&lt;br /&gt;
* Inquire&lt;br /&gt;
|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The table tries to explain its data with some text. &lt;br /&gt;
&lt;br /&gt;
The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.&lt;br /&gt;
&lt;br /&gt;
It states labels for the ASSETS and the FUND columns. These column headers label the information below them and should be separated from the data with a horizontal line. &lt;br /&gt;
&lt;br /&gt;
The return values are clearly grouped with the spanner header RETURN.  Maybe it should be stated that this is the return on investment. &lt;br /&gt;
Below the RETURN spanner header we find column headers which state the period for which the data is valid. These should be separated from the data with a horizontal line. Furthermore it is not absolutely clear what there meaning is, and the mixing of so different periods makes it more difficult to understand the table. For example it would be interesting which 3 year period the 3-YR column covers. &lt;br /&gt;
&lt;br /&gt;
The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.&lt;br /&gt;
&lt;br /&gt;
The table does not try to focus my interest to a special area, because no area is specially highlighted. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Delineating columns and rows ===&lt;br /&gt;
{{Quotation|The design process involves several decisions regarding the layout of columns and rows to provide a structure that is easy and efficient to read and understand. Readers should be able to scan quickly through the content to find what they need and perhaps make localized comparisons of related numbers. |[Few, 2004]}}&lt;br /&gt;
{{Definition|Columns and rows are delineated through&lt;br /&gt;
* White space&lt;br /&gt;
*  Rules and grids&lt;br /&gt;
*  Fill color &lt;br /&gt;
.}}&lt;br /&gt;
&lt;br /&gt;
==== White space ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
It is not possible to read the rows without difficulty because the vertical white space between them is pretty small. Therefore it is recommended that the vertical white space between the rows is increased. &lt;br /&gt;
&lt;br /&gt;
As well the horizontal white space between the columns should be increased to ease the reading of the columns. From my point of view, the comparison of the funds is the most interesting information in this table. To lead the reader to scan down the columns, it is advisable to pronounce the white space between the columns more than the one between the rows. &lt;br /&gt;
&lt;br /&gt;
To make a clear distinction between row headers and data, the horizontal white space should be increased between these two parts. As well the horizontal white space between the ASSETS and FUND column should be increased a bit to make a clear distinction.&lt;br /&gt;
&lt;br /&gt;
==== Rules and grids ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Despite the uselessness of grids and the limited usefulness of rules to delineate columns and rows in tables, they are sometimes useful for grouping or highlighting subsets of data. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
In order to make the table more readable it is advisable to draw a line between the column headers and the data.&lt;br /&gt;
&lt;br /&gt;
If the table is in its original context surrounded with some objects where there should be a clear distinction, thin lines could be drawn on each side. Remember to keep the lines as thin and light as possible.   &lt;br /&gt;
&lt;br /&gt;
A combination of horizontal and vertical rules could be used if there is an area of special interest.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Fill color ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When white space alone can´t be used to effectively delineate columns and rows in tables, fill shades and hues work better than grids and rules. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this quotation the rows of the table could be separated with fill shades. It would also be possible to delineate the headers in the table as separate groups of information in using fill colors.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging data ===&lt;br /&gt;
&lt;br /&gt;
==== Columns or rows ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Some sequential relationships are more easily understood when they are arranged in a particular way, either horizontally from left to right or vertically from top to bottom. … We naturally think of time as moving from left to right, rather than down from top to bottom. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.  &lt;br /&gt;
&lt;br /&gt;
The time is illustrated from left to right, but the relations between the columns are not clear at all. &lt;br /&gt;
&lt;br /&gt;
==== Groups and breaks ====&lt;br /&gt;
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.&lt;br /&gt;
&lt;br /&gt;
For example make a table for the year 2003 till 2007. Or make a table showing the quarters in the year 2003. Everything is possible, but it should be consistent. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Columns sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Columns containing sets of quantitative values that you want your readers to compare easily should be placed as close to one another as possible. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this principle the table puts the values near together which should be easily comparable.&lt;br /&gt;
&lt;br /&gt;
The table shows the returns in percentage and the reader can easily compare the percentages. &lt;br /&gt;
&lt;br /&gt;
==== Data sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When you need to sequence numbers, their quantitative order, either ascending or descending, is the only useful way to sequence them. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The funds are listed descending concerning their assets. Since the asset of a fund is one of the most important characteristics and the assets are listed in numbers, it is useful to list the funds in their quantitative order.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Formatting text ===&lt;br /&gt;
==== Orientation ====&lt;br /&gt;
==== Alignment ====&lt;br /&gt;
==== Number and date format ====&lt;br /&gt;
==== Number and date precision ====&lt;br /&gt;
==== Fonts ====&lt;br /&gt;
==== Emphasis ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Summarizing values ===&lt;br /&gt;
==== Column summary values ====&lt;br /&gt;
==== Row summary values ====&lt;br /&gt;
==== Group summary values ====&lt;br /&gt;
==== Header versus footers ====&lt;br /&gt;
{{Quotation|When the summary values are more important to your message or to your readers than the details, and placing them below the details would make them&lt;br /&gt;
harder and less efficient to find, it often makes sense to place them in headers even though this is less conventional.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
=== Page information ===&lt;br /&gt;
{{Quotation|Because of short-term memory constraints, effective table design requires that certain information be repeated on each new page. Otherwise, your readers may lose track of information that they need to interpret the table as they move from page to page. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Our table is not split into multiple pages, therefore this rule is not applicable here.&lt;br /&gt;
==== Repeated column headers ====&lt;br /&gt;
{{Quotation|When tables extend onto multiple pages, the columns are no longer labeled after the first page unless you repeat the column headers on each.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The proper way of handling tables spreading across multiple pages would be to copy the table headers on top of each page. However, in our case this is not necessary.&lt;br /&gt;
==== Repeated row headers ====&lt;br /&gt;
{{Quotation|[...] even those of us who are careful to repeat column headers on each page seldom think to repeat the row headers as well, yet the problem is the same.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
This principle is applicable when multiple rows, which spread across multiple pages, are grouped together and have one title column where the title printed only for the first row of the group. The correct way of designing such a table would be to re-print the title on the first row on each page. Again, this is of no concern to our table here.&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 8 - Table Design.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18015</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_2&amp;diff=18015"/>
		<updated>2007-11-20T10:33:19Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Aufgabenstellung ==&lt;br /&gt;
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]&lt;br /&gt;
&lt;br /&gt;
=== Zu beurteilende Tabelle ===&lt;br /&gt;
&lt;br /&gt;
[[Image:tufte_2006_beautiful-evidence_funds.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Critics ==&lt;br /&gt;
=== Structural Components of Tables ===&lt;br /&gt;
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Tables generally work best when they also contain additional text that is used to complement the categorical subdivisions and quantitative values in various ways. In Chapter 7, General Design for Communication, we noted that additional text can do the following:&lt;br /&gt;
* Label&lt;br /&gt;
* Introduce&lt;br /&gt;
* Explain&lt;br /&gt;
* Reinforce&lt;br /&gt;
* Highlight&lt;br /&gt;
* Sequence&lt;br /&gt;
* Recommend&lt;br /&gt;
* Inquire&lt;br /&gt;
|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The table tries to explain its data with some text. &lt;br /&gt;
&lt;br /&gt;
The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.&lt;br /&gt;
&lt;br /&gt;
It states labels for the ASSETS and the FUND columns. These column headers label the information below them and should be separated from the data with a horizontal line. &lt;br /&gt;
&lt;br /&gt;
The return values are clearly grouped with the spanner header RETURN.  Maybe it should be stated that this is the return on investment. &lt;br /&gt;
Below the RETURN spanner header we find column headers which state the period for which the data is valid. These should be separated from the data with a horizontal line. Furthermore it is not absolutely clear what there meaning is, and the mixing of so different periods makes it more difficult to understand the table. For example it would be interesting which 3 year period the 3-YR column covers. &lt;br /&gt;
&lt;br /&gt;
The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.&lt;br /&gt;
&lt;br /&gt;
The table does not try to focus my interest to a special area, because no area is specially highlighted. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Delineating columns and rows ===&lt;br /&gt;
{{Quotation|The design process involves several decisions regarding the layout of columns and rows to provide a structure that is easy and efficient to read and understand. Readers should be able to scan quickly through the content to find what they need and perhaps make localized comparisons of related numbers. |[Few, 2004]}}&lt;br /&gt;
{{Definition|Columns and rows are delineated through&lt;br /&gt;
* White space&lt;br /&gt;
*  Rules and grids&lt;br /&gt;
*  Fill color &lt;br /&gt;
.}}&lt;br /&gt;
&lt;br /&gt;
==== White space ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
It is not possible to read the rows without difficulty because the vertical white space between them is pretty small. Therefore it is recommended that the vertical white space between the rows is increased. &lt;br /&gt;
&lt;br /&gt;
As well the horizontal white space between the columns should be increased to ease the reading of the columns. From my point of view, the comparison of the funds is the most interesting information in this table. To lead the reader to scan down the columns, it is advisable to pronounce the white space between the columns more than the one between the rows. &lt;br /&gt;
&lt;br /&gt;
To make a clear distinction between row headers and data, the horizontal white space should be increased between these two parts. As well the horizontal white space between the ASSETS and FUND column should be increased a bit to make a clear distinction.&lt;br /&gt;
&lt;br /&gt;
==== Rules and grids ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Despite the uselessness of grids and the limited usefulness of rules to delineate columns and rows in tables, they are sometimes useful for grouping or highlighting subsets of data. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
In order to make the table more readable it is advisable to draw a line between the column headers and the data.&lt;br /&gt;
&lt;br /&gt;
If the table is in its original context surrounded with some objects where there should be a clear distinction, thin lines could be drawn on each side. Remember to keep the lines as thin and light as possible.   &lt;br /&gt;
&lt;br /&gt;
A combination of horizontal and vertical rules could be used if there is an area of special interest.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Fill color ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When white space alone can´t be used to effectively delineate columns and rows in tables, fill shades and hues work better than grids and rules. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this quotation the rows of the table could be separated with fill shades. It would also be possible to delineate the headers in the table as separate groups of information in using fill colors.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging data ===&lt;br /&gt;
&lt;br /&gt;
==== Columns or rows ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Some sequential relationships are more easily understood when they are arranged in a particular way, either horizontally from left to right or vertically from top to bottom. … We naturally think of time as moving from left to right, rather than down from top to bottom. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.  &lt;br /&gt;
&lt;br /&gt;
The time is illustrated from left to right, but the relations between the columns are not clear at all. &lt;br /&gt;
&lt;br /&gt;
==== Groups and breaks ====&lt;br /&gt;
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.&lt;br /&gt;
&lt;br /&gt;
For example make a table for the year 2003 till 2007. Or make a table showing the quarters in the year 2003. Everything is possible, but it should be consistent. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Columns sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Columns containing sets of quantitative values that you want your readers to compare easily should be placed as close to one another as possible. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Following this principle the table puts the values near together which should be easily comparable.&lt;br /&gt;
&lt;br /&gt;
The table shows the returns in percentage and the reader can easily compare the percentages. &lt;br /&gt;
&lt;br /&gt;
==== Data sequence ====&lt;br /&gt;
&lt;br /&gt;
{{Quotation|When you need to sequence numbers, their quantitative order, either ascending or descending, is the only useful way to sequence them. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The funds are listed descending concerning their assets. Since the asset of a fund is one of the most important characteristics and the assets are listed in numbers, it is useful to list the funds in their quantitative order.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Formatting text ===&lt;br /&gt;
==== Orientation ====&lt;br /&gt;
==== Alignment ====&lt;br /&gt;
==== Number and date format ====&lt;br /&gt;
==== Number and date precision ====&lt;br /&gt;
==== Fonts ====&lt;br /&gt;
==== Emphasis ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Summarizing values ===&lt;br /&gt;
==== Column summary values ====&lt;br /&gt;
==== Row summary values ====&lt;br /&gt;
==== Group summary values ====&lt;br /&gt;
==== Header versus footers ====&lt;br /&gt;
&lt;br /&gt;
=== Page information ===&lt;br /&gt;
{{Quotation|Because of short-term memory constraints, effective table design requires that certain information be repeated on each new page. Otherwise, your readers may lose track of information that they need to interpret the table as they move from page to page. |[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
Our table is not split into multiple pages, therefore this rule is not applicable here.&lt;br /&gt;
==== Repeated column headers ====&lt;br /&gt;
{{Quotation|When tables extend onto multiple pages, the columns are no longer labeled after the first page unless you repeat the column headers on each.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
The proper way of handling tables spreading across multiple pages would be to copy the table headers on top of each page. However, in our case this is not necessary.&lt;br /&gt;
==== Repeated row headers ====&lt;br /&gt;
{{Quotation|[...] even those of us who are careful to repeat column headers on each page seldom think to repeat the row headers as well, yet the problem is the same.|[Few, 2004]}}&lt;br /&gt;
&lt;br /&gt;
This principle is applicable when multiple rows, which spread across multiple pages, are grouped together and have one title column where the title printed only for the first row of the group. The correct way of designing such a table would be to re-print the title on the first row on each page. Again, this is of no concern to our table here.&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 8 - Table Design.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]&lt;br /&gt;
&lt;br /&gt;
* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]&lt;br /&gt;
&lt;br /&gt;
*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17818</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17818"/>
		<updated>2007-11-09T11:37:57Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Wikipedia, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Computer Graphics may be divided into four major categories: &lt;br /&gt;
===Geometry===&lt;br /&gt;
The subfield of Geometry studies ways to represent and process surfaces. Boundary representations are most commonly used, because the appearance of an object depends mainly on its exterior. Although &amp;lt;b&amp;gt;point-based&amp;lt;/b&amp;gt; representations have been getting more and more popular lately, &amp;lt;b&amp;gt;polygonal meshes&amp;lt;/b&amp;gt; are still the most popular form of discrete digital approximation of surfaces. These representations are &amp;lt;b&amp;gt;Lagrangian&amp;lt;/b&amp;gt; (the spatial locations of the samples are independent) as opposed to &amp;lt;b&amp;gt;Eulerian&amp;lt;/b&amp;gt; surface descriptions (i.e., where spatial samples are fixed) which are mainly used for deforming surfaces which undergo many topological changes (e.g. fluids).&lt;br /&gt;
&lt;br /&gt;
===Animation===&lt;br /&gt;
This subfield of Geometry studies ways to represent and manipulate motion. Historically most interest has been focused on &amp;lt;b&amp;gt;parametric&amp;lt;/b&amp;gt; and &amp;lt;b&amp;gt;data-driven models&amp;lt;/b&amp;gt;, but in recent years &amp;lt;b&amp;gt;physical simulation&amp;lt;/b&amp;gt; has experienced a renaissance due to the growing computational capacity of modern machines.&lt;br /&gt;
===Rendering===&lt;br /&gt;
This subfield of Geometry studies algorithms to reproduce light transport. It does so by converting a model into an image by simulating light transport to get physically-based photorealistic images, or by applying a style as in non-photorealistic rendering. Two basic operations in realistic rendering are &amp;lt;b&amp;gt;transport&amp;lt;/b&amp;gt; (how much light gets from one place to another) and &amp;lt;b&amp;gt;scattering&amp;lt;/b&amp;gt; (how surfaces interact with light).&lt;br /&gt;
===Imaging===&lt;br /&gt;
This subfield of Geometry studies &amp;lt;b&amp;gt;image acquisition&amp;lt;/b&amp;gt; or &amp;lt;b&amp;gt;image editing&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:whirlwind.jpg |thumb|200px|Whirlwind displays aircraft positions and auxiliary information.]]&lt;br /&gt;
In the &amp;lt;b&amp;gt;60&#039;s&amp;lt;/b&amp;gt;, Jack Bresenham published how to draw lines on a raster device. He later extended this to circles. Larry Roberts pointed out the usefulness of homogeneous coordinates, 4x4 matrices and hidden line detection algorithms. Steve Coons introduced parametric surfaces and developed early computer aided geometric design concepts. The earlier work of Pierre Bézier on parametric curves and surfaces also became public. &lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;70&#039;s&amp;lt;/b&amp;gt;, rendering (shading) was discovered by Gouraud and Phong at the University of Utah. Turned Whitted developed recursive ray tracing which became the standard for photorealism. One of the first displays of computer animation was Futureworld (1976), which included an animation of a human face and hand — produced by Ed Catmull and Fred Parke also at the University of Utah.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;80&#039;s&amp;lt;/b&amp;gt;, Jim Blinn introduced blobby models and texture mapping concepts. Binary space partitioning (BSP) trees were introduced as a data structure. Loren Carpenter started exploring fractals in computer graphics. Postscript was developed by John Warnock.Steve Cook introduced stochastic sampling to ray tracing. Video arcade games took off.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;90&#039;s&amp;lt;/b&amp;gt;, Mosaic, the first graphical Internet browser was written. OpenGL became the standard for graphics APIs.Dynamical systems (physically based modeling) that allowed animation with collisions, gravity, friction, and cause and effects were introduced. Surface subdivision algorithms were rediscovered. Wavelets begin to be used in computer graphics. Image based rendering became the area for research in photo-realistic graphics.&lt;br /&gt;
==Application==&lt;br /&gt;
[[Image:Pov_ray.png|thumb|300px|Glasses (created by using POV-Ray 3.6).]]&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
[http://www.imdb.com/title/tt0074559/ Futureworld at the Internet Movie Database]&amp;lt;br&amp;gt;&lt;br /&gt;
[http://www.siggraph.org/ ACM SIGGRAPH]&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17816</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17816"/>
		<updated>2007-11-09T11:05:32Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Wikipedia, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Computer Graphics may be divided into four major categories: &lt;br /&gt;
===Geometry===&lt;br /&gt;
The subfield of Geometry studies ways to represent and process surfaces. Boundary representations are most commonly used, because the appearance of an object depends mainly on its exterior. Although &amp;lt;b&amp;gt;point-based&amp;lt;/b&amp;gt; representations have been getting more and more popular lately, &amp;lt;b&amp;gt;polygonal meshes&amp;lt;/b&amp;gt; are still the most popular form of discrete digital approximation of surfaces. These representations are &amp;lt;b&amp;gt;Lagrangian&amp;lt;/b&amp;gt; (the spatial locations of the samples are independent) as opposed to &amp;lt;b&amp;gt;Eulerian&amp;lt;/b&amp;gt; surface descriptions (i.e., where spatial samples are fixed) which are mainly used for deforming surfaces which undergo many topological changes (e.g. fluids).&lt;br /&gt;
&lt;br /&gt;
===Animation===&lt;br /&gt;
Studies with ways to represent and manipulate motion&lt;br /&gt;
===Rendering===&lt;br /&gt;
Studies algorithms to reproduce light transport&lt;br /&gt;
===Imaging===&lt;br /&gt;
Studies image acquisition or image editing&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:whirlwind.jpg |thumb|200px|Whirlwind displays aircraft positions and auxiliary information.]]&lt;br /&gt;
In the &amp;lt;b&amp;gt;60&#039;s&amp;lt;/b&amp;gt;, Jack Bresenham published how to draw lines on a raster device. He later extended this to circles. Larry Roberts pointed out the usefulness of homogeneous coordinates, 4x4 matrices and hidden line detection algorithms. Steve Coons introduced parametric surfaces and developed early computer aided geometric design concepts. The earlier work of Pierre Bézier on parametric curves and surfaces also became public. &lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;70&#039;s&amp;lt;/b&amp;gt;, rendering (shading) was discovered by Gouraud and Phong at the University of Utah. Turned Whitted developed recursive ray tracing which became the standard for photorealism. One of the first displays of computer animation was Futureworld (1976), which included an animation of a human face and hand — produced by Ed Catmull and Fred Parke also at the University of Utah.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;80&#039;s&amp;lt;/b&amp;gt;, Jim Blinn introduced blobby models and texture mapping concepts. Binary space partitioning (BSP) trees were introduced as a data structure. Loren Carpenter started exploring fractals in computer graphics. Postscript was developed by John Warnock.Steve Cook introduced stochastic sampling to ray tracing. Video arcade games took off.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;90&#039;s&amp;lt;/b&amp;gt;, Mosaic, the first graphical Internet browser was written. OpenGL became the standard for graphics APIs.Dynamical systems (physically based modeling) that allowed animation with collisions, gravity, friction, and cause and effects were introduced. Surface subdivision algorithms were rediscovered. Wavelets begin to be used in computer graphics. Image based rendering became the area for research in photo-realistic graphics.&lt;br /&gt;
==Application==&lt;br /&gt;
[[Image:Pov_ray.png|thumb|300px|Glasses (created by using POV-Ray 3.6).]]&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
[http://www.imdb.com/title/tt0074559/ Futureworld at the Internet Movie Database]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17815</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17815"/>
		<updated>2007-11-09T10:34:29Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Wikipedia, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Computer Graphics may be divided into four major categories: &lt;br /&gt;
===Geometry===&lt;br /&gt;
Studies ways to represent and process surfaces&lt;br /&gt;
===Animation===&lt;br /&gt;
Studies with ways to represent and manipulate motion&lt;br /&gt;
===Rendering===&lt;br /&gt;
Studies algorithms to reproduce light transport&lt;br /&gt;
===Imaging===&lt;br /&gt;
Studies image acquisition or image editing&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:whirlwind.jpg |thumb|200px|Whirlwind displays aircraft positions and auxiliary information.]]&lt;br /&gt;
In the &amp;lt;b&amp;gt;60&#039;s&amp;lt;/b&amp;gt;, Jack Bresenham published how to draw lines on a raster device. He later extended this to circles. Larry Roberts pointed out the usefulness of homogeneous coordinates, 4x4 matrices and hidden line detection algorithms. Steve Coons introduced parametric surfaces and developed early computer aided geometric design concepts. The earlier work of Pierre Bézier on parametric curves and surfaces also became public. &lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;70&#039;s&amp;lt;/b&amp;gt;, rendering (shading) was discovered by Gouraud and Phong at the University of Utah. Turned Whitted developed recursive ray tracing which became the standard for photorealism. One of the first displays of computer animation was Futureworld (1976), which included an animation of a human face and hand — produced by Ed Catmull and Fred Parke also at the University of Utah.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;80&#039;s&amp;lt;/b&amp;gt;, Jim Blinn introduced blobby models and texture mapping concepts. Binary space partitioning (BSP) trees were introduced as a data structure. Loren Carpenter started exploring fractals in computer graphics. Postscript was developed by John Warnock.Steve Cook introduced stochastic sampling to ray tracing. Video arcade games took off.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;b&amp;gt;90&#039;s&amp;lt;/b&amp;gt;, Mosaic, the first graphical Internet browser was written. OpenGL became the standard for graphics APIs.Dynamical systems (physically based modeling) that allowed animation with collisions, gravity, friction, and cause and effects were introduced. Surface subdivision algorithms were rediscovered. Wavelets begin to be used in computer graphics. Image based rendering became the area for research in photo-realistic graphics.&lt;br /&gt;
==Application==&lt;br /&gt;
[[Image:Pov_ray.png|thumb|300px|Glasses (created by using POV-Ray 3.6).]]&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
[http://www.imdb.com/title/tt0074559/ Futureworld at the Internet Movie Database]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=17814</id>
		<title>File:Pov ray.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=17814"/>
		<updated>2007-11-09T10:28:24Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
An image created by using POV-Ray 3.6.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
Public domain&lt;br /&gt;
== Source ==&lt;br /&gt;
http://commons.wikimedia.org/wiki/Image:Glasses_800_edit.png&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=17813</id>
		<title>File:Pov ray.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Pov_ray.png&amp;diff=17813"/>
		<updated>2007-11-09T10:26:45Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: == Summary ==  == Copyright status ==  == Source ==&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17811</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17811"/>
		<updated>2007-11-09T10:08:54Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Wikipedia, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
Computer Graphics may be divided into four major categories: &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;b&amp;gt;Geometry&amp;lt;/b&amp;gt;: studies ways to represent and process surfaces&lt;br /&gt;
*&amp;lt;b&amp;gt;Animation&amp;lt;/b&amp;gt;: studies with ways to represent and manipulate motion&lt;br /&gt;
*&amp;lt;b&amp;gt;Rendering&amp;lt;/b&amp;gt;: studies algorithms to reproduce light transport&lt;br /&gt;
*&amp;lt;b&amp;gt;Imaging&amp;lt;/b&amp;gt;: studies image acquisition or image editing&lt;br /&gt;
&lt;br /&gt;
[[Image:whirlwind.jpg |thumb|200px|Whirlwind displays aircraft positions and auxiliary information.]]&lt;br /&gt;
==History==&lt;br /&gt;
:In the 60&#039;s, Jack Bresenham published how to draw lines on a raster device. He later extended this to circles. Larry Roberts pointed out the usefulness of homogeneous coordinates, 4x4 matrices and hidden line detection algorithms. Steve Coons introduced parametric surfaces and developed early computer aided geometric design concepts. The earlier work of Pierre Bézier on parametric curves and surfaces also became public. &lt;br /&gt;
&lt;br /&gt;
:In the 70&#039;s, rendering (shading) was discovered by Gouraud and Phong at the University of Utah. Turned Whitted developed recursive ray tracing which became the standard for photorealism. One of the first displays of computer animation was Futureworld (1976), which included an animation of a human face and hand — produced by Ed Catmull and Fred Parke also at the University of Utah.&lt;br /&gt;
&lt;br /&gt;
:In the 80&#039;s, Jim Blinn introduced blobby models and texture mapping concepts. Binary space partitioning (BSP) trees were introduced as a data structure. Loren Carpenter started exploring fractals in computer graphics. Postscript was developed by John Warnock.Steve Cook introduced stochastic sampling to ray tracing. Video arcade games took off.&lt;br /&gt;
&lt;br /&gt;
: In the 90&#039;s, Mosaic, the first graphical Internet browser was written. OpenGL became the standard for graphics APIs.Dynamical systems (physically based modeling) that allowed animation with collisions, gravity, friction, and cause and effects were introduced. Surface subdivision algorithms were rediscovered. Wavelets begin to be used in computer graphics. Image based rendering became the area for research in photo-realistic graphics.&lt;br /&gt;
==Application== &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
[http://www.imdb.com/title/tt0074559/ Futureworld at the Internet Movie Database]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Whirlwind.jpg&amp;diff=17776</id>
		<title>File:Whirlwind.jpg</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Whirlwind.jpg&amp;diff=17776"/>
		<updated>2007-11-08T21:25:53Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Image of whirlwind display&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;br /&gt;
http://design.osu.edu/carlson/history/lesson2.html&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17773</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17773"/>
		<updated>2007-11-08T21:17:10Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Wikipedia, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
Computer Graphics may be divided into four major categories: &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;b&amp;gt;Geometry&amp;lt;/b&amp;gt;: studies ways to represent and process surfaces&lt;br /&gt;
*&amp;lt;b&amp;gt;Animation&amp;lt;/b&amp;gt;: studies with ways to represent and manipulate motion&lt;br /&gt;
*&amp;lt;b&amp;gt;Rendering&amp;lt;/b&amp;gt;: studies algorithms to reproduce light transport&lt;br /&gt;
*&amp;lt;b&amp;gt;Imaging&amp;lt;/b&amp;gt;: studies image acquisition or image editing&lt;br /&gt;
&lt;br /&gt;
[[Image:whirlwind.jpg |thumb|200px|Whirlwind display.]]&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==Application== &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17771</id>
		<title>File:Utah teapot.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17771"/>
		<updated>2007-11-08T21:15:51Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
The Utah teapot.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
This image has been released into the public domain by its author, Finlay McWalter at the English Wikipedia project.&lt;br /&gt;
== Source ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
http://en.wikipedia.org/wiki/Image:Utah_teapot.png&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Whirlwind.jpg&amp;diff=17769</id>
		<title>File:Whirlwind.jpg</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Whirlwind.jpg&amp;diff=17769"/>
		<updated>2007-11-08T21:03:15Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: Image of whirlwind display&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Image of whirlwind display&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17768</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17768"/>
		<updated>2007-11-08T20:57:36Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Definition==&lt;br /&gt;
{{Quotation|Computer graphics broadly studies the manipulation of visual and geometric information using computational techniques. Computer graphics as an academic discipline focuses on the mathematical and computational foundations of image generation and processing rather than purely aesthetic issues.|[Wikipedia, 2007]}}&lt;br /&gt;
&lt;br /&gt;
==Subfields==&lt;br /&gt;
*&amp;lt;b&amp;gt;Geometry&amp;lt;/b&amp;gt;: studies ways to represent and process surfaces&lt;br /&gt;
*&amp;lt;b&amp;gt;Animation&amp;lt;/b&amp;gt;: studies with ways to represent and manipulate motion&lt;br /&gt;
*&amp;lt;b&amp;gt;Rendering&amp;lt;/b&amp;gt;: studies algorithms to reproduce light transport&lt;br /&gt;
*&amp;lt;b&amp;gt;Imaging&amp;lt;/b&amp;gt;: studies image acquisition or image editing&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==Application== &lt;br /&gt;
* graphs and charts&lt;br /&gt;
* computer-aided design&lt;br /&gt;
* virtual-reality environment&lt;br /&gt;
* data visualisation&lt;br /&gt;
* education and training&lt;br /&gt;
* computer art&lt;br /&gt;
* entertainment&lt;br /&gt;
* image processing&lt;br /&gt;
* graphical user interfaces &lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17767</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17767"/>
		<updated>2007-11-08T20:30:47Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
==Definition==&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Wikipedia, Computer Graphics. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Computer_graphics.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17766</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17766"/>
		<updated>2007-11-08T20:29:14Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
==Definition==&lt;br /&gt;
&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965. &amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007] Finlay McWalter, Utah Teapot, Wikipedia. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Image:Utah_teapot.png.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17765</id>
		<title>File:Utah teapot.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17765"/>
		<updated>2007-11-08T20:22:17Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
The Utah teapot.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
This image has been released into the public domain by its author, Finlay McWalter at the English Wikipedia project.&lt;br /&gt;
== Source ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[Wikipedia, 2007]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17764</id>
		<title>File:Utah teapot.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17764"/>
		<updated>2007-11-08T20:10:27Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
The Utah teapot.&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
This image has been released into the public domain by its author, Finlay McWalter at the English Wikipedia project.&lt;br /&gt;
== Source ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
http://en.wikipedia.org/wiki/Image:Utah_teapot.png&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17763</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17763"/>
		<updated>2007-11-08T20:04:58Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:utah teapot.png|thumb|300px|The Utah teapot.]]&lt;br /&gt;
==Introduction==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17762</id>
		<title>File:Utah teapot.png</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:Utah_teapot.png&amp;diff=17762"/>
		<updated>2007-11-08T19:59:57Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: == Summary ==  == Copyright status ==  == Source ==&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17747</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17747"/>
		<updated>2007-11-08T14:29:28Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1965]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17726</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1 - Computer Graphics</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09_-_Aufgabe_1_-_Computer_Graphics&amp;diff=17726"/>
		<updated>2007-11-08T11:42:42Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: ==Introduction== &amp;lt;br&amp;gt; {{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer program...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{{Quotation|Perhaps the best way to define computer graphics is to find out what it is not. It is not a machine. It is not a computer, nor a group of computer programs. It is not the know-how of a graphic designer, a programmer, a writer, a motion picture specialist, or a reproduction specialist.&lt;br /&gt;
Computer graphics is all these – a consciously managed and documented technology directed toward communicating information accurately and descriptively.|[Fetter, 1966]}}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[Fetter, 1966] W. A. Fetter, Computer Graphics in Communication, McGraw-Hill Book Company, New York, 1965.&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0708_0225966&amp;diff=17401</id>
		<title>User:UE-InfoVis0708 0225966</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0708_0225966&amp;diff=17401"/>
		<updated>2007-10-29T10:54:49Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:VladimirD.jpg|right|Vladimir Drienovsky]]&lt;br /&gt;
{| &lt;br /&gt;
|&#039;&#039;Nachname:&#039;&#039;||&#039;&#039;&#039;Drienovsky&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Vorname:&#039;&#039;||&#039;&#039;&#039;Vladimir&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Matrikelnummer:&#039;&#039;||&#039;&#039;&#039;0225966&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Studienkennzahl:&#039;&#039;||&#039;&#039;&#039;533&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;E-mail Adresse:&#039;&#039;||&#039;&#039;&#039;e0225966_at_student.tuwien.ac.at&#039;&#039;&#039;&lt;br /&gt;
|}&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0708_0225966&amp;diff=17400</id>
		<title>User:UE-InfoVis0708 0225966</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0708_0225966&amp;diff=17400"/>
		<updated>2007-10-29T10:52:45Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:VladimirD.jpg|Georg Prohaska]]&lt;br /&gt;
{| &lt;br /&gt;
|&#039;&#039;Nachname:&#039;&#039;||&#039;&#039;&#039;Drienovsky&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Vorname:&#039;&#039;||&#039;&#039;&#039;Vladimir&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Matrikelnummer:&#039;&#039;||&#039;&#039;&#039;0225966&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Studienkennzahl:&#039;&#039;||&#039;&#039;&#039;533&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;E-mail Adresse:&#039;&#039;||&#039;&#039;&#039;e0225966_at_student.tuwien.ac.at&#039;&#039;&#039;&lt;br /&gt;
|}&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=File:VladimirD.jpg&amp;diff=17399</id>
		<title>File:VladimirD.jpg</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=File:VladimirD.jpg&amp;diff=17399"/>
		<updated>2007-10-29T10:52:02Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: == Summary ==  == Copyright status ==  == Source ==&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
&lt;br /&gt;
== Copyright status ==&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09&amp;diff=17395</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09&amp;diff=17395"/>
		<updated>2007-10-29T09:44:53Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Dies ist die Gruppenseite der &#039;&#039;&#039;Gruppe 9&#039;&#039;&#039; der Lehrveranstaltung &lt;br /&gt;
[[Teaching:TUW - UE InfoVis WS 2007/08|UE Informationsvisualisierung WS 07/08]]&amp;lt;br&amp;gt;.&lt;br /&gt;
== Gruppenmitglieder ==&lt;br /&gt;
[[User:UE-InfoVis0708_0200905|Kremmel, Thomas]] &amp;lt;br&amp;gt;&lt;br /&gt;
[[User:UE-InfoVis0708_0325904|Prohaska, Georg]] &amp;lt;br&amp;gt;&lt;br /&gt;
[[User:UE-InfoVis0708_0225966|Drienovsky, Vladimir]]&lt;br /&gt;
== Aufgaben ==&lt;br /&gt;
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1|Aufgabe 1]] &amp;lt;br&amp;gt;&lt;br /&gt;
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2|Aufgabe 2]] &amp;lt;br&amp;gt;&lt;br /&gt;
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3|Aufgabe 3]] &amp;lt;br&amp;gt;&lt;br /&gt;
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 4|Aufgabe 4]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09&amp;diff=17394</id>
		<title>Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2007/08_-_Gruppe_09&amp;diff=17394"/>
		<updated>2007-10-29T09:33:59Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Dies ist die Gruppenseite der &#039;&#039;&#039;Gruppe 9&#039;&#039;&#039; der Lehrveranstaltung &lt;br /&gt;
[[Teaching:TUW - UE InfoVis WS 2007/08|UE Informationsvisualisierung WS 07/08]]&amp;lt;br&amp;gt;.&lt;br /&gt;
== Gruppenmitglieder ==&lt;br /&gt;
[[User:UE-InfoVis0708_0200905|Kremmel, Thomas]] &amp;lt;br&amp;gt;&lt;br /&gt;
[[User:UE-InfoVis0708_0325904|Prohaska, Georg]] &amp;lt;br&amp;gt;&lt;br /&gt;
[[User:UE-InfoVis0708_0225966|Drienovsky, Vladimir]]&lt;br /&gt;
== Aufgaben ==&lt;br /&gt;
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1|Aufgabe 1]]&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
	<entry>
		<id>https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0708_0225966&amp;diff=17393</id>
		<title>User:UE-InfoVis0708 0225966</title>
		<link rel="alternate" type="text/html" href="https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0708_0225966&amp;diff=17393"/>
		<updated>2007-10-29T09:32:37Z</updated>

		<summary type="html">&lt;p&gt;UE-InfoVis0708 0225966: New page: {|  |&amp;#039;&amp;#039;Nachname:&amp;#039;&amp;#039;||&amp;#039;&amp;#039;&amp;#039;Drienovsky&amp;#039;&amp;#039;&amp;#039; |- |&amp;#039;&amp;#039;Vorname:&amp;#039;&amp;#039;||&amp;#039;&amp;#039;&amp;#039;Vladimir&amp;#039;&amp;#039;&amp;#039; |- |&amp;#039;&amp;#039;Matrikelnummer:&amp;#039;&amp;#039;||&amp;#039;&amp;#039;&amp;#039;0225966&amp;#039;&amp;#039;&amp;#039; |- |&amp;#039;&amp;#039;Studienkennzahl:&amp;#039;&amp;#039;||&amp;#039;&amp;#039;&amp;#039;533&amp;#039;&amp;#039;&amp;#039; |- |&amp;#039;&amp;#039;E-mail Adresse:&amp;#039;&amp;#039;||&amp;#039;&amp;#039;&amp;#039;e0225966_at_stu...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| &lt;br /&gt;
|&#039;&#039;Nachname:&#039;&#039;||&#039;&#039;&#039;Drienovsky&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Vorname:&#039;&#039;||&#039;&#039;&#039;Vladimir&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Matrikelnummer:&#039;&#039;||&#039;&#039;&#039;0225966&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Studienkennzahl:&#039;&#039;||&#039;&#039;&#039;533&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;E-mail Adresse:&#039;&#039;||&#039;&#039;&#039;e0225966_at_student.tuwien.ac.at&#039;&#039;&#039;&lt;br /&gt;
|}&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>UE-InfoVis0708 0225966</name></author>
	</entry>
</feed>