Paper
Outline for 158.359 Human-Computer Interaction
Paper Number and Title: 158.359: Human-Computer Interaction
Credits Value: 15 Semester: S2
Campus:
Paper Coordinator: Brian
Whitworth
Other Contributing Staff: Tong Liu, t.liu@massey.ac.nz
Aim: To introduce students to the importance
of Human-Computer Interaction in IT system evaluation, design and development.
By linking human factors to IT factors, the course develops human-centred
design principles to create user-friendly information and communication
systems. It is a seminal paper for any graduates who want to develop systems
that people enjoy using. It provides guidelines to system development based on
what we know about how people work.
Calendar Prescription: Analysis, design, prototyping and evaluation of interfaces to allow efficient and effective use of interactive systems, focusing on the user-centred design approach as a key part of the software development lifecycle. Practical examples will be taken from areas such as multimedia, the web and novel interface applications.
Learning
Outcomes:
A student who successfully completes this paper will be able to:
a. Define
and describe the basic
principles of human information processing (including sensation, perception
cognition and interaction) (HCI Lecture Series, Tests, Exam)
b. Be
able to illustrate them with examples from a Web environment (Assignment 1)
c.
Apply the principles of HCI to evaluate a web site or IT design (Assignment 1,
Assignment 2)
d. Make
design recommendations based on HCI for a web site or IT system (Assignment 2)
This course is not only about
factual information, but also aims to help students form healthy social
attitudes and skills, to be a productive member of society. Hence the following
objectives are also pursued:
a. To
be helpful to other people (students should help each other).
b. To
fulfill obligations to the group (students will work in groups on some
assignments).
c. To be
effectual and professional (students are expected to plan and prepare their
work on time).
d. To
be honest and fair (students will not cheat or plagiarize the work of others).
e. To
be open-minded and creative (students are encouraged to explore new things, and
staff do not consider they know all the answers).
Prerequisite(s): 157.2xx or 158.2xx or 159.2xx
Corequisite(s): none
Restrictions: 159.353, 157.356, 157.359, 159.318
Assessment:
Course assessment (subject to modification) is broken down as follows:
|
Assessment |
Allocation |
Graded Out Of |
|
Assignment 1. Illustrate HCI Principles |
18% |
10 |
|
Assignment 2. HCI Evaluation |
20% |
100 |
|
Ten Minute Tests Lessons 1-8 |
32% |
100 |
|
Final Exam Lessons 1-8 |
30% |
100 |
|
TOTAL |
100% |
|
Written material:
a. Loose material
is not acceptable. Do not submit assignments with expensive bindings, as you
may have to come to get them back. Your work is not judged by its cover. A single
staple in the top left corner is satisfactory for most printed work. Your name
must be on all work submitted.
b. ALL WRITTEN
WORK MUST BE SPELL CHECKED. Bad spelling indicates carelessness or ignorance,
and spell checking is easy to do. For any assignment, any spelling error found
that could have been detected by a spell checker will result in an automatic
deduction of 5% out of 100% from the final grade.
All assignments
submitted for this course originate in computer form. Students must retain
a copy on their own computer of all material submitted, as backup in case
something happens to their submitted work. By submitting any material to this
course for assessment, the student authorizes instructors to retain a copy of
that material for grading and teaching. Instructors may reference a part of
that material, or parts of it, given the student involved is anonymous, for the
purpose of instructing other students, and for their learning benefit.
Deadlines and Penalties: Assignments
must be done professionally and submitted on time. Being on time is
part of being professional. Plan to complete assignments with this in mind.
If you leave things until the last moment, you are predictably vulnerable to
the unexpected. All assignments due in class (see Timetable) are due at
the beginning of the stated class period. For assessments that involve specific events, like
project progress presentations and the final presentation, no “late” or “redo”
is possible, as part of the desired learning experience is that event. For the
final project, the time deadline for submission is very
tight, so each working day late will reduce the points graded out of by 10, and
projects submitted more than two days
late will not be accepted, except under exceptional circumstances. Other
assignments lose 10% for each working day late, and will not be accepted at all
after five days (over one working week late).
Requirements to Pass the Paper: All of the course assessments must be attempted. Also
note that failure to complete any of these requirements will lead to a DNC
unless covered by the Aegrotat Regulations.
E-learning Category: Web supported through the syllabus and other materials available at
Stream
Conditions for
Conditions for Impaired Performance: If you consider that
your performance in, or preparation for, an examination, or another compulsory
assessment element that occurs at a fixed time and place, has been seriously
impaired by illness, injury or a serious crisis, you may apply for an impaired
performance consideration. You must
apply on the form available from the Examinations Office, the Student Health
Service or the Student Counselling Service.
Student Time Budget: Information Systems Project is a
15-credit paper. That equates to 12.5 hours of work per week for a 15-week
semester, or the equivalent of over 4 weeks of full-time work (187 hours).
Textbook and Other Resources: Students will use the web links given in the course
presentations.
Recommended book: Gregory, R. L., 1998, The
Timetable
Thursday 3-6pm in room NW100
For each lesson you should:
1. Print off the lesson print version and bring to class to make notes on.
2. Attend the class and the tutorial, as both are important.
3. Download the Powerpoint Show and run it. Click on
the main links to understand the
ideas. If you like a link, you can add it to your favorites under
"HCI"
Note: In this class, as well as recommend HCI changes to a computer system, you
must also give valid HCI reasons in
support.
|
No |
Week |
Lecture |
Tutorial |
|
1. |
1 Mar |
HCIIntro
Introduction |
Course outline |
|
2. |
8 |
Brain vs Computer 2 ctd (parallel analysis, process driven,
chaotic) |
|
|
3. |
15 |
HCI2 Sensations
and Attention (print
version) |
Groups: Prepare assignment 1a Review Test Questions1 |
|
4. |
22 |
HCI3 Perception
(print version) |
Present assignment 1a |
|
5. |
29 |
HCI4 Recognizing
Things (print
version) |
Present assignment 1a (ctd) |
|
6. |
5 April |
HCI5 Space
& Movement (print version) |
Assignment 2
issued Review Test Questions4 |
|
|
|
BREAK |
|
|
7. |
26 |
HCI6 (22Mb with sounds) Sound, Language, Thought and Sense Integration (print version). |
Present assignment 1b |
|
8. |
3 May |
HCI7a Interactivity
(print version) |
Present assignment 1b (ctd) |
|
9. |
10 |
HCI7b
Interactivity (ctd) (print version) |
Groups: Prepare assignment 1c, work on Assignment 2 |
|
10. |
17 |
HCI8 Learning
(print version) |
Present assignment 1c |
|
11. |
24 |
HCI8 (ctd) |
Assignment 2 due |
|
12. |
31 |
Exam Review |
Review Test
Questions8 |
|
15. |
|
|
Final Exam (HCI1-8) 2 Hours. |
Plagiarism:
Grievance Procedures: A student who claims
that he/she has sustained academic disadvantage as a result of the actions of a
University staff member should use the University Grievance Procedures.
Students, whenever practicable, should in the first instance approach the
University staff member concerned. If the grievance is unresolved with the
staff member concerned, the student should then contact the
Additional links:
· The Encyclopedia of Human-Computer Interaction
· Jakob Nielsen's Website UseIt
· A collection Tessellations
· Escher's amazing optical illusions
· How to reference electronic stuff you copied