The purpose of this assignment is to provide you with some experience designing a visualization from scratch. You will use the examples that we have discussed in class to design an effective visualization of spatial data. This assignment must be completed on your own. Each part is equally weighted: please follow the submission guidelines on T-Square to receive full credit.
In this assignment, you will design a visualization for a data set and provide a rigorous rationale for your design choices. You should in theory be ready to explain the contribution of every pixel in the display. You are free to use any graphics or charting tool you please--including drafting it by hand. However, you may find it most instructive to create the chart from scratch using a graphics API of your choice.
Your task is to design a static (i.e., single image) visualization that you believe effectively communicates the data. While you must use the data set given, note that you are free to transform the data as you see fit. You are also free to incorporate external data as you see fit. Your chart image should be interpretable without recourse to your short write-up. Do not forget to include title, axis labels or legends as needed! Feel free to draw upon the examples described in class, in the textbook, and from assigned readings for inspiration.
Grading: We will evaluate the quality of your design with respect to the data available. We will evaluate if you followed the directions and estimate the quality of your design choices. We will determine if you followed the rules of thumb and design criteria discussed in class.[Back to Top]
You should provide a short write-up (no more than 1 page) describing your design. As different visualizations can emphasize different aspects of a data set, you should document what aspects of the data you are attempting to most effectively communicate. In short, what story (or stories) are you trying to tell? What tasks does this visualization support? Just as important, also note which aspects of the data might be obscured or down-played due to your visualization design. In your write-up, you should provide a rigorous rationale for your design decisions. Document the visual encodings you used and why they are appropriate for the data. These decisions include the choice of visualization idiom, size, marks and channels, as well as the use of sorting or other data transformations. How do these decisions facilitate effective communication?
Grading: We will evaluate the quality of your design justification. We will evaluate if you followed the directions and estimate the quality of your rationale. We will evaluate how well you justify your choice of attributes, tasks, and visual idioms based upon the material we've covered in class so far. Please proofread your submission before submitting it and make sure it is free of spelling and grammar issues.[Back to Top]
Shakespeare's Romeo and Juliet: Co-occurrence Network [xlsx]
The workbook contains two sheets: Summary and Scenes. In the Summary sheet, you will find a co-occurrence network of all the major characters in William Shakespeare's Romeo and Juliet. This data is stored as an adjacency matrix. Each time any two characters are in the same scene of the play, the link increases in magnitude by one. The identity link (e.g., RO x RO = 13) indicates the total scenes each character appears in. The second sheet, Scenes, provides the full information for which characters appear in the scenes of the play. The scenes are organized by Act. The second sheet is also a key to the abbreviations used in the first sheet (e.g., RO = "Romeo, son to Montague"). You are required to utilize the data in the adjacency matrix on the Summary sheet. You may use the scenes information if you choose to enhance your visualization, but it is not required. If you are familiar with the story, you are encouraged to use your knowledge of the material towards improving the effectiveness of your design. If you are not familiar with the story, many summaries are available online and the full text is available on Project Gutenberg.