InfoVis:Wiki - User contributions [en]

User:UE-InfoVis0708 0200905

2008-07-18T16:00:34Z

UE-InfoVis0708 0200905:

[[Image:ThomasK.jpg|right|thumb|pic]] 
{|
|''Nachname:''||'''K'''
|-
|''Vorname:''||'''T'''
|-
|''Matrikelnummer:''||'''0200905'''
|-
|''Studienkennzahl:''||'''926 - Wirtschaftsinformatik'''
|-
|''E-mail Adresse:''||''''''
|}

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3

2007-11-30T11:16:33Z

UE-InfoVis0708 0200905:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Traeume.jpg]]

Frauen träumen sanfter

== Critics ==
=== Data-Ink Ratio ===
{{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]}}
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.

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.

=== Visual Means to Highlight Data ===
{{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]}}
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.

=== Background ===
{{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]}}
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.

=== Emphasize the most important data ink ===
{{Quotation| Regardless of the encoding method, certain visual attributes of objects, words, and numbers stand out more than others.| [Few, 2004]}}
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.

{{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:
* Group the data (i.e., segment the data into meaningful subsets)
* Prioritize the data (i.e., rank the data by importance)
* Sequence the data (i.e., give direction for the order in which the data
.| [Few, 2004]}}
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.

=== Prioritize the Data ===
{{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]}}
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.
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.

== References ==

[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.

[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 7 - General Design for Communication.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3

2007-11-30T11:15:04Z

UE-InfoVis0708 0200905:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Traeume.jpg]]

Frauen träumen sanfter

== Critics ==
=== Data-Ink Ratio ===
{{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]}}
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.

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.

=== Visual Means to Highlight Data ===
{{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]}}
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.

=== Background ===
{{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]}}
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.

=== Emphasize the most important data ink ===
{{Quotation| Regardless of the encoding method, certain visual attributes of objects, words, and numbers stand out more than others.| [Few, 2004]}}
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.

{{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:
* Group the data (i.e., segment the data into meaningful subsets)
* Prioritize the data (i.e., rank the data by importance)
* Sequence the data (i.e., give direction for the order in which the data
.| [Few, 2004]}}
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.

=== Prioritize the Data ===
{{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]}}
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.
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.

== References ==

[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.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3

2007-11-30T11:13:34Z

UE-InfoVis0708 0200905:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Traeume.jpg]]

Frauen träumen sanfter

== Critics ==
=== Data-Ink Ratio ===
{{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]}}
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.

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.

=== Visual Means to Highlight Data ===
{{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]}}
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.

=== Background ===
{{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]}}
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.

=== Emphasize the most important data ink ===
{{Quotation| Regardless of the encoding method, certain visual attributes of objects, words, and numbers stand out more than others.| [Few, 2004]}}
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.

{{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:
* Group the data (i.e., segment the data into meaningful subsets)
* Prioritize the data (i.e., rank the data by importance)
* Sequence the data (i.e., give direction for the order in which the data
.| [Few, 2004]}}
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.

=== Prioritize the Data ===
{{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]}}
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.
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.

== References ==

[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.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3

2007-11-30T10:23:27Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3

2007-11-30T10:21:46Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 3

2007-11-29T09:03:16Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T13:50:12Z

UE-InfoVis0708 0200905:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:tufte_2006_beautiful-evidence_funds.jpg]]

== Critics ==
=== Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}

The table tries to explain its data with some text.

The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.

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.

The return values are clearly grouped with the spanner header RETURN. Maybe it should be stated that this is the return on investment.
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.

The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.

The table does not try to focus my interest to a special area, because no area is specially highlighted.

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

==== White space ====

{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}

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.

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.

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.

==== Rules and grids ====

{{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]}}

In order to make the table more readable it is advisable to draw a line between the column headers and the data.

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.

A combination of horizontal and vertical rules could be used if there is an area of special interest.

==== Fill color ====

{{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]}}

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.

=== Arranging data ===

