J. Blustein

CS 4163: Human-Computer Interaction


Contents of this webpage


Last updated: 13 May

PDF version (with links)
approx. 240Kb
Postscript format
approx. 192Kb


groups.htmls (last updated: 14 May)


09 June
New due dates for many phases announced (see table below)
31 May
Task Analysis due date changed to Wed. 05 June

Due Dates

Project Due Dates
Milestone New Due Date
User and Feature analyses 27 May (Thurs.)
Task analysis 05 June (Wed.)
Design document 26 June (Wed.)
Testing strategy 08 July (Mon.)
final deadline to get consent form approved 16 July (Tue.)
Demonstration 22 July (Mon.)
Final Revision and 29 July (Mon.)
Group work report and 02 August (Fri.)
Lessons learned

Informed Consent

Informed consent is essential for human experimentation regardless of how simple the experiment or how slight the risk. You must have each participant in your tests give their permission to: participate in the experiment and for you to use the data collected from their participation. Their permission must be informed, i.e. they must know what they are being asked to do and what risks and benefits might arise from their participation.

The form that you use must be approved by an independent review. Because this project is part of a course you can have it reviewed by the Faculty of Computer Science Ethics Review Committee. Dr. Watters is the sole member of that committee and you will need to obtain her approval of your form before you can use it to obtain informed consent.

I have prepared a boilerplate consent form in text format for you to adapt to your specific experiment. You may want to include additional details about your experiment in it but be careful not to exceed one page because then people won't want to read it.

The boilerplate form is in consent.txt. There are some examples on reserve in the library about testing and experimental consent (by Nielsen and Shneiderman).

The HTML sample consent form includes an image you can use to make your own `letterhead'.

Advice from Walt Maner

Formative Evaluation,
Scenario-based Testing
Rapid Application Development,
Iterative Prototyping (as part of rapid application development)

09 June 2002
J. Blustein <jamie@cs.dal.ca>

Valid XHTML 1.0!

Jump to top of webpage | contents list