CMSC 434 - Spring 2009
Prof. Bederson

Introduction to Human-Computer Interaction


Home Contact Syllabus Schedule Deliverables Links

Class Text:

Universal Principles of Design, Lidwell, Holden and Butler [Rockport], 1998.

Recommended Texts:

Designing the User Interface: Strategies for Effective Human-Computer Interaction, 4th Edition, Shneiderman and Plaisant  [Addison-Wesley], 1998.
 

 

In December 1995, American Airlines Flight 965 departed from Miami on a regularly scheduled trip to Cali, Columbia. On the landing approach, the pilot of the 757 needed to select the next radio navigation fix, named "ROZO." He entered an "R" into his navigation computer. The computer returned a list of nearby navigation fixes starting with "R" and the pilot selected the first of these, whose latitude and longitude appeared to be correct. Unfortunately, instead of "ROZO," the pilot selected "ROMEO," 132 miles to the northeast. The jet was southbound, descending into a valley that runs north-south, and any lateral deviation was dangerous. Following indications on the flight computer, the pilots began an easterly turn and slammed into a granite peak at 10,000 feet. One hundred and fifty two passengers and all eight crewmembers aboard perished. Four passengers survived with serious injuries. The National Transportation Safety Board investigated, and-- as usual-- declared the problem human error. The navigational aid the pilots were following was valid but not for the landing procedure at Cali. In the literal definition of the phrase, this was indeed human error, because the pilot selected the wrong fix. However, in the larger picture, it wasn't the pilot's fault at all.

-- The Inmates are Running the Asylum (Cooper)

 

Technology is a growing component of all of our lives, and computers are a growing component of many forms of technology. Yet, until quite recently, most computer applications were designed without considering the people who would use them. Rather, functionality and computational efficiency were the primary design factors. Often, computers are ineffective from a practical standpoint despite the fact that they do exactly what the designers intended. The problem is that a tool as complex as a computer needs to take into account more than just functionality, especially as more people without technical experience start to use them.

 

ACM defines CHI as "… a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them." In this course, we will survey the various components and techniques of Human-Computer Interaction. Starting with a look at some basic capabilities of people, we will look at the design of everyday objects to motivate the design of computer interfaces. We will explore various techniques for bringing users into the design-loop as we learn about basic user interface design tools. Finally, we will study evaluation techniques to help understand if our designs are effective. We will use these approaches in our class projects as we iteratively design, evaluate, and eventually build a user interface.

The course will consist of these topics:

  1. Overview

  2. The Past and the Future

  3. Principles for Design

  4. Understanding users and their tasks

  5. Designing with the user

  6. Basic human factors

  7. Designing visual interfaces

  8. Interface technology

  9. Implementing GUIs

  10. Evaluation and experimental design

Work load

There will be individual homework assignments, and group projects throughout the course. In addition, there will be substantial reading assignments and occasional other exercises. There will be assignment write-ups for each step of the project, and a final in-class presentation. No assignments strictly require programming, although some programming can help you do a more interesting and thorough job. A significant part of the course will involve your participation. Classes will frequently involve discussion and exercises in addition to lectures. Turned in material might be used (anonymously) as a starting point for discussion.

Group Project

The project will focus on solving a real world problem, and it will be divided into 4 steps, each 3 weeks long. The steps include: defining users goals, building a low fidelity a prototype, implementing a functional prototype and evaluating the prototype.  The class will be divided into groups of 3-4 people. The groups will be formed near the beginning of the course, and will be kept throughout the semester. Aside from exceptional circumstances, the members of the group can not be switched. However, if a student is not actively participating in their group, they can be removed from their group. Before this can happen, the group must make their concerns clear to the student in question several times. Then, I must be notified about the difficulty. If after these repeated efforts, the student still is not actively participating in a group, they will be removed from the group and will have to work on an assignment on their own.

Machines

All assignments can be done using the technology of your choice. Prototypes can be built with MacroMedia Flash, Expression Blend, Java, or any other technology.  The only requirement is that they run on a PC so the TA and I can evaluate them on our computers.  We will form groups taking into account the preferred technology that you want to use.

Writing

This course involves a lot of writing. You will be graded on your writing quality as well as your writing content. Good writing conveys ideas more clearly than poor writing, and the process of writing down your thoughts often helps to clarify them. Thus it is to your advantage to make the effort to organize your thoughts and write well.

Late Assignments and Excused Absences policy

All assignments are due at the beginning of the class on the day that they are due. The paper part (if any) must be turned in in class, and the electronic part (if any) must be submitted by the time of the beginning of class. Late assignments will be strictly penalized. Exceptional circumstances will be considered only if discussed with me in advance. Students claiming an excused absence must apply in writing and furnish documentary support (such as from a health care professional who treated the student) for any assertion that the absence qualifies as an excused absence. The support should explicitly indicate the dates or times the student was incapacitated due to illness. Self-documentation of illness is not itself sufficient support to excuse the absence. Instructors are not under obligation to offer a substitute assignment or to give a student a make-up assessment unless the failure to perform was due to an excused absence. An excused absence for an individual typically does not translate into an extension for team deliverables on a project. All late assignments will have points deducted as follows:

-20% - Up to 24 hours late
-50% - Up to 48 hours late
-100% - More than 48 hours late

Grading

Your final grade will be computed using the following contributions:

10% Participation
20% Homework
10% Project step 1
10% Project step 2
10% Project step 3
10% Project step 4
10% Midterm Exam
20% Final Exam

In addition, you must pass both exam components and assignment components to pass the course.

If you wish to contest a grade, please do so by submitting a grade change request through the online grading system before the grade change deadline (which is published for each assignment on the grading system).Your work will then be graded again and a new grade issued. Please note that the new grade might be lower than the original grade.

Disability Support Services Requests

Any student eligible for and requesting reasonable academic accommodations due to a disability is requested to provide a letter of accommodation from the Office of Disability Support Services (DSS) within the first two weeks of the semester.

Academic Honesty

The University of Maryland, College Park has a nationally recognized Code of Academic Integrity, administered by the Student Honor Council. This Code sets standards for academic integrity at Maryland for all undergraduate and graduate students. As a student you are responsible for upholding these standards for this course. It is very important for you to be aware of the consequences of cheating, fabrication, facilitation, and plagiarism. For more information on the Code of Academic Integrity or the Student Honor Council, please visit http://www.studenthonorcouncil.umd.edu/whatis.html.

 

The four  project steps are group assignments, and each member of the group is expected to accurately represent their contribution. Homework and exam are individual works and a student may not look at another student's homework or exam, or share notes (unless exceptions are stated in advance), during homework preparation or the exam period. You may discuss homework in a general way, but you may not consult any one else's written work, program drafts, computer files, etc. Similarly, groups may discuss their project in general ways but may not consult any one else's written work, program drafts, computer files, etc. Any marked similarity in form or notation between submissions with different authors (or groups in case of a project) will be regarded as evidence of academic dishonesty -- so protect your work.

 

You are free to use reference material to help you with assignments, but you must cite any reference you use and clearly mark any quotation or close paraphrase that you include (this includes material from the web). Such citations will not lower your grade, although extensive quotation might.

 

Any student violating any of these or general University Academic Honesty Rules will be reported to judicial programs for a hearing.

Network usage in class

Our classroom has Internet connectivity. Students are expected to focus on class during class time.  Students that are observed participating in non-classroom activities will be asked to leave.