==== Columns or rows ====

{{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]}}

Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.

The time is illustrated from left to right, but the relations between the columns are not clear at all.

==== Groups and breaks ====
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}

Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.

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.

==== Columns sequence ====

{{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]}}

Following this principle the table puts the values near together which should be easily comparable.

The table shows the returns in percentage and the reader can easily compare the percentages.

==== Data sequence ====

{{Quotation|When you need to sequence numbers, their quantitative order, either ascending or descending, is the only useful way to sequence them. |[Few, 2004]}}

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.

=== Formatting text ===
==== Orientation ====
==== Alignment ====
==== Number and date format ====
==== Number and date precision ====
==== Fonts ====
==== Emphasis ====

=== Summarizing values ===
==== Column summary values ====
==== Row summary values ====
==== Group summary values ====
==== Header versus footers ====

=== Page information ===
==== Repeated column headers ====
==== Repeated row headers ====

== References ==

[Few, 2004] Stephen Few, Show Me the Numbers: Designing Tables and Graphs to Enlighten, Analytics Press, 2004, Chapter 8 - Table Design.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T13:47:17Z

UE-InfoVis0708 0200905:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:tufte_2006_beautiful-evidence_funds.jpg]]

== Critics ==
=== Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}

The table tries to explain its data with some text.

The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.

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.

The return values are clearly grouped with the spanner header RETURN. Maybe it should be stated that this is the return on investment.
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.

The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.

The table does not try to focus my interest to a special area, because no area is specially highlighted.

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

==== White space ====

{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}

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.

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.

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.

==== Rules and grids ====

{{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]}}

In order to make the table more readable it is advisable to draw a line between the column headers and the data.

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.

A combination of horizontal and vertical rules could be used if there is an area of special interest.

==== Fill color ====

{{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]}}

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.

=== Arranging data ===

==== Columns or rows ====

{{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]}}

Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.

The time is illustrated from left to right, but the relations between the columns are not clear at all.

==== Groups and breaks ====
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}

Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.

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.

==== Columns sequence ====

{{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]}}

Following this principle the table puts the values near together which should be easily comparable.

The table shows the returns in percentage and the reader can easily compare the percentages.

==== Data sequence ====

{{Quotation|When you need to sequence numbers, their quantitative order, either ascending or descending, is the only useful way to sequence them. |[Few, 2004]}}

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.

=== Formatting text ===
==== Orientation ====
==== Alignment ====
==== Number and date format ====
==== Number and date precision ====
==== Fonts ====
==== Emphasis ====

=== Summarizing values ===
==== Column summary values ====
==== Row summary values ====
==== Group summary values ====
==== Header versus footers ====

=== Page information ===
==== Repeated column headers ====
==== Repeated row headers ====

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T13:45:37Z

UE-InfoVis0708 0200905:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:tufte_2006_beautiful-evidence_funds.jpg]]

== Critics ==
=== Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}

The table tries to explain its data with some text.

The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.

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.

The return values are clearly grouped with the spanner header RETURN. Maybe it should be stated that this is the return on investment.
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.

The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.

The table does not try to focus my interest to a special area, because no area is specially highlighted.

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

==== White space ====

{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}

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.

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.

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.

==== Rules and grids ====

{{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]}}

In order to make the table more readable it is advisable to draw a line between the column headers and the data.

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.

A combination of horizontal and vertical rules could be used if there is an area of special interest.

==== Fill color ====

{{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]}}

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.

=== Arranging data ===

{{Quotation|When you need to sequence numbers, their quantitative order, either ascending or descending, is the only useful way to sequence them. |[Few, 2004]}}

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.

==== Columns or rows ====

{{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]}}

Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.

The time is illustrated from left to right, but the relations between the columns are not clear at all.

==== Groups and breaks ====
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}

Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.

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.

==== Columns sequence ====

{{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]}}

Following this principle the table puts the values near together which should be easily comparable.

The table shows the returns in percentage and the reader can easily compare the percentages.

