|
|
The textbook for the course is Interaction Design: Beyond Human-Computer Interaction by Yvonne Rogers, Jenny Preece, and Helen Sharp. It should be available in the bookstore. Be sure you get the second edition. There is
a reading assignment for each week.
LECTURE: Course Overview (Week 0: Thursday 9/27)
The first lecture will provide an overview of the course. Grading will be based on two midterms, a final exam, and a personal blog you maintain to document your weekly course-related activities.
HCI PERSON OF WEEK 0: Yvonne Rogers
ASSIGMENT WEEK 0:
Create a personal blog. I recommend using www.blogger.com. Send your blog url to 120@hci.ucsd.edu by Sunday evening (9/30). You should make at least one blog entry by Sunday evening each week. Feel feel free to make multiple entires each week. The blog will serve as a portfolio to document your thinking about the topics we cover and any course-related activities undertaken each week. It will also be a repository for copies of your written assignments. Be sure to maintain a personal copy of each blog posting and assignment. |
LECTURES: Complete Overview (Week 1: Tuesday 10/2 and Thursday 10/4)
READINGS WEEK 1: Chapters 1 and 2 (1-92)
Chapter 1: What is Interaction?
The main aims of this chapter are to:
- Explain the difference between good and poor interaction design.
- Describe what interaction design is and how it relates to human-computer interaction and other fields.
- Explain what is meant by the user experience and usability.
- Describe what is involved in the process of interaction design.
- Outline the different forms of guidance used in interaction design.
- Enable you to evaluate an interactive product and explain what is good and bad about it in terms of the goals and principles of interaction design.
Chapter 2 : Understanding and Conceptualizing Interaction
The main aims of this chapter are to:
- Explain what is meant by the problem space.
- Explain how to conceptualize interaction.
- Describe what a conceptual model is and explain the different kinds.
- Discuss the pros and cons of using interface metaphors as conceptual models.
- Debate the pros and cons of using realism versus abstraction at the interface.
- Outline the relationship between conceptual design and physical design
HCI PERSON OF WEEK 1: Randy Pausch
ASSIGMENT WEEK 1:
You should make your weekly blog entry by the end of Sunday evening (10/7). Feel free to make multiple entries each week. Your nomination to the Interface Hall of Fame or Hall of Shame will be due next week. You should start considering possibilities. |
LECTURES: Early History of HCI (Week 2: Tuesday 10/9 and Thursday 10/11)
READINGS WEEK 2: Chapters 3 and 4 (93-179)
Chapter 3: Understanding Users?
The main aims of this chapter are to:
- Explain what cognition is and why it is important for interaction design.
- Describe the main ways cognition has been applied to interaction design.
- Provide a number of examples in which cognitive research has led to the design of more effective interactive products.
- Explain what mental models are.
- Give examples of conceptual frameworks that are useful for interaction design.
- Enable you to try to elicit a mental model and be able to understand what it means
Chapter 4: Designing for Collaboration and Communication
The main aims of this chapter are to:
- Explain what is meant by communication and collaboration.
- Describe the main kinds of social mechanisms that are used by people to communicate and collaborate.
- Outline the range of collaborative systems that have been developed to support this kind of social behavior.
- Consider how field studies and socially based theories can inform the design of collaborative systems.
HCI PERSONS OF WEEK 2: Vannevar Bush, Ivan Sutherland, and Doug Engelbart
ASSIGMENT WEEK 2:
In addition to your regular blog post this week, you should make a separate post by end of the day on 10/14 of your nomination for the Interface Hall of Fame or Hall of Shame.
Choose an interface that you find particularly worthy of praise or blame in terms of its usability. Example usability factors you might want to consider include: fit to users' tasks, feedback, learnability, visibility of system status, match between system and the real world, user control and freedom, consistency with other interfaces and standards, error prevention, exploting recognition over recall, flexibility and efficiency of use, aesthetic design, helping users recognize, diagnose, and recover from errors, help and documentation, or other factors.
The interface can be for a PC application, a web-based application, or an interactive device. Identify aspects of the chosen interface that exemplify why the interface should be inducted into the Hall of Fame or the Hall of Shame.
In a short paper (aproximately 3 pages) describe the interface and explain why you are nominating it. While the paper should give an overview of the interface (images and figures are useful), who the users are, and what tasks the the interface is designed to support, the focus should be to characterize as clearly as you can the specific reasons the interface is particularly effective or ineffective and thus deserving of entry into the Hall of Fame or Hall of Shame. The goal of the assignment is to encourage you to think critically about a specific interface.
|
LECTURES: Direct
Manipulation Interfaces (Week 3: Tuesday 10/16 and Thursday 10/18)
READINGS WEEK 3: Chapters 5 and 6 (180-288)
Chapter 5: Affective Aspects
The main aims of this chapter are to:
- Explain what expressive interfaces are and the affects they can have on people.
- Outline the nature of user frustration and how to reduce it.
- Debate the pros and cons of applying anthropomorphism in interaction design.
- Describe the affective aspects used in interface agents and interactive physical toys.
- Present models and frameworks of affect that can be applied to interaction design.
- Enable you to critique the persuasive impact of an online agent on customers.
Chapter 6: Interfaces and Interactions
The main aims of this chapter are to:
- To introduce the notion of a paradigm and set the scene for how the various interfaces have developed in interaction design.
- To overview the many different kinds of interfaces.
- To highlight the main design and research issues for each of the different interfaces.
- To consider which interface is best for a given application or activity
HCI PERSON OF WEEK 3: Jun Rekimoto ASSIGMENT WEEK 3:
You should make your weekly blog entry by the end of the day (10/21). |
Week 4: DUE TO FIRE AND UCSD CLOSURE:
Exam is postponed until Thursday 11/1.
Review in class on Tuesday 10/30.
|
Week 5: Tuesday 10/30 Review and Thursday 11/1 Exam
The exam will cover chapters 1-6 and week 1 through 3 lectures. It will include short-answer, true-false, and multiple choice questions.
|
LECTURES Project II Related Topics (Week 6 : Tuesday 11/6 and Thursday 11/8)
READINGS WEEK 6: Chapter 7 (289-352)
Chapter 7: Data Gathering
The main aims of this chapter are to:
- Discuss how to plan and run a successful data gathering program.
- Enable you to plan and run an interview.
- Enable you to design a simple questionnaire.
- Enable you to plan and execute an observation.
HCI PERSON OF WEEK 6:
ASSIGMENT WEEK 6:
In addition to your normal weekly blog entry (due 11/11) you should continue making progress on the contextual interview assignment that is due week 8. At this point you should have formed a team of 3-4 students and decided on the focus of your project. Here is a brief description of the assignment. More details will be given in class.
The
essence of contextual design is (1) to go where the user works,
(2) observe the user as he or she works, and (3) talk to the user
about the work. The process of contextual design starts with interviews
with users in their workplace while they work. For this project you will form teams of 3-4 students and interview people (4-6 people) while they
are using an interface (it doesn't necessarily need to be a computer-based
interface). Your team should
jointly write a short paper (4-5 pages) describing what you learned
about the interface from your interviews. You should mention both
the positive and negative aspects of the interface as well as ideas you have for design improvements.
The paper (due 11/20) should include the following:
- Describe the interface and context of use
- Briefly describe how you conducted the interview
- Report the significant data from your interview (both positive and negative aspects of the interface) and the conclusions the data supports. Be especially careful to use your data to ground your conclusions
- Describe any design changes motivated by your data
HCI PERSON OF WEEK 6: Patrick Baudisch |
LECTURES (Week
7: Tuesday 11/13 and Thursday (11/15)
READINGS WEEK 7: Chapters 8 and 9 (353-470)
Chapter 8: Data Analysis, Interpretation, and Presentation
The main aims of this chapter are to:
- Discuss the difference between qualitative and quantitative data and analysis.
- Enable you to be able to analyze data gathered from questionnaires.
- Enable you to be able to analyze data gathered from interviews.
- Enable you to be able to analyze data gathered from observation studies.
- Make you aware of the kind of software packages that are available to help your analysis.
- Identify some of the common pitfalls in data analysis, interpretation, and presentation.
- Enable you to be able to interpret and present your findings in a meaningful and appropriate manner.
Chapter 9: The Process of Interaction Design
The main aims of this chapter are to:
- Explain some advantages of involving users in development.
- Consider what ‘doing’ interaction design involves.
- Explain some advantages of involving users in development.
- Explain the main principles of a user-centered approach.
- Ask and provide answers for some important questions about the interactiondesign process.
- Introduce the idea of a lifecycle model to represent a set of activities and how they are related.
- Describe some lifecycle models from software engineering and HCI and discuss how they relate to the process of interaction design.
- Present a lifecycle model of interaction design.
HCI PERSON OF WEEK 7: Ken Hinckley
ASSIGMENT WEEK 7:
As part of your weekly blog entry (due 11/18) you should document your project and highlight your specific contributions. |
WEEK 8: Lecture 11/20
Assignment II Due in or before class Tuesday 11/20
No ClassThursday 11/22 Thanksgiving Holiday)
READINGS WEEK 8: Chapers 10 and 11 (472-582)
Chapter 10: Identifying Needs and Establishing Requirements
The main aims of this chapter are to:
- Describe different kinds of requirements.
- Enable you to identify examples of different kinds of requirements from a simple description.
- Explain how different data gathering techniques (those introduced in Chapter 7 and others) may be used during the requirements activity.
- Enable you to develop a ‘scenario,’ a ‘use case,’ and an ‘essential use case’ from a simple description.
- Enable you to perform hierarchical task analysis on a simple description.
Chapter 11: Data Analysis,
The main aims of this chapter are to:
- Describe prototyping and different types of prototyping activities.
- Enable you to produce simple prototypes from the models developed during the requirements activity.
- Enable you to produce a conceptual model for a product and justify your choices.
- Explain the use of scenarios and prototypes in design.
- Discuss the range of tool support available for interaction design.
HCI PERSON OF WEEK8: Mark Weiser and John Seely Brown
ASSIGMENT WEEK 8:
No blog entry this week. Catch up on reading and enjoy the holiday.+
Final Exam Options for Students with A Grades on First Exam
If you received A grades on the first exam, you have the option of completing an optional project rather than taking the first section of the final. The goal of project is to encourage you to think carefully about interaction design. The project can be done individually or in a group. The scale of the project should reflect the size of the group. For group projects each person will provide a separate description of the specific contributions of each group member (including their own). There are two alternatives.
Option I: You will explore an interaction technique. The objectives are to observe interaction in detail, analyze the interaction to understand the situation and factors that contribute to problems, and propose an interaction technique that might mitigate or eliminate a problem. Focus on one specific interaction technique rather than the whole interface. You should document your exploration and proposed improvement in a 4-5 page paper. The paper is due at the time of the final.
Option II: Use the Processing programming language to create, modify, or explore a interaction technique. Processing is a language for exploring the emerging conceptual space enabled by electronic media. You
can download the Processing software by going to this website. In addition to turning in your processing code, you should document the design and development of your interaction technique in a 4-5 page paper. The paper is due at the time of the final.
|
LECTURES (Week 9: Tuesday 11/27
and Thursday 11/29)
READINGS WEEK 9: Capters 12 and 13 (584-643)
Chapter 12: Introducing Evaluation
The main aims of this chapter are to:
- Illustrate how observation, interviews, and questionnaires that you encountered in Chapters 7 and 8 are used in evaluation.
- Explain the key concepts and terms used in evaluation.
- Introduce three main evaluation approaches and key evaluation methods within the context of real evaluation studies.
- Examine how the approaches and methods are used for different purposes at different stages of the design process.
- Discuss some of the practical challenges that evaluators have to consider when doing evaluation.
Chapter 13: An Evaluation Framework
The main aims of this chapter are to:
- Discuss the conceptual, practical, and ethical issues involved in evaluation.
- Introduce and explain the DECIDE framework.
HCI PERSON OF WEEK 9: Jan Borchers
ASSIGMENT WEEK 9:
Your blog entry this week is due 12/2. |
LECTURES (Week 10: Tuesday 12/4
and Thursday 12/6 )
READINGS WEEK 10: Capters 14 and 15 (644-722)
Chapter 14: Usability Testing and Field Studies
The main aims of this chapter are to:
- Explain how to do usability testing through examples.
- Outline the basics of experimental design.
- Discuss the methods used in usability testing.
- Discuss the role of field studies in evaluation.
Chapter 15: Analytical Evaluation
The main aims of this chapter are to:
- Describe the important concepts associated with inspection methods.
- Show how heuristic evaluation can be adapted to evaluate different types of interactive products.
- Explain what is involved in doing heuristic evaluation and various kinds of walkthrough.
- Describe how to perform two types of predictive technique, GOMS and Fitts’ Law, and when to use them.
- Discuss the advantages and disadvantages of using analytical evaluation.
HCI PERSON OF WEEK 10: Jimmy Wales
ASSIGMENT WEEK 10:
Your blog entry this week is due 12/9.
|
FINAL EXAMINATION: (Thursday 12/13 8-11AM )
The final exam will contain two sections: one that cover lectures and readings from weeks 1 through 3, and another that covers lectures and readings from weeks 6 trhough 10. Students with an A grade on the first exam who choose to do an optional project will complete only the second section of the final. The optional project is due at the time of the final (hand in a paper version) and it will count for 37.5% of the final examination grade. |
|
