Human-Computer Interaction
CS 6751 Winter 1996
Guidelines for the final presentation
REMINDER: Attendance is mandatory for both
days of final presentations. Class participation in the discussion of
all projects is strongly encouraged.
Graduating students must present on behalf of their development
team. Each team is responsible for two presentations, one from the
developer's perspective and one from the evaluator's perspective. The
same person cannot present both developer and evaluator's perspective.
Since the form of the presentation is Developer-Evaluator-Developer,
it makes sense that the development and evaluation teams coordinate
their presentations to avoid repeated discussion and prepare rebuttals.
It is up to your team to determine who will be planning and presenting
the talk. Remember, your teammates will get a chance at the end of the
quarter to let me know how effort was distributed across the project,
so view this as an opportunity to balance the workload. You have
very little time to discuss a fair amount of information, so you don't
want to waste time changing speakers.
All material used in your final presentation should be made available
through a link on your project notebook page.
The purpose of the final presentation is to have the development team
present the ideas and usability criteria behind the prototype built
this quarter and to allow the evaluation team to present the results
of their independent evaluation of the project.
The presentation will last a total of 20 minutes, with the following
allotment of time:
- Development team presentation (10 minutes)
- Introduction of team members
- Purpose of system built in your project and its role in the
Classroom 2000 scheme.
- Most important functional capabilities of your system. This
should be done in the form of a storyboard presentation describing how
your system is to be used. You should use screen shots from your
system prototype to aid in this storyboard presentation.
- Most important usability criteria for evaluating your system.
- Evaluation team presentation (5 minutes)
- For each of the three evaluation tasks:
- describe what the goal of
the evaluation task was;
- describe how you went about executing the evaluation; and
- summarize the results of the evaluation task.
- Summarize how the prototype meets the usability criteria stated
by the development team.
- Development team rebuttal/discussion (5 minutes)
The development team will be given the chance to comment on the
conclusions drawn by the evaluation team. The entire class will be
invited to give comment on the prototype and its evaluation.
The schedule for presentations is:
- Tuesday, March 5
-
- Audio Annotation
- Virtual Reviewers
- CACD
- ESfINT
- Thursday, March 7
-
- Content-Based Foraging
- Electronic Syllabus Manager
- DreamPad
Back to Winter 96 CS 3302 Home Page