Course Project Information


The purpose of this project is to give you hands-on experience designing and developing an information visualization. You will work with a team to identify a data source that is worthwhile, determine a set of important questions, and design a strategy for exploring that data through an appropriate set of representation and interaction techniques.


M1 Pitch

Presentation: Monday, June 1 in class

Pitch blurb: Monday, June 1 before the start of class

You will briefly pitch your project idea(s) to the whole class. You'll have just 2 minutes each and no slides - like the proverbial elevator pitch. These pitches will give you (and me) situational awareness of what other people are thinking of working on. You might find project partners, either because you find somebody else interested in what you care about, or you're more intrigued by a new idea than your previous plan. You must rehearse ahead of time to get your timing down!

A short description of your pitch (1-2 sentences max) is due on June 1 by the start of class as a submission to T-Square.

[Back to Top]

M2 Short Project Statement

Due: Friday, June 5 by 5pm

You're submitting a statement of intent, not a specification - it's natural that your plans will change somewhat as you refine your ideas. I advise that you start by thinking about what you want your software to do, and only then think about how you would implement it (languages, platforms, etc). The key is to find some domain and task that both interests you and presents an opportunity for infovis. That is, there is some task where a human needs to understand the structure of a large dataset. You're definitely welcome to link the infovis project to another class or research project. You may also build on existing software, but your project should include some implementation work of your own.

I do not advise that you start by deciding on a language, and then look around for some task that you might be able to do in that language - that's backwards, and is likely to stifle your creativity.

Statement format: your writeup should be 1-2 pages and include:

One statement per project team is due on June 5 by 5pm as a submission to T-Square. Submissions should be single-spaced and use no larger than 11pt font (1.5 spacing between paragraphs is fine). Submissions should be in pdf form.

[Back to Top]

M3 Project Design Document

Due: Friday, June 19 by 5pm

You're submitting a design document that should include solid plans for applying information visualization techniques we have discussed in class to your proposed data set.

Document format: your writeup should be 5-6 pages and include:

One proposal per project team is due on June 19 by 5pm as a submission to T-Square. Submissions should be single-spaced and use no larger than 11pt font (1.5 spacing between paragraphs is fine). Submissions should be in pdf form. Submissions should be in pdf form.

[Back to Top]

M4 Status Updates

Due: Friday, July 3 by 5pm

A written project status update is due two weeks after the proposal. Tell me what you've gotten done so far, what obstacles you have encountered, and whether/how your plans have changed as you have gotten to work. The writing style can be more informal than the proposal and the final reports. I want you to spend time on the project not the writing, my goal is to make sure you've all gotten a good start instead of putting things off until the last minute, and to give you feedback if I see any signs of danger.

Document format: your update should be 1-2 pages and include:

[Back to Top]

M5 Final Presentations and Video

Presentations: During class on Week 10, Wed July 15
Video Due: Friday, July 17 by 5pm.

Final presentation length: 12 minutes total, followed by 3 minutes for questions.