HCI II is an advanced HCI course, covering material in more depth. It is taught using a combination of personal study and reading, classroom interaction, group work and conventional lectures.
Ongoing approaches for the course are the design exercise documented in the blogs, the course reading and the associated lectures. These are detailed in the table below.
New blog list here (with contact details of students - note: not checked since received from office - let me know of errors. If the error is you're not in a group of 5 and never have been, contact others who aren't as well).
Mock exam here - answers at the bottom of the page.
Revision notes here [ppt] and here [pdf].
Exam guidance here.
Blogs will be assessed as a group contribution. Deadline: end of semester. Full details of assessment are here.
HCI Extended: you have to write a blog entry on a research topic on computer science. You must submit the permalink address and your name to the school office by 5pm on the last day of the semester. The entry should be no more than a page. You shold briefly review the field, link to the relevant papers where appropriate, and give your views on the technology and its potential.
| Week | Design activity | Blogging activity | Course Reading
|
Lecture |
| 1 | ||||
| 2a | Get into threes, identify domain/product/concept | Set up project blogs. Ensure your full names are in the blog sidebar. Make sure you all have logins to the blog. |
IBM's site on UCD - read most if not all of it
|
What is user-centered design? How does it different from conventional software engineering? Why do it? |
| 2b | In pairs of threes, brainstorm concepts for product | Start blogging | MindTools creativity approaches
|
Approaches to creativity and design; brainstorming |
| 3a | Do detailed problem definition, user needs analysis, task analysis, scenarios, etc. Collect results in lab book/folder/box file |
Send blog details to front office. Set up blogrolls or similar to point to other blogs you like (include some of your fellow students) |
UCD: Problem definition, user needs analysis, scenarios Personas
|
|
| 3b | Groups outline ideas to lecturer and demonstrators |
|||
| 4 | Identify key users and get their views (interviews, questionnaires, surveys, observation etc.) Questionnaire, or task analysis, on either users or persona set. Define key use cases and key scenarios |
Document, document, document | Getting around the task-artifact cycle: how to make claims and design by scenario |
Finding out what people want Ethnography, cultural probes. |
| 5 | Start prototyping - paper and post-it's, powerpoint or HTML | Capture prototype in blog - describe in detail, show in use cases or scenarios | Old and Young Design information
|
UTOPIA project |
| 6 | Continue prototyping | Document prototype | Designing for (and with) kids | |
| 7 | Test design on persona |
HCI Extended: research topic selection |
2 example personas [1, 2] and results | |
| 8 | Evaluation. Learn design lessons |
Comparison of evaluation methods (1 page) Heuristic evaluation: Nielsen (follow the main links too!) |
Evaluation approaches | |
| 9 | Redesign Build improved prototype |
Document improved prototype - interactive ones are great, images or screens are fine, sketches are just about acceptable, only minor tweaks are not acceptable |
Anything on context-aware systems, mobile systems, or design approaches: a couple of papers, or reviews, or similar | Context-aware systems |
| 10 | Re-evaluate | Finalise description of revised prototype. |
|
|
| 11 | Conclude | |||
