Spring Quarter
Tuesdays 18:40-21:20 p.m., Capital Center 1305
March 31-June 9, 2009
Instrucations for course E-mail list
https://mailhost.cecs.pdx.edu/mailman/listinfo/cs560-list
Instructor
James A. Larson, Ph.D.
Larson Technical Services
16055 SW Walker Road, #402
Beaverton, OR 97006
Fax (503) 645-3598
E-mail: jim@larson-tech.com
Textbook
Ben Shneiderman & Catherine Plaisant, 2010, Designing the User Interface: Strategies for Effective Human-Computer Interaction, 5th Edition, Boston: Addison Wesley, ISBN: 0-321-53735-1
Course Description
Introduction to the basic theory of human-computer interaction. Principles of human cognition and interface design, interface evaluation techniques. Several prototyping tools will be presented. Projects are required.
Training, skill, and experience are necessary to design user interfaces that are truly easy to learn and use. This course presents the theory and principles behind great user interfaces and enables students to put theory into practice by (1) specifying criteria for evaluating user interfaces; (2) implementing a variety of user interfaces, including GUI (Graphical User Interface), VUI (Voice User Interface) , and MMUI (Multimodal User Interface); and (3) applying the evaluation criteria to the user interface. Students should be able to apply the knowledge they gain from this course to both design and evaluate user interfaces using technologies available today and tomorrow.
Course Prerequisite: Knowledge of HTML, so students can develop prototype Graphical User Interfaces (Students may use any HTML generation tool such as Front Page, Dreamweaver, etc.)
Course Requirements
Students will form teams to prototype and evaluate three user-user interfaces (GUI, VUI, and MMUI)
Teams
During the first class, teams of 2 to 3 students will be formed to complete the first project. After the first project is completed, the teams may be reorganized.
Course Grading
No late reports will be accepted. (If you are not able to attend class, make sure your team mate turns in reports. Alternatively, reports may be mailed, e-mailed, or faxed to instructor.)
| Date | In class activity | Readings relating to this week's in-class activity | Assignment due the following week |
|---|---|---|---|
March 31 |
Review syllabus |
Chapter 1: Introduction |
Develop scenarios for project 1 |
April 7 |
Use scenarios to develop conceptual model. |
Chapter 6: Menu Selection, Form Fill-in, and Dialog Boxes |
Create GUI prototype for project 1 |
|
Demonstrate GUI prototypes for project 1 |
Chapter 5: Direct Manipulation and Virtual Environments |
Create final GUI for project 1 |
April 21 |
Demonstrate final GUIs for project 1 |
Chapter 7: Command and Natural Languages |
Demonstrate an elementary VUI application using Prophecy and VoiceXML 2.0/2.1 |
April 28 |
Collaboration and Social Media Participation |
Chapter 9: Collaboration and Social Media Participation |
Create VUI prototype for project 2 |
May 5 |
Demonstrate VUI prototypes for project 2 |
Chapter 10: Quality of Service |
Create final VUI for project 2 |
May 12 |
Demonstrate final VUI for project 2 |
Opera Voice Page |
Demonstrate an elementary MMUI application using Opera |
| May 19 | Criteria for evalating MMUI User Documentation and Online Help |
Chapter 11: Balancing Functions and Fashion |
Create MMUI prototype for project 3 |
| May 26 | Demonstrate MMUI prototype for project 3 User Documentation and Online Help |
Chapter 12: User Documentation and Online Help |
Create final MMUI for project 3 |
| June 2 | Demonstrate final MMUI for project 3 Course Summary: Comparison of GUI, VUI, and MMUI |
|
|
| June 9 | Final exam |
Class cancellation: In the event of bad weather or other unforeseen circumstances, the instructor will telephone and/or e-mail students two hours before the beginning of class. On bad weather days, please check your e-mail before coming to the classroom.