The course highlights the design, development, and evaluation of
human-computer interfaces, with an emphasis on usability, interaction
paradigms, computer-mediated human activities, and implications to
society. These issues are studied from a number of perspectives
including that of the engineer and end-user.
A
team-based
project applies your knowledge and skills to the full life cycle
of an interactive human-computer interface.
You will gain an overview of Human-Computer Interaction (HCI), with an
understanding of user interface design in general, and alternatives to
traditional "keyboard and mouse" computing; become familiar with the
vocabulary associated with sensory and cognitive systems as relevant
to task performance by humans; be able to apply models from cognitive
psychology to predicting user performance in various human-computer
interaction tasks and recognize the limits of human performance as
they apply to computer operation; appreciate the importance of a
design and evaluation methodology that begins with and maintains a
focus on the user; be familiar with a variety of both conventional and
non-traditional user interface paradigms, the latter including virtual
and augmented reality, mobile and wearable computing, and ubiquitous
computing; and understand the social implications of technology and
their ethical responsibilities as engineers in the design of
technological systems. Finally, working in small groups on a product
design from start to finish will provide you with invaluable team-work
experience.
Many students have commented that this should be a 6-credit course. But it's not.
(from a 2004 on-line course evaluation): "I do know that I have
worked harder in this course than in some 5 credit courses I have
taken and probably will not do as well. This is more than made up
by the interesting content of the course and overall quality of the
lectures. Someone just interested in their GPA would be better off just
sitting in on the lectures if they could."
(from a non-student's comment): "I do remember students who took your
classes. They were clearly divided as those who complained saying
that you were a hard grader and expected them to do work, and those
who were appreciative for the hard work and what they learned. All
those who were willing to do work thought you were a great educator."
(Full disclosure: Not all students agree with that comment.)
If you're a regular ECSE student, you already know the drill.
Non-ECSE students wishing to enroll in this course must submit a brief
statement to me, summarizing your relevant background, reasons for
taking the course, what you expect to contribute, and what skills or
experience you hope to gain from it. Graduate students wishing to
enroll should select ECSE-689, confusingly named as "Recent Advances:
Electrical Engineering 2". Note that for graduate credit, an additional
project component or small seminar project will be required as a part
of your term grade.
Each week, selected readings, all available on-line, will be assigned.
As such, there is no official text required for the course, although
many good HCI references are available, some on reserve in the
Schulich library. Students are expected to complete their assigned
readings each week. Note that you must be logged on to a McGill
computer system (e.g., via VPN) in order to download the readings from
the ACM web site.
Your marks will be based largely on the term project (55%), which
includes an end-of-term presentation, in-class and take-home exercises
(10%), a final examination (30%), in addition to participation and
contribution to in-class and on-line discussions (5%). The term
project will be done in groups -- ideally two-to-three students per
group. Each member must take on a primary responsibility of at least
one component and identify his or her role. While team members may
work together on multiple aspects of the project and are encouraged to
do so, specific responsibilities of each member must be delineated.
If you're a grad student taking the 600-level version of the course,
an additional project-related component will comprise 20% of your grade.
All assigned work is due at the start of class on the assigned date.
At that time, a web agent will collect all of the material from the
project web pages and copy it to a private directory. You may
continue to modify your web pages beyond the deadline, but any such
changes will not be seen by the marker. In cases of illness or other
compelling reason warranting an extension, the group must notify the
instructor at least one week in advance of the due date, in order to
make special arrangements. Barring such advance notice,
no credit
will be given for late work.
| Week of |
Topic |
Guests/Videos |
Readings |
Material Due weight |
Lecture Slides |
| Jan. 3 |
Introduction: Use and Context, Terminology |
Alan Kay (video part 1 | part 2) |
Norman, The Psychopathology of Everyday Things (missing pages to be provided) | Norman, Affordance and Design |
Raskin, Intuitive Equals Familiar
|
Exercise 1: Yearbook |
Jan 5 | Jan 7 |
| Jan. 10 |
User-Centered Design, Understanding and Observing Users |
André Gascon (Jan. 12) |
Gould, The 1984 Olympic Message System | IBM, Cost justifying ease of use | Snyder, Paper Prototyping
|
Exercise 2: Design Critique |
Jan 12 | Jan 14 |
| Jan. 17 |
Use Case Scenarios, Personas, and User Modeling |
Adriana Olmos (Jan. 19) |
Thompson, Personas | Business Week, The IDEO way |
|
Jan 19 |
| Jan. 24 |
User Experience, Usability Requirements, and Low-Fidelity Prototyping |
David Rollert (Jan. 26) |
Norman, Emotional Design | Berry, The User Experience |
|
Project Proposal 6% |
Jan 26 | Jan 28 |
| Jan. 31 |
Usability Testing, Interaction Design and Analytical Evaluation |
Bill Moggridge (Designing Interactions video) |
Nielsen, How to conduct a heuristic evaluation | Dickelman, Fear and Loathing on the Keyboard | Tognazzini, First Principles of Interaction Design
|
|
Feb 2 |
| Feb. 7 |
Models and Theories: GOMS, MHP, Fitts' Law |
Michael McGuffin (Feb. 11) |
Buxton, Chunking and Phrasing
|
Low-Fidelity Prototype 2% |
Feb 9 | Feb 11 |
| Feb. 14 |
Accessibility and Risks: Error Classification, Automation, Designing for Error |
Gary Perlman (Feb. 16) |
Nielsen, Accessibility is not enough | Norman, Human error and the design of computer systems |
Leveson, The Therac-25 Accidents (pp. 1-8, 21-22, 44-49) |
Weiser, The Technologist's Responsibilities
|
Test Plan 4% |
Feb 16 | Feb 18 |
| Feb. 21 |
Study Week
|
|
|
| Feb. 28 |
Graphics and Sound: GUIs, speech and non-speech audio |
Mike Mills (Mar. 2) |
Buxton, Speech, Language, and Audition | Raskin, Down With GUIs!
|
Computer Prototype 10% |
Mar 2 | Mar 4 |
| Mar. 7 |
Multimodal Interfaces and Ubiquitous Computing |
Jerome Pasquero (Mar. 11) |
Weiser, The Computer for the 21st Century | Oviatt, Ten Myths of Multimodal Interaction |
|
Formative Feedback 5% |
Mar 9 | Mar 11 |
| Mar. 14 |
Gestural Interaction and Tangible User Interfaces |
Marcelo Wanderley (Mar. 16) |
Billinghurst, Gesture Recogntion | Fitzmaurice, Bricks | Ishii, Tangible Bits
|
|
Mar 16 | Mar 18 |
| Mar. 21 |
Affective and Social Computing |
Hal Myers (Mar. 23) |
Picard, Affective Computing | Bigham, VizWiz |
|
Alpha System 10% |
Mar 23 | Mar 25 |
| Mar. 28 |
Augmented Reality and CSCW |
Mike Wozniewski (Mar. 30) |
Wellner, Interacting with paper on the DigitalDesk |
Buxton, Integrating the periphery and context
|
Peer Critique 5% |
Mar 30 | Apr 1 |
| Apr. 4 |
Project Presentations |
Presentation 10% Improvements on Alpha 3% |
|