==== Data sequence ====

=== Formatting text ===
==== Orientation ====
==== Alignment ====
==== Number and date format ====
==== Number and date precision ====
==== Fonts ====
==== Emphasis ====

=== Summarizing values ===
==== Column summary values ====
==== Row summary values ====
==== Group summary values ====
==== Header versus footers ====

=== Page information ===
==== Repeated column headers ====
==== Repeated row headers ====

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T13:37:05Z

UE-InfoVis0708 0200905:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:tufte_2006_beautiful-evidence_funds.jpg]]

== Critics ==
=== Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}

The table tries to explain its data with some text.

The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.

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.

The return values are clearly grouped with the spanner header RETURN. Maybe it should be stated that this is the return on investment.
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.

The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.

The table does not try to focus my interest to a special area, because no area is specially highlighted.

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

==== White space ====

{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}

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.

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.

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.

==== Rules and grids ====

{{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]}}

In order to make the table more readable it is advisable to draw a line between the column headers and the data.

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.

A combination of horizontal and vertical rules could be used if there is an area of special interest.

==== Fill color ====

{{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]}}

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.

=== Arranging data ===
==== Columns or rows ====

{{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]}}

Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.

The time is illustrated from left to right, but the relations between the columns are not clear at all.

==== Groups and breaks ====
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}

Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.

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.

==== Columns sequence ====

{{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]}}

Following this principle the table puts the values near together which should be easily comparable.

The table shows the returns in percentage and the reader can easily compare the percentages.

==== Data sequence ====

=== Formatting text ===
==== Orientation ====
==== Alignment ====
==== Number and date format ====
==== Number and date precision ====
==== Fonts ====
==== Emphasis ====

=== Summarizing values ===
==== Column summary values ====
==== Row summary values ====
==== Group summary values ====
==== Header versus footers ====

=== Page information ===
==== Repeated column headers ====
==== Repeated row headers ====

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T13:17:28Z

UE-InfoVis0708 0200905:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:tufte_2006_beautiful-evidence_funds.jpg]]

== Critics ==
=== Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}

The table tries to explain its data with some text.

The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.

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.

The return values are clearly grouped with the spanner header RETURN. Maybe it should be stated that this is the return on investment.
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.

The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.

The table does not try to focus my interest to a special area, because no area is specially highlighted.

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

==== White space ====

{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}

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.

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.

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.

==== Rules and grids ====

{{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]}}

In order to make the table more readable it is advisable to draw a line between the column headers and the data.

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.

A combination of horizontal and vertical rules could be used if there is an area of special interest.

==== Fill color ====

{{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]}}

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.

=== Arranging data ===
==== Columns or rows ====

{{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]}}

Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.

The time is illustrated from left to right, but the relations between the columns are not clear at all.

==== Groups and breaks ====
{{Quotation|It is often appropriate, and perhaps even necessary, to break sets of data into smaller groups. |[Few, 2004]}}

Since the changing time scale of the table is confusing, I would suggest to group the data for a given time scale.

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.

==== Columns sequence ====
==== Data sequence ====

=== Formatting text ===
==== Orientation ====
==== Alignment ====
==== Number and date format ====
==== Number and date precision ====
==== Fonts ====
==== Emphasis ====

=== Summarizing values ===
==== Column summary values ====
==== Row summary values ====
==== Group summary values ====
==== Header versus footers ====

=== Page information ===
==== Repeated column headers ====
==== Repeated row headers ====

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T13:08:17Z

UE-InfoVis0708 0200905:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:tufte_2006_beautiful-evidence_funds.jpg]]

== Critics ==
=== Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}

The table tries to explain its data with some text.

The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.

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.

The return values are clearly grouped with the spanner header RETURN. Maybe it should be stated that this is the return on investment.
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.

The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.

The table does not try to focus my interest to a special area, because no area is specially highlighted.

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

==== White space ====

{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}

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.

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.

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.

==== Rules and grids ====

{{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]}}

