Working in groups of 3 people, build, install, and evaluate a visualization of an existing set of WWW pages, or create a tool for creating visualizations and evaluate the results. The visualization could be a set of Web pages using image maps, a 3D VRML model, or a 2D or 3D map with active elements implemented in Java. Our objective is for the teams to include members with varied and complementary skills. (Note - we are open to suggestions for other types of team or individual projects which fit both your personal objectives and the overall thrust of the class.)
Decide in advance the set of tasks against which your design will be optimized and tested. Keep one fundamental rule from user interface design in mind: there is no 'ultimate' design. There are only designs that more or less support a certain task. In this case the tasks are navigation, finding information, learning the structure of this information space,...
Evaluate your design by user testing (do some really simple tests at an early stage). This usability testing has to be quick and dirty - "discount usability engineering." as Jakob would say. Be concerned with issues like major navigational paths and frequently visited pages. Do the testing at workstations, not in the usabilty lab; run four evaluators for 15 to 30 minutes Focus on learning from their "talking out loud", by watching what they do, and by debriefing them afterwards. Don't try to do measurements or questionnaires. Do develop a task script which the evaluators follow for at least part of the session. The script should include the tasks you designed toward.
Teams will be formed in class on April 17. You are encouraged to develop teams before that time by getting to know your class mates. Talk with us about your ideas as they evolve prior to April 17, and afterwards as well.
Before class on April 24, post to the class newsgroup a brief (on the order of 300 words) description of your group project and a membership list.
Before class on May 8 post to the newsgroup a status report describing what has been accomplished to date and what is yet to be done, in check-list form. Indicate who has done each completed item and who is responsible for each to-be-completed item. Likewise on May 22. (The purpose here is to encourage some explicit project management and to alert us to difficulties you may be having.)
During the two classes the week of May 27-31, each team will give a 15 minute presentation. We will try to have live projection of your project so you can demonstrate. Plan your presentation to include an introductory overview of why and how you did what you did, then show what you did, then discuss the results of your usability testing.
Turn in hard copy of your presentation foils and the URL or execution instructions for your visualization.
[CS6364 page] [calendar] [Reading] [Assignments] [Resources] [Webpointers]
last modified on 6/3/96
Andreas Dieberger