Links
- HCI2 Module Description
- Timetable
- The course text (compulsory reading - older edition also OK)
- Spider Page (see also a quick guide to submitting on spider)
- Class Spider news
Overview
To provide the student with a critical appreciation and understanding of both technical and non-technical factors relevant to the production and use of usable systems. This class is jointly taught by Mark Dunlop and Eva Hornecker
The class is taught by lecture and problem-based learning with considerable work outside class (but no labs). The contact timetable is:
- Tuesday 10 - Lecture
- Wednesday 9 - Problem based learning session
Lecture Notes
Lectures will follow the (rough) weekly timetable as below (with lecture notes
appearing as the class proceeds). Please print lecture notes multiple to a page
(4 per page is normally perfectly readable) - see print options for your printer
(maybe under "properties" in the print dialogue). Slides are available
in
PDF format suitable for opening in your browser but with some animation problems
and
Open Document Presentation
(ODP) suitable for opening in OpenOffice or MS Office.
- Introduction to User Centred Design MDD
- Programmers' Guide to the Human MDD
- "
- Requirements Analysis EH
+
- "
- Who are your users? MDD
- Experimental Prototyping EH
- Evaluation EH
- Experimental Design MDD
- Modelling User Interaction MDD
- Graphics Design MDD
- Revision MDD+EH
Problem based learning sessions
Wednesday sessions will be group based, with groups being allocated in the first Wednesday session. The topics covered through Problem Based Learning are as follows (with sheets to follow as the class proceeds). Task sheet n will be handed out in week n-1 and will be due at the noon on the Friday at the end of week n (with the exception of sheet 1!).
- Planning user centred design due 29/1
- Usability rules and heuristics due 5/2
- Non-functional requirements due 12/2
- Criteria for good/bad designs due 19/2
- Affordances in interaction due 26/2
- Conceptual models due 5/3
- Creative methods due 12/3
- Storyboards due 19/3
- Feedback due 26/3
- Designing for emotions due 2/4
- Error safe design due 23/4
- Group allocation to follow
All reports should be submitted physically through the general office. You will need a barcoded cover sheet with your submission (but do each submission as an individual submission by the author, to save getting the signature of all members of the group every week).
Summary peer assessment forms must be submitted in weeks 5 7 and 11. It is a good idea to keep a weekly record of your groups activity for your own memory (but these should not be submitted). Forms: Weeks 1-7 ; Weeks 8-11
Assessments
By default the module is assessed 30% by coursework and 70% by exam.
An exemption scheme will operate - students achieving 70% or more in the coursework will not have to sit the exam. Once all assessed work is marked you will be informed if you have an exemption. If you do, your coursework mark will be your final mark for the module. If you do not achieve an exemption you will have to sit the exam but your coursework will still contribute 30% of your mark.
The assessments are as follows:
- PBL Session Reports (individual reports on group activity 14%)
- User and Requirements Analysis (group 8%)
- can start 17/2, all possible 24/2, due 11/3
- Handout (individual contribution forms to follow)
- System Design (individual 8%) - can start 17/3, all possible 31/3, due 20/4
- Exam (individual 70%)