Last changed 15 March 1998 ............... Length about 900 words (6,000 bytes).
This is a WWW document by Steve Draper, installed at http://www.psy.gla.ac.uk/~steve/HCI/hos.html. You may copy it. How to refer to it.

(Back up to main page for HCI module)

HCI course handouts

HCI course handouts
Number
Content
Medium
A
Official module description
Course handbook
Web page
B
Exercise D1 (CSCLN web page lecture notes)
Web page
1
Course notes for lectures 1,2
Paper handout
2
Diagrams
Paper handout
3
Exercise D2(bug report)
Paper handout
4
User interface performance measurement
Huge paper handout
5
Exercise B (questionnaire and interview)
Extra help with the report
Paper handout
6
Checklist
Paper handout
7
Diary example
Paper handout
8
Ex.D3 Experiment exercise
Paper handout
9
Ex.A The major exercise
Paper handout
Web page
C
WWW: how to author web pages
Web document
D
Hypercard handout
Clarisworks file for printing in ITlib:HCI folder
10
HCI theory: theory of action etc.
Paper handout
11
Ex.C (applying the theory of action)
Paper handout
12
Interface styles
Paper handout
13
Revision notes: Interaction techniques
Paper handout
14
User Interface Implementation Support
Paper handout

Assessment and deadlines

See also the handbook spec..

Assessment and deadlines
What
Worth
Deadline
Exam
60%
May?
Ex.A Iterative design and testing
20%
End of term 2
Ex.B Questionnaire & interview
8%
3 Feb.
Ex.C Written theoretical exercise
8%
Last lecture of term
Ex.D1 CSCLN on the web
1.33%
7 days after the lecture
Ex.D2 Critique of an interface
1.33%
27 Jan
Ex.D3 Experiment
1.33%
10 Feb


My views on assessment and learning in this course

[Email sent to the class on 9 March 1998]

The class rep., Scott Goodwin, tells me that many of you are agitated about the notional reduction to 1.33% from 2% credit for each of the "D" small exercises. To me, from the other side of the fence, this couldn't be further from the point. My belief is that possibly in any subject but certainly in HCI you learn from doing the exercises: not from reading, or listening to me lecture, or writing the exam. I do not have good experimental evidence for their learning value, but it corresponds to the experiences I remember as important to me in developing what I know about HCI. If you did the exercises seriously and nothing else, I expect you would have learned something useful. If you read the handouts and did the exam but not the exercises, you would probably have learned nothing of value.

The management and examiners on the IT course dictate that I must use 60% of the marks on an exam, and what the form of the exam should be. They do so even though writing an exam question has nothing much to do with HCI because in an exam it is easy to be confident that an answer is all that student's work, while for practical coursework it is not.

This leaves me only 40% to allocate between the exercises. I do that to indicate their relative value to each other, and to indicate that I think they are valuable to do. But with only 40% to go round, some of the marks look very small. Nevertheless, that I believe is where your best learning may take place. There is nothing very unusual about this. The maths I learned from primary school to university always relied on doing numerous examples, and there was no nonsense about getting credit for it outside exams: that is just what learning maths involves. What is sad is if you think the only point of doing such work is to get marks, rather than to learn or understand some HCI. To a great extent we (teachers) have brought this on ourselves. Over the last 10 years there has been a marked trend in the IT course towards more and more firm deadlines, penalties, and rewards by marks. This has been good in that far more students work in a regular and orderly way now, and considerably more work of a reasonable standard is done. But it is bad because it further reduces the personal choice and responsibility of students over what they learn and do.

Your real choice as a student is whether to try to get high marks without caring whether you learn anything worthwhile, or to try to learn the most useful stuff while ignoring marks, or both: to learn what is most worthwhile while politely putting up with a marks system that is at best loosely connected with that. Occasionally past students who meet me again say how this HCI course made a deep impression on them, and even changed how they looked at things. Then I know that at least a few students really learned something. But one reason why I haven't campaigned harder for a different assessment system is that I can't imagine one that would be acceptable and yet test what matters. What matters in HCI above all is not knowing some fact, but having a different attitude: one that will make you argue with employers to try a prototype early on, to pay for user testing and to do all this several times during the design process. How could I test whether you really believed that and how hard you would fight for it? The concepts I lecture on offer one basis for belief (and for justifying it to others); the exercises offer another, perhaps more important. If you have had the experience, which I try to contrive in ex.A but cannot guarantee for each of you, of building a user interface you actually think is pretty neat and bound to please others and then see friends of yours nevertheless have trouble even though they want to be polite to you, then you really get the message that testing makes a difference. When asked, you would be able to say that you have seen the difference it makes with your own eyes.

In the end, the marks are one way I have to say I believe the exercises are important to your learning. This message is another.