21 Syllabus

download 21 Syllabus

of 4

Transcript of 21 Syllabus

  • 8/2/2019 21 Syllabus

    1/4

    CS260 Research Topics in Human-Computer Interaction

    Syllabus

    Jennifer Mankoff(510) 643 4205

    [email protected]

    January 21, 2003

    1 Course Description

    What is Research in Human Computer Interaction? This question will be the focal point of our studies overthe course of the coming semester. CS 260, or Research Topics in Human-Computer Interaction, will focuson a mixture of research methods and research topics in Human Computer Interaction (HCI) this semester.This is a project-based course, with a heavy reading component.

    For the purposes of this class, we will break HCI up into three domains: Tools and Techniques, Evaluation,and Design. Approximately a third of the semester will be spent on each area. You will learn about researchmethods in each of them, and pick two areas in which to do your projects. You will be expected to keep adiary of research ideas and select one of them to explore in depth over the course of the semester. You willlearn to read, skim, critique, summarize, and present research papers in the area of HCI. You will be askedto defend and present your work in writing and orally. You should leave with a thorough understanding ofhow to pick and judge research in Human Computer Interaction.

    2 Learning Goals

    The learning goals of this class are as follows:Research HCI Research in HCI

    read, skim, summarize, and evalu-ate a paper

    present work orally

    write about your work

    generate a research proposal

    find gaps in existing work

    conduct a literature survey

    constructively critique your peers

    know the strengths and weaknessesand history of

    HCI tools and interaction tech-niques

    HCI evaluation techniques

    HCI design methods/areas

    design and evaluate a system ortechnique or tool.

    raise the floor/lower the ceil-ing/change the path of leastresistance

    evolve a new evaluation technique

    select an area and design in/forthat area. Contribute to knowledgeabout design

    3 Requirements

    A required prerequisite for this class is CS160 or an equivalent class or experience with user interface design,development, and evaluation. Most of the students in the class will be graduate computer science students.If you feel partially but not completely prepared (i.e. you have experience designing and evaluating auser interface but perhaps have not covered all of the material in a standard HCI class formally), this is

    1

  • 8/2/2019 21 Syllabus

    2/4

    a page of suggested background readings put together for a similar class by Saul Greenberg at UCalgary.http://pages.cpsc.ucalgary.ca/~saul/681/background-readings.html Look at it, and then contactthe instructor.

    If you are a graduate student in HCI, buy some of these books you should own them and know them(especially The Design of Everyday Things, Readings in HCI: Towards... and at least one of the standardtextbooks). Additionally, the entire Lewis & Rieman book is available online for a shareware fee of $5.

    You will be expected to actively participate in lectures, and complete readings ahead of time. I willpromptly return graded homework to you, and will be available to provide feedback and help with problems.

    This class will require approximately the following time commitment: 8.5 hours each week including 3hours a week of class time. Approximately 12 hours of additional individual assignments spread throughoutthe semester. Additionally individual assignments may be added as the semester goes on.

    Weekly activities

    3 or more hours Research Project3 hours Class time (1.5 hours discussion, 1.5 hours lecture, review, excersizes and so on)2 hours Reading papers (2-3 per week, pluss summarization)30 minutes DiarySemesterly activities4 hours Skim an entire conference proceedings and write first paper critique5 hours Literature survey for project 1

    4 hours Research proposal for project 21 hours Prepare to lead lecture

    You should familiarize yourself with the class website (http://http://www.cs.berkeley.edu/projects/io/courses/cs260/spring2003/) and Swiki (http://kettle.cs.berkeley.edu/cs260-spring-03). Toaccess the Swiki, enter cs260 as a user name and student as a password. Most of your assignments willbe turned in here, and you should make a page for yourself as demonstrated in class.

    4 Contacting Me

    I will hold regular office hours, Thursday from 11am-12pm. I prefer phone to email. If you send me anemail, it should only contain yes or no questions. Please do not send me any attachments. Instead, send mea URL or plain text.

    Students with disabilities should contact me to discuss any accommodations that are necessaryI will keep you informed about important announcements by posting them on the Swiki announcementspage (See http://kettle.cs.berkeley.edu/cs260-spring-03). You should add yourself to the list ofpeople who should be notified when that page changes by editing the page and putting you email address inthe box labelled Send e-mail alerts to these addresses upon next save:.

    5 Assessment and Expectations

    CS260 includes both group and individual assignments. Much of the grading in this class is qualitative,including assessments of the end user experience of the system and the quality of your designs, evaluations,and prototypes.

    You will be expected to read papers regularly, and to turn in questions about the readings on the day

    before the class in which they will be discussed.

    You will be expected to keep a diary of research ideas, making entries at a minimum on a weekly basis.

    You will be asked to select two research ideas to work on alone, or in a small group, as your majorefforts during the semester. In the first project, you will focus on execution of a research plan. In thesecond, you will focus on development of a research plan. You will be asked to defend these ideas,write about them, implement them, and present them at various times during the semester.

    2

    http://kettle.cs.berkeley.edu/cs260-spring-03http://kettle.cs.berkeley.edu/cs260-spring-03http://http//www.cs.berkeley.edu/projects/io/courses/cs260/spring2003/http://http//www.cs.berkeley.edu/projects/io/courses/cs260/spring2003/http://pages.cpsc.ucalgary.ca/~saul/681/background-readings.html
  • 8/2/2019 21 Syllabus

    3/4

    You will be expected to lead one discussion in class.

    There will be one examination.

    Assignments will be turned in on the Swiki (http://kettle.cs.berkeley.edu/cs260-spring-03).

    Group assignments may not be turned in late. Individual assignments will lose one grade point per

    day they are late.

    Working in groups is a responsibility and a burden, due to the need to work out group dynamics. Youwill be asked to self-assess multiple times during the semester. Please be critical, as it is crucial tocatch problems early.

    Cheating and plagiarism will not be tolerated.

    Grading will not be on a curve. Your grade will be a combination of:

    final (15%)

    individual assignments (20%)

    project 1 (30%)

    project 2 (20%)

    in class participation (5%)

    diary (5%)

    preparedness (questions, etc) (5%)

    This course has no textbook, but you will be expected to make use of the Berkeley library to accesspapers from the ACM digital library and other online resources.

    Should you conduct user evaluations, you may wish to offer your users incentives to participate in yourevaluations, such as food or a gift certificate. This expense is your choice and your responsibility.

    6 Additional Information

    We expect to include at most 25 students in this class. Although we are open to various backgrounds, thevast majority of students will be Computer Science graduate students who are knowledgable about HCI.Students who do not have this backround will have to speak with the instructor to determine whether theywill be able to succeed in the class.

    3

    http://kettle.cs.berkeley.edu/cs260-spring-03
  • 8/2/2019 21 Syllabus

    4/4

    7 Calendar

    This calendar is tentative and subject to change.Week Topic Goals

    Wk 1 (J21/23) Introduction to class/Research in HCITools and Techniques

    Wk 2 (J28/30) UI organization; Interaction Techniques Select Project 1Wk 3 (F4/6) Interface Attachements, Fluid Documents, Merca-tor and other toolkit hacks

    Initial Lit Review

    Wk 4 (F11/13) Tangible Computing; Interacting with PaperWk 5 (F18/20) Change Blindness; Peripheral DisplaysWk 6 (F25/27) Recognition; Ambiguity

    EvaluationWk 7 (M4/6) Research Methods; GOMSWk 8 (M11/13) Fitts Law; EthnographyWk 9 (M18/20) Heuristic Evaluation; Writeup of Project 1

    Spring BreakDesign

    Wk 10 (A1/3) Design Initial Literature Survey for ProWk 11 (A8/10) ***CHI*** Initial Proposoal & CritiqueWk 12 (A15/17) Research Methods; Visual Design Revised Proposal & CritiqueWk 13 (A22/24) Sound Design; Sketching and Prototyping Revised Lit SurveyWk 14 (A29/M1) Direct Manip vs Inter Agents; Two Handed InteractionWk 15 (M6/8) Other TopicsWk 16 (M13) Wrapup Writeup of Project 2M20 8-11am Final Exam

    4