Final Project

Deadline Timeline

Note: Deadlines are at 1pm on the day listed

• 10/5/15 Project out
• 10/13/15 Team formation DUE (email team members to nad@umd.edu)
• 10/26/15 Project Proposal DUE (email to nad@umd.edu)
• 11/23/15 Project Progress Report Presentation DUE (in class presentation)
• 12/7/15 Final Project Presentation DUE (in class presentation with guest evaluators)
• 12/11/15 Final Project Report DUE (email to nad@umd.edu)

Project Description

Your final data visualization project should show that you have integrated the knowledge you acquire in this class and are able to apply it in the design and implementation of a data visualization story package.

You’ll do this project in teams of 2 or possibly 3 people. If you work in a group of three people please note that your project will be expected to reflect an additional person’s time and effort.

To start, you’ll need to find a dataset or datasets that are interesting and which you think will provide a fertile bed for an interesting or even newsworthy visualization-based story. Finding data can be very time consuming, so please start on this as soon as possible (you might start with https://app.enigma.io/search, http://data.gov, or any of the sources linked in this article; there are many sources of data online that you might find or collect. The data can be national or local, or something else entirely, but try to find something that might have some news value or interest. The data you find may need to be cleaned and wrangled into a shape before you can really start working with it; you might want to read up more on data wrangling or review the lecture slides on data again. Once you’ve settled on a dataset that you find interesting you should spend some time understanding the variables in that dataset. Each dataset is different and some of them have special terminology that you may need to research in order to understand. What do the variables mean? How were they measured or collected? You need to fully understand your dataset before you can build a presentation to help other people understand it easily.

Then you’ll do some exploratory visualization (you’ll also practice this with Tableau in assignment #2) to find some potential angles or interesting observations about the data. You can begin to sketch out ideas for how you want to present the data and visualization as part of a broader story. You will design visualizations, mappings, colors, interactions, and an information layout that ties everything together. What’s the story that you want to tell with this data? How can you help end users experience that story and understand what you’re communicating? Depending on the data types in your data set will you use charts, timelines, maps, network diagrams, or something else entirely?

Finally you’ll implement your designs in HTML, CSS, and javascript. We’ve been learning D3 in the course however this using D3 in the final is not mandatory. If there are other tools that help you tell your story more effectively with visualization you are welcome to use them.

Project Team
Please find teammates as soon as possible and see the instructor if you're having trouble finding a team. Each team should send an email to nad@umd.edu to indicate who is on the team by the deadline listed above.

Project Proposal
Your project proposal will succinctly describe (~500 words) what you intend to visualize and why that is an interesting and potentially even newsworthy story. You should have already spent time collecting some data and doing some preliminary exploratory analysis. In the proposal write-up include information about the data you have acquired, what the data describes, where you got it, how you processed or cleaned it, and any limitations you have identified. Does the data speak to the kinds of questions you want to answer? Also describe what you think the story might be based on your initial exploratory visualization and analysis or other reporting you have undertaken. Include sketches or early mockups that show how you are conceptualizing the story and its presentation. Also look ahead and describe any challenges you foresee in how you will implement your ideas.

You should email a PDF to nad@umd.edu with a file name of "Final_Project_Proposal_<project_title>.pdf" by the deadline listed above.

Project Progress Report Presentation
In order to help assess the strengths and weaknesses of your project you will have ~20 minutes to present your project to the class on the date listed above. This presentation will give you a chance to both receive feedback from other class members as well as to offer your own critiques of their work. You should have some aspects of your visualization project implemented and you can use this time to demo what you have, explain the intent of the project, the design process or storyboards, and the emerging story. Make sure to describe and motivate your project for the class, and describe what you have left to work on. Is there anything you need help with?

Final Project Presentation
Final project presentations of ~20 minutes will be made in class on the date listed above. This should be the buffed up and polished version of the progress report presentation you gave previously. Make sure to motivate the project, explain the data you used, how you visualized it and implemented it, and what the story is. This will be an open “public” session with other people from throughout the college invited to see your projects. For all intents and purposes your project should be done by now.

Project Report
Your project report is due via email to nad@umd.edu as a PDF with file name “Final_Project_<project_title>.pdf” by the date listed above. Also include a .zip file of your project's code so that it can be loaded and viewed (if you have a server where you are hosting the project please also include a link). In addition to the information that you presented in your final project proposal and final project presentation, please also describe and reflect on your project. Why did you decide to design the visualizations the way you did? What was hard or easy about the project? What would you do differently next time? Please also describe in some detail the work that each team member did and how it was broken out.