CMPUT
302
Introduction to Human Computer Interaction
Winter
2014
Instructor:
Pierre Boulanger, Office: ATH 411,
Email: pierreb@ualberta.ca,
Web: http://www.cs.ualberta.ca/~pierreb,
Contact the instructor by email for questions and for making appointments.
Teaching
Assistants: Yuchen Wang ywang6@cs.ualberta.ca
Gregory Burlet gburlet@ualberta.ca
Kai Zhou kzhou3@ualberta.ca
Lecture Time and
Location: MWF 1100-1150, V 102
This course introduces students to topics in human computer interaction,
focusing on human capabilities and limitations, interaction design, current and
future interaction systems and devices, and methods for evaluating interaction
systems.
You will gain an understanding of:
1. The
characteristics and limitations of human perception, cognitive processing and
actions
2. The design
of systems and devices suitable for efficient human computer interactions
3. Current
and future interaction systems
4. The
evaluation of interactions and interaction systems
The course will cover the following topics:
Introduction and
overview
o Definition
of HCI
o Why HCI is
Important?
o Usability
Requirements
o Understanding
Users
o Requirements
Analysis
o Software
Engineering and HCI
User Centered Design
and Prototyping
o System
Centered Design
o User
Centered Design
o Case
Studies
o Participatory
Design
o Design
Rationale
o User
interface prototyping
o Paper-based
prototypes
o Software-based
prototypes
o Where Does
All This Fit Into the Software Engineering Process?
Sensation, Perception,
Cognition
o Science
Fundamentals
o Psychophysics
(psychophysical methods, psychometric function, thresholds, perceptual
magnitude)
o Visual
perception - low level
o Visual
perception - high level
o Auditory
Perception
o Haptic /
kinesthetic perception
o Attention
o Motor behavior,
ergonomics
Experimental Design and
Analysis
o A Model of
Usability Factors
o Ethics,
experimental planning, basic terminology
o Experimental
design
o Statistical
analysis (t-test, F-Test, correlation/regression)
o Anova (simple, post-hoc tests)
o Anova (factorial and mixed, assumption testing, post-hoc
tests)
o Non-parametric
analysis (nominal and ordinal scale)
Interaction Systems 1
o Visual:
eye movements
o Visual:
gesture reognition
o Haptic: haptic
guidance
o Multimodal
interaction
Interaction Systems 2
o Tabletop
interfaces
o Tangible
interfaces
o 3D
interfaces
o Virtual
and augmented reality
o Emotional
computing
o Wearable
computing
o Brain
Computer Interface
The course builds upon knowledge and
skills acquired in CMPUT 301 Introduction to Software Engineering. Bear tracks indicates
that CMPUT 301 can be taken as a co-requisite, but I
cannot wait for certain topics to be covered in that course. If you are taking
it as a co-requisite, you must consult textbooks and online materials on CMPUT
301 topics, including software development process, classical user interfaces,
design patterns, refactoring, and more. Otherwise, you will not be in a
position to contribute adequately to the team project.
There is no textbook. There
are excellent resources for this courses, available as books you can buy from a
variety of suppliers, or available through open access on the web. I will
provide pointers to such resources on the Course website.
Your final mark is based on the following components:
|
Course Work |
|
Due Date |
Weight |
|
Assignment 1 |
|
February 15 |
10% |
|
Assignment 2 |
|
March 7 |
10% |
|
Project |
Team preferences |
January 13 |
0% |
|
|
Design |
February 14 |
5% |
|
|
Ethics |
March 7 |
5% |
|
|
Halfway prototype |
March 24 |
10% |
|
|
Presentation + Demo |
April 9 |
10% |
|
|
Final report |
April 12 |
20% |
|
|
Total |
|
50% |
|
Final |
|
April 17 at 9h00 in V-102 |
30% |
|
Deferred Final |
|
TBA |
30% |
Please review the Departmental
Course Policies very carefully.
The assignments must be done
individually. You can discuss the concepts with your class
mates, but these discussions are limited to an informal level. You must
develop your own solution for the assignments. I do not allow exchanging any
written text, code, or giving detailed step by step
verbal advice. Do not give other students access to your solutions and do not
seek access to other's solutions. This is considered
plagiarism. I reserve the right to give you an exam (class quizz,
oral, and/or written) to determine the degree that you understand what you submitted.
The course project is produced in teams of 5 members. All team members must understand all components
of the deliverables. For example, every team member must prepared for an
individual inspection/walkthrough in which you explain what every line of
your code, design, documentation etc. does and why you chose to write it that
way. This may impact the mark that you receive for the
deliverable. For every deliverable, each team member will comment on the
contributions of the other team members to allow me to find problems in teams
or with particular team members. If I find that a team member has not
contributed adequately to the team effort for a project component, I may decide
to reduce the mark for that member, and I have done so in the past.
Regardless of the collaboration method allowed, you
must always properly acknowledge the sources you used and people you worked
with. All sources of information used, e.g., books, websites, must be cited in
all deliverables.
Assignments and project components must
be submitted in hardcopy as well as in electronic form by sending me an
email. The assignments are due on the due date at the beginning of the lecture.
Important: Late submissions of assignments and project components will not be accepted. Plan your work on assignments and
projects accordingly. All projects involve the use of special hardware. For
this reason, do not try to finish the project in the last moment. Otherwise,
you are likely to fail.
A student who cannot write a term assignment due to
incapacitating illness, severe domestic affliction or other compelling reasons
can apply for deferral of the term work weight to the final exam. Deferral of
term work is a priviledge and not a right; there is
no guarantee that a deferral will be granted. Misrepresentation of facts to
gain a deferral is a serious breach of the Code of Student Behaviour.
Any questions or concerns about marks on an assignment
or project component must be brought to my attention
within seven days of its return date. After that, I will not consider remarking
or re-evaluating the work
Students may only submit work authored by themselves,
or with approved co-authors. Work either submitted by a student that is the
work of someone else (e.g. another student or a tutor) in part or in entirety is considered plagiarism. This also applies to work that
previously submitted for another course. Please review the Don't
Cheat Sheet (PDF) for more information.
The University of Alberta is committed to the highest
standards of academic integrity and honesty. Students are
expected to be familiar with these standards regarding academic honesty
and to uphold the policies of the University in this respect. Students are
particularly urged to familiarize themselves with the provisions of the Code of
Student Behaviour (online at www.governance.ualberta.ca ) and
avoid any behaviour which could potentially result in suspicions of cheating,
plagiarism, misrepresentation of facts and/or participation in an offence.
Academic dishonesty is a serious offence and can result in suspension or
expulsion from the University.
Cases of plagiarism and other forms of cheating are immediately referred to the Dean of Science, who
determines what course of action is appropriate. We do not hesitate to send ALL
cases of cheating to the Dean's office. Please do not put yourself or us into
such an unpleasant situation. Please read the Code of Student Behavior
carefully. For up-to-date information, please visit http://www.ombudservice.ualberta.ca/en/ReferenceShelf/AcademicAppeals.aspx .
Audio or video recording of lectures or any other
teaching environment by students is allowed only with
the prior written consent of the instructor or as a part of an approved
accommodation plan. Recorded material is to be used
solely for personal study, and is not to be used or distributed for any other
purpose without prior written consent from the instructor.
You must use your
Campus Computing ID CCID.
Your subject line
must begin with your course number, e.g., Subject: CMPUT 302 Assignment 2
Identify yourself
using your full name.
Be precise, and
attach all code if relevant.
Be aware of the University
Electronic Communication Policy.
If you are registered with Specialized Support
and Disability Services (SSDS) and will be using accommodations in the
classroom or the lab, or will be writing exams through SSDS, you are required
to provide a "Letter of Introduction" to your instructor as soon as
possible. If you need accommodated exams, you must provide your instructor and
lab coordinator with an "Exam Instructions & Authorization"
(orange) form one week before each exam. You are encouraged to make an
appointment with your instructor and lab coordinator to discuss any required
accommodations.
For students who write exams with accommodations at SSDS, please be cognizant of their deadlines and
regulations. If you fail to meet these deadlines or follow the procedures, the
result is most likely that SSDS will be unable to provide the necessary space
and/or services you require. In these situations, the Department of Computing
Science does not have the resources to provide disability- related exam
accommodations, and you will be invited to write your
exams with peers during the allotted time in the assigned room.
Students who require additional help in developing
strategies for better time management, study skills or examination skills
should contact the Student Success Centre (2-300 Students’ Union Building).
Any typographical errors in this Course Outline are
subject to change and will be announced in class.
Please review the Departmental Course Policies https://www.cs.ualberta.ca/resources-services/policy-information/department-course-policies very carefully.
The University policy about course outlines can be found in §23.4(2) of the
University Calendar.