The final presentation is the opportunity for both
teams involved in the project to show their efforts
and achievements. It should concentrate on the design
and implementation of the user interface for the system,
and on the evaluation and assessment of that user interface.
Each team will give two (partial) presentations, one
from the developer's and one from the evaluator's
perspective. Both the development and the evaluation
team of a given project should coordinate their presentations;
this is part of the duty of the evaluation contact persons
in the respective teams.
The final presentation will be part of the project documentation,
and must be made available on the project Web page.
<------------------- cut here ------------------>
CSC 481 Winter 2002: [Project Name]: Presentation
CSC 481 Winter 2002: [Project Name]: Presentation
Development Team
Team name
email link
Member name
email link
Member name
email link
Member name
email link
Member name
email link
Use the outline below to structure your presentation.
You should recognize most points from your project
documentation, and of course you can use material
from there.
Project Overview (Development Team)
task and purpose of the system
design overview
intended usage
evaluation criteria
evaluation plan
team members and tasks
Project Evaluation (Evaluation Team)
evaluation tasks and methods
for each method, describe
purpose of the method
results
evaluation results
Does the prototype meet the evaluation criteria established by the development team?
What were good and not so good aspects in the performance?
evaluation plan critique
Were the evaluation criteria, and the testing
and evaluation plan appropriate for the intended purpose?
Was the documentation and support provided
by the development team sufficient?
