SIMS 247 Spring 2002 Project Proposal
This course requires a final project. This can consist of designing
a new visualization (that solves a problem or sheds light on a
dataset), doing usability studies to assess the efficacy of an
existing visualization, or applying known visualization techniques
to an interesting problem. Other ideas are possible, subject to
instructor approval.
The first step is to write up a proposal and have it approved by
the instructor.
Project groups should have 2-3 people.
To do:
- April 5: Turn in a short description of a project proposal.
I will review it and give you feedback. If it is ok, then
you're done, but I might want an iteration. This description should
include:
- Name(s) of student(s) involved
- Project goals, including what kinds of tasks the interface containing
the visualization is targeted towards.
- What data (if any) will be used to accomplish the goals.
- Which tools will be used to accomplish the goals (this can change if
needed).
- What steps will be required to accomplish goals.
- What kinds of results you anticipate achieving.
- What kinds of results you would like to achieve but which you probably
do not have the time or the tools for.
- April 12: Finalized version of project description, on a topic that I have
approved.
- May 10: Students present final projects in class
- May 13: Writeups due.
Grading:
- Class presentation of project results (must fit within designated time
limits which are TBA) (25%)
- Quality of writeup of results (25%)
- Quality of actual project (50%)