In order to make the table more readable it is advisable to draw a line between the column headers and the data.

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.

A combination of horizontal and vertical rules could be used if there is an area of special interest.

==== Fill color ====

{{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]}}

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.

=== Arranging data ===
==== Columns or rows ====

{{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]}}

Concerning the ranking relationships the table shows an easy to understand top-down ranking of funds regarding their assets in million dollars.

The time is illustrated from left to right, but the relations between the columns are not clear at all.

==== Groups and breaks ====
==== Columns sequence ====
==== Data sequence ====

=== Formatting text ===
==== Orientation ====
==== Alignment ====
==== Number and date format ====
==== Number and date precision ====
==== Fonts ====
==== Emphasis ====

=== Summarizing values ===
==== Column summary values ====
==== Row summary values ====
==== Group summary values ====
==== Header versus footers ====

=== Page information ===
==== Repeated column headers ====
==== Repeated row headers ====

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T11:57:09Z

UE-InfoVis0708 0200905:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:tufte_2006_beautiful-evidence_funds.jpg]]

== Critics ==
=== Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}

The table tries to explain its data with some text.

The title of the table should be clearly seperated from the table and maybe regrouped in a title and a sub title.

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.

The return values are clearly grouped with the spanner header RETURN. Maybe it should be stated that this is the return on investment.
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.

The dollar and percent signs should not be introduced at the first data line. Data definitions should be part of the column headers.

The table does not try to focus my interest to a special area, because no area is specially highlighted.

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

==== White space ====

{{Quotation|White space is the preferred means for arraning data into columns and rows. |[Few, 2004]}}

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.

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.

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.

==== Rules and grids ====

{{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]}}

In order to make the table more readable it is advisable to draw a line between the column headers and the data.

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.

A combination of horizontal and vertical rules could be used if there is an area of special interest.

==== Fill color ====

{{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]}}

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.

=== Arranging data ===
==== Columns or rows ====
==== Groups and breaks ====
==== Columns sequence ====
==== Data sequence ====

=== Formatting text ===
==== Orientation ====
==== Alignment ====
==== Number and date format ====
==== Number and date precision ====
==== Fonts ====
==== Emphasis ====

=== Summarizing values ===
==== Column summary values ====
==== Row summary values ====
==== Group summary values ====
==== Header versus footers ====

=== Page information ===
==== Repeated column headers ====
==== Repeated row headers ====

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T11:49:14Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T11:41:38Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T11:39:59Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T11:35:06Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T11:19:51Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T10:51:54Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T10:49:37Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:52:45Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:49:22Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:41:47Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:39:34Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:38:11Z

UE-InfoVis0708 0200905:

== = Structural Components of Tables ===
{{Definition|Thoughtfully designed Data and Structural Components lead to clear and efficient communication.}}

{{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:
* Label
* Introduce
* Explain
* Reinforce
* Highlight
* Sequence
* Recommend
* Inquire
|[Few, 2004]}}
Write critic for quotation here..

{{Quotation|Support components are the non-data ink objects that highlight or organize the data. The following visual objects and attributes can function as support components:
* White space and page breaks
* Rules and grids
* Fill color
|[Few, 2004]}}
Write critic for quotation here..

=== Delineating columns and rows ===
{{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]}}
{{Definition|Columns and rows are delineated through
* White space
* Rules and grids
* Fill color
.}}

Write critic for quotation here..

=== Arranging data ===

=== Formatting text ===

=== Summarizing values ===

=== Page Information ===

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:20:43Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:19:18Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 2

2007-11-18T09:18:29Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09

2007-10-26T00:36:48Z

UE-InfoVis0708 0200905: New page: Dies ist die Gruppenseite der '''Gruppe 9''' der Lehrveranstaltung UE Informationsvisualisierung WS 07/08 . == Gruppenmitglieder == [[User:UE-I...

Dies ist die Gruppenseite der '''Gruppe 9''' der Lehrveranstaltung
[[Teaching:TUW - UE InfoVis WS 2007/08|UE Informationsvisualisierung WS 07/08]] .
== Gruppenmitglieder ==
[[User:UE-InfoVis0708_0200905|Kremmel, Thomas]] 
[[User:UE-InfoVis0708_0325904|Prohaska, Georg]]
== Aufgaben ==
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09 - Aufgabe 1|Aufgabe 1]]

Teaching:TUW - UE InfoVis WS 2007/08

2007-10-26T00:36:16Z

UE-InfoVis0708 0200905:

[[Image:Aigner03infovis ue.gif]] <big>WS 2007/08</big>

'''LVA Nr:''' 188.308 ([http://tuwis.tuwien.ac.at/lva/tuwien/188308 TUWIS++ Seite])

'''LVA Homepage:''' http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html

'''Leitung:''' [[Aigner, Wolfgang|Wolfgang Aigner]] [aigner (at) ifs.tuwien.ac.at] 
'''Tutor:''' [[User:ASchratt|Alexander Schratt]] [alexander.schratt (at) donau-uni.ac.at]

== Gruppen ==

[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01|Gruppe 01 (Kaburek)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 02|Gruppe 02 (KOGLER)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 03|Gruppe 03 (DELPORTE, KLAUSNER)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05 (Petrak, Planinc, Sackl)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 09|Gruppe 09 (Drienovsky, Kremmel, Prohaska)]] 

== News / Bemerkungen ==
'''Kostenlose Tableau EDU Lizenz verfügbar'''
Tableau ist ein kommerzielles Produkt zur visuellen Datenanalyse.
Für TeilnehmerInnen an der Übung besteht jedoch die Möglichkeit des Downloads einer kostenlosen EDU Lizenz.
Der notwendige Link wird bei Interesse per E-mail zugesandt.
'''Hinweis:''' ''Die Verwendung von Tableau ist für Übungsaufgaben '''NICHT''' erforderlich.'' 
-- [[User:Iwolf|Wolfgang Aigner]] 17:35, 24 October 2007 (CEST)

Teaching:TUW - UE InfoVis WS 2007/08

2007-10-26T00:35:37Z

UE-InfoVis0708 0200905:

[[Image:Aigner03infovis ue.gif]] <big>WS 2007/08</big>

'''LVA Nr:''' 188.308 ([http://tuwis.tuwien.ac.at/lva/tuwien/188308 TUWIS++ Seite])

'''LVA Homepage:''' http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html

'''Leitung:''' [[Aigner, Wolfgang|Wolfgang Aigner]] [aigner (at) ifs.tuwien.ac.at] 
'''Tutor:''' [[User:ASchratt|Alexander Schratt]] [alexander.schratt (at) donau-uni.ac.at]

== Gruppen ==

[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01|Gruppe 01 (Kaburek)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 02|Gruppe 02 (KOGLER)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 03|Gruppe 03 (DELPORTE, KLAUSNER)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05 (Petrak, Planinc, Sackl)]] 
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 09 (Drienovsky, Kremmel, Prohaska)]] 

== News / Bemerkungen ==
'''Kostenlose Tableau EDU Lizenz verfügbar'''
Tableau ist ein kommerzielles Produkt zur visuellen Datenanalyse.
Für TeilnehmerInnen an der Übung besteht jedoch die Möglichkeit des Downloads einer kostenlosen EDU Lizenz.
Der notwendige Link wird bei Interesse per E-mail zugesandt.
'''Hinweis:''' ''Die Verwendung von Tableau ist für Übungsaufgaben '''NICHT''' erforderlich.'' 
-- [[User:Iwolf|Wolfgang Aigner]] 17:35, 24 October 2007 (CEST)

Teaching:TUW - UE InfoVis WS 2007/08

2007-10-26T00:34:47Z

UE-InfoVis0708 0200905:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06

2007-10-24T10:09:35Z

UE-InfoVis0708 0200905:

