CPSC 481: Foundations of HCI

James Tam (instructor)

Project Demonstrations

General information

  • Your group needs to sign up ahead of time for a demo slot (the list will be outside my office sometime near the end of the term).

  • All group members must be present during the demo to receive a grade for the project.

  • Each group will have a maximum of a half an hour.

  • Demos will take place in the regular tutorial room using the machines in the lab.  Hint: If you work at home then you should periodically import your code here (perhaps once a week, more often as the deadline approaches) and check that it works on the machines/display resolutions here.  It is your responsibility to ensure that your program will work on the lab machines.
  • During the day of the demo: Well ahead of time make sure that your system is working and ready (I won't have time to do this for you) so you aren't late when your allotted time comes up.  If you are late in getting set up, your group won't be provided with additional time.

  • You can assume that I am familiar enough with your portfolio and system that I don't need an introduction about what you did.
  • The idea is for your group to show the outstanding parts of your system (it's your opportunity to shine rather than my stress testing it looking for bugs).

  • Don't worry if there a few minor bugs (unless it is so bad that your system is constantly crashing so I can't really tell how it's supposed to work).

  • Demos will vary depending upon the situation but generally there are three main parts:

 
  • Introduction: I briefly remind you all of how the demos will be run  (as a quick reminder!)
 
  • The main demonstration: I will be using the system but mostly your group members will be directing me as to which parts of the system that I should be looking at (make sure that you try to show me as many of the strengths of your system as you can - I suggest that you prioritize them in a list beforehand to make sure that there will be time for me to see the really outstanding parts of your system).
 
  • Debriefing: I give your group a brief overview of your system's strengths and areas of improvement (all projects, even the best ones can still be improved upon).  Because I need to see all the projects before assigning grades as well as reading through your portfolios I won't immediately provide a mark at this point but I will post the project grades as soon as I have them available.