Dies ist die Gruppenseite der '''Gruppe 6''' der Lehrveranstaltung
[[Teaching:TUW - UE InfoVis WS 2007/08|UE Informationsvisualisierung WS 07/08]] .
== Gruppenmitglieder ==
[[User:UE-InfoVis0708_0200905|Kremmel, Thomas]]
== Aufgaben ==
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1|Aufgabe 1]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06

2007-10-24T10:09:06Z

UE-InfoVis0708 0200905:

Dies ist die Gruppenseite der '''Gruppe 6''' der Lehrveranstaltung
[[Teaching:Teaching:TUW - UE InfoVis WS 2007/08|UE Informationsvisualisierung WS 07/08]] .
== Gruppenmitglieder ==
[[User:UE-InfoVis0708_0200905|Kremmel, Thomas]]
== Aufgaben ==
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1|Aufgabe 1]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06

2007-10-24T10:07:20Z

UE-InfoVis0708 0200905:

Dies ist die Gruppenseite der '''Gruppe 6''' der Lehrveranstaltung
[[Teaching:Teaching:TUW_-_UE_InfoVis_WS_2007/08|UE Informationsvisualisierung WS 07/08]] .
== Gruppenmitglieder ==
[[User:UE-InfoVis0708_0200905|Kremmel, Thomas]]
== Aufgaben ==
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1|Aufgabe 1]]

User:UE-InfoVis0708 0200905

2007-10-24T10:03:39Z

UE-InfoVis0708 0200905:

[[Image:ThomasK.jpg|right|thumb|pic]] 
{|
|''Nachname:''||'''Kremmel'''
|-
|''Vorname:''||'''Thomas'''
|-
|''Matrikelnummer:''||'''0200905'''
|-
|''Studienkennzahl:''||'''926 - Wirtschaftsinformatik'''
|-
|''E-mail Adresse:''||'''thomas (punkt) kremmel (klammeraffe) gmail (punkt) com'''
|}

User:UE-InfoVis0708 0200905

2007-10-24T10:03:10Z

UE-InfoVis0708 0200905:

{|
|''Nachname:''||'''Kremmel'''
|-
|''Vorname:''||'''Thomas'''
|-
|''Matrikelnummer:''||'''0200905'''
|-
|''Studienkennzahl:''||'''926 - Wirtschaftsinformatik'''
|-
|''E-mail Adresse:''||'''thomas (punkt) kremmel (klammeraffe) gmail (punkt) com'''
|}

[[Image:ThomasK.jpg|right|thumb|pic]]

File:ThomasK.jpg

2007-10-24T10:02:23Z

UE-InfoVis0708 0200905: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

User:UE-InfoVis0708 0200905

2007-10-24T08:54:17Z

UE-InfoVis0708 0200905:

User:UE-InfoVis0708 0200905

2007-10-24T08:51:26Z

UE-InfoVis0708 0200905: New page: {| |''Nachname:''||'''Kremmel''' |- |''Vorname:''||'''Thomas''' |- |''Matrikelnummer:''||'''0200905''' |- |''Studienkennzahl:''||'''926 - Wirtschaftsinformatik''' |- |''E-mail Adresse:''|...

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06

2007-10-24T08:46:59Z

UE-InfoVis0708 0200905:

Dies ist die Gruppenseite der '''Gruppe 6''' der Lehrveranstaltung ''UE Informationsvisualisierung WS 07/08''.
== Gruppenmitglieder ==
[[User:UE-InfoVis0708_0200905|Kremmel, Thomas]]
== Aufgaben ==
[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1|Aufgabe 1]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06

2007-10-24T08:40:35Z

UE-InfoVis0708 0200905: New page: Dies ist die Gruppenseite der '''Gruppe 6''' der Lehrveranstaltung ''UE Informationsvisualisierung WS 07/08''. == Gruppenmitglieder == Kremmel, Thomas == Au...

Teaching:TUW - UE InfoVis WS 2007/08

2007-10-24T08:38:49Z

UE-InfoVis0708 0200905: added the group 06