Sunteți pe pagina 1din 6

CS 4800/6800

Syllabus

Human-Computer Interaction SP11 Course Policies


V 8.18.09

Instructor
Chris Doc Plaue Office: 217 Boyd Office Hours: T 11:00-12:00; W 15:30-16:30 Email: plaue@uga.edu

Teaching Assistant
To Be Announced

Meeting Times Meeting Place Required Textbooks (2) Optional Textbook Evaluation

Tuesdays/Thursdays from 9:30 - 10:45 to 13:45, Wednesdays 10:10 to 11:00, Spring 2011 Semester Tuesdays/Thursdays: Poultry Sciences 136 Wednesdays: 306 Interaction Design: Beyond Human-Computer Interaction Emotional Design: Why We Love (or Hate) 2nd Edition Everyday Things Sharp, Rogers, Preece. ISBN 978-0470018668 Norman, ISBN 978-0465051366 Design of Everyday Things Norman, ISBN 978-0465067107

Methods

Method Qty Points Individual Homework & Participation 6 300 24.4% In-Class Exercises TBD 100 8.1% All assignments aside Syllabus Quiz 1 30 2.4% from the group project are Milestone 1 1 100 to be competed Milestone 2 1 100 individually unless Milestone 3 1 100 40.7% otherwise (and explicitly) Milestone 4 1 100 noted Poster Session 1 50 Presentation 1 50 Examinations 2 300 24.4% Undergraduate Total 1230 Graduate Total 1430* * Graduate students enrolled in the CSCI 6800 section of the course have additional responsibilities including an additional individual homework exercise (worth 100 points) and a research paper presentation (worth 100 points). All academic work must meet the standards contained in, A Culture of Honesty, and the Student Honor Code. All academic work must meet the standards described in A Culture of Honesty found at: www.uga.edu/honesty. Lack of knowledge of the academic honesty policy is not a reasonable explanation for a violation. Questions related to course assignments and the academic honesty policy should be directed to the instructor. Project

Examinations

Students may request to take an exam prior to the examination date. This request must be made at least one week prior to the scheduled examination date. Students who do not make such a request and are not in attendance on the examination date have an opportunity to take the exam at a different time only under exceptional circumstances, such as family or medical emergencies. We will have several (perhaps many) in-class exercises to apply skills and further explore course material. In-class exercises will be turned in to the TA and will be graded as check, plus, or minus. Please see the homework section of this syllabus to learn about the grading system. At the end of the semester, we will drop your two lowest in-class exercise scores. Each homework assignment will include formatting instructions, delivery instructions, and deadline. In order to be eligible for credit, submissions must conform to each of these requirements. The late policy for the assignment will be explicitly listed on each assignment.

In-Class Exercises

Homework

CS 4800/6800

Syllabus

Homework will be graded on a list of criteria (specified on the assignment). For each criterion, you will receive either a check plus, check, or check minus. Most criterions will receive a check. A plus means, "you impressed me." A minus means the assignment is incomplete, incorrect, or sloppy in some fashion with respect to that criterion. Pluses and minuses are combined to give your grade for the assignment. For most assignments, you start out half way between a B+ and A-. One plus makes it an A-; one minus makes it a B+. These are general guidelines, grading on specific assignments may differ. Attendance is mandatory for group presentation and poster presentation days. Missing class during these days will result in a penalty of 25 points from individual scores per absence. This class involves a number of in-class exercises, discussions, and time for group work, so the instructor expects regular attendance from all students. There is no roll call or explicit account for attendance on lecture days. However, there will be frequent in-class exercises, some of which will be turned in for grading, as outlined in In-Class Exercises. Students do not need to notify the instructor in advance of a planned absence, except as explained above for examinations. In the case of absence, students must first consult with a classmate about missed material prior to seeking assistance from the instructor. Students may request a re-grade of any graded material except in-class exercises. To make a request, a student should submit a written justification for the request on the material itself or via email. Students should be aware (perhaps beware) that such requests could result in a lower grade being assigned. Any request must be made by the end of the class immediately after the instructor returns the graded material, regardless of whether the student is in attendance. For example, if the instructor returns the material on a Wednesday, then the student has until the end of class Friday to request a re-grade. It is in your best interest to contact the instructor before initiating a withdrawal from this course in order to understand your standing in the class. You may withdraw from CSCI-4800/6800 within the first two weeks of classes and receive a grade of WP. After this point, a grade of WP or WF will be assigned depending on your current standing in the course (i.e. if your course progress is failing numerically, you will be assigned a grade of WF). Students who require accommodations based on a disability of any kind should follow the procedures outlined by the UGA Disability Resource Center. I am happy to help anyone with a disability by providing any reasonable accommodations, but I cannot provide them until I receive appropriate documentation. The instructor will communicate through announcements via email and eLC. You are required to check eLC and your uga.edu email at least once a day. When emailing the instructor or TA, please include a [cs4800] or [cs6800] tag in the subject line. The instructor (sort of) grew up in the digital age and is not a total Luddite. If your electronic device sounds in class, its no big deal, just silence it quickly. You will not get ejected from class (especially since chances are good that my phone may vibrate loudly and Id rather not kick myself out of class). You will notice, though, that I will never take a call or text message during class and I ask you to do the same. Laptops offer genuine advantages to students who wish to use them to take notes, but they also serve as distractions (Facebook, IM, etc). If you opt to use a laptop during class, please exercise good judgment since what you use your laptop for may distract not only yourself, but students seated around you. The instructor will excuse any students found to be using laptops in such a way that it distracts from the learning experience of other students (read: absolutely do NOT play games during class). The instructors wish to view this syllabus as a contract of what they expect from the class, and what the class should expect of them After the first week of the class, due dates and exam dates will be solidified and will not be changed unless unusual circumstances arise. Lecture topics, however, are subject to change to accommodate guest speakers, catch up on material, etc.. UGAs official policy is, The course syllabus is a general plan for the course; deviations announced to the class by the instructor may be necessary.

Attendance

Re-grade Requests

Withdrawals

Accommodations

Communication

Mobile Devices

Laptop Usage

Changes

Welcome to Human-Computer Interaction!

CS 4800/6800

Syllabus

Content Schedule Fall 2009


Goals Broadly stated, there are four goals for this class: 1) Understand the principles of user-centered design and how to apply them to a software-based project 2) Understand the history of human-computer interaction and how its changed over time 3) Explore why good interface design is not necessarily common sense 4) Utilize skills and knowledge from other disciplines in developing a software-based project We will achieve these goals by completing various in-class exercises, a group project, and homework assignments. In addition, through required readings and lectures, students will acquire or improve a number of skills that can help them design more usable software. Class Schedule
Readings Key: ID = Interaction Design (Required Text) DOET = Design of Everyday Things (Optional Text) ED = Emotional Design (Optional Text; chapter(s) on e-reserve)

Note, the schedule of lectures is subject to change to accommodate guest speakers, catch up on materials, etc. Revisions will be posted on the course Website on eLC. Please check eLC daily for any revisions.

Topic
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 1/11/11 1/12/11 1/13/11 1/18/11 1/19/11 1/20/11 1/25/11 1/26/11 1/27/11 2/1/11 2/2/11 2/3/11 2/8/11 2/9/11 2/10/11 2/15/11 2/16/11 2/17/11 2/22/11 2/23/11 2/24/11 3/1/11 3/2/11 3/3/11 3/8/11 3/9/11 3/10/11 3/15/11 Introductions/Course Policies/History Student Introductions HCI History 1 Projects & Requirements Gathering To be announced Requirements Gathering / Task Analysis HCI History/ Stakeholder Analyses Stakeholder Analyses Exercise Human Abilities 1: Input Systems Abilities 2: Cognition & Attention Abilities 3: Perception & Memory Abilities 4: Motor Systems Gestalt ,Visual Design, Graphic Design Implementation 1 Design Alternatives Design of Everyday Things SR DOET / Errors & Documentation Futuristic Prototyping Review User Experience POSTER SESSION P2 Studio Review Prototyping TBA 2 Dialogs: Command & WIMP

Reading
ID 1.1-1.4 ID 1 ID 7, ID 9.1-9.3 ID 9.4, ID 10 ID 10, ID 3

Assignment
Out: HW-A Out: P-0 In: HW-A In: P-0, Out: P-1

Notes

Out: HW 1 Start ED

ID 15.4

In: HW 1

ID 9.1-9.3, skim rest DOET, ID 2.3, 2.4 DOET - ED EXAM I ED

In: P-1, Out: P-2 Out: HW 2

In: Understanding the Problem

In: HW2

In: P-2, Out P-3 Recall ID 2, ID 11 Out: HW 3 ID 6

Mid-Semester!

CS 4800/6800
29 30 3/16/11 3/17/11 3/22/11 3/23/11 3/24/11 3/29/11 3/30/11 3/31/11 4/5/11 4/6/11 4/7/11 4/12/11 4/13/11 4/14/11 4/19/11 4/20/11 4/21/11 4/26/11 4/27/11 4/28/11

Syllabus

31 32 33 34 35 36 37 38 39 40 41 42 43 44 45

Observation / Usability TBA 3 Cognitive Walkthrough Predictive/Discount Evaluation Mobile HCI-1 Mobile HCI-2 Implementation 3 Mobile HCI-3 Testing and Evaluation Plans TBA 4 Testing and Evaluation Plans Testing and Evaluation Plans Studio Review P3 Special Topics Special Topics Review Special Topics TBD Closing Plenary

ID 7 ID 15

In: HW 3 WithdrawalDeadline

ID 12 ID 13.1-13.4 ID 14

Out: HW 4

In-P3, Out P-4 In: HW 4

Exam II

In: P-4

5/10/11 Final Exam Slot (8:00 11:00) In: Video Candidates for Special Topics (but not limited to): Mobile HCI, Collaborate Mobile Learning, Qualitative Methods, Information Visualization, CSCW, Cognitive Abilities & Aging.

Acknowledgments: Thanks to Dr. Duke Hutchings (Elon University), Dr. Melody Moore Jackson (GSU-GT), and Robert Amar (formerly GT) for letting me borrow some content and ideas from their course syllabi. Also, thanks to Drs. Dan Hyde and Steve Guattery (Bucknell University) for the initial ideas on facilitating CS group projects. Some content from course slides are from the Human-Centered Computing Education Digital Library, under the Creative Commons License Scheme.

CS 4800/6800

Syllabus

Project
During this semester, you will undertake a group project (approximately 4 people per team) to: evaluate some computing-related task/problem develop interface design alternatives for the task/problem implement a prototype of your design evaluate your design

This is user-centered or interaction design! And the goal of this class is to provide practical and valuable experience with the tasks, research, and experimentation that interface designers do everyday. Themes for projects: The theme for this semesters projects is: Connecting to (*) You You should think of this domain as exploring how technological innovation can help an individual become the person they want to be. Thus, the * in the domain above can be a better, a wealthier, a healthier, etc. By design, this is a large and rich domain to explore and we will help you investigate ideas for different problems to explore in this solution. The critical aspect of selecting a problem is that it must matter to some real-life people. These people can me a small group of individuals, or a large one, or any group in-between, but they will serve as your clients whom you must communicate with and learn from. We will help you come up with possible project ideas or you can come up with your own. In the case of the latter, you must make sure you get it approved by the instructor. It is your responsibility to find and contact the clients for your projects. They will not come to you. Thus, you need to make sure that your problem domain has an obtainable population. Grading. After each milestone, each team member will complete a survey of the work of their teammates. This information will be used to adjust grades, as necessary. To be clear, lack of participation may result in an individual reduction of grade. Likewise, doing more than your fair share of work may result in a grade adjustment. Recall, the group project is over 40% of your final grade. Within the team, you must negotiate on how much and what each person will contribute. There are many factors that must be discussed at the beginning of the project to ensure that things go smoothly. Such factors include: Where do people live and what hours do they prefer to work. Some people commute from nearly an hour away! Where will the group meet? What skills do different individuals bring to the group and how can they be best utilized. o Remember, skills go beyond programming. Artistic design, interviewing individuals, writing, are all valuable skills. It is in your interest to work together and discuss issues. If problems arise with group dynamics, it is your duty to first attempt to work them out before approaching the instructor or TA. However, be warned that waiting

CS 4800/6800

Syllabus

too long to seek outside help resolving inter-group conflict will most likely adverse your project and deliverables, which is a large portion of your grade. Many group problems cannot simply be fixed at the last minute. Team Selection In my experience, self-selecting student groups tend to be unbalanced. Similarly, randomly generated groups often have similar issues. For this project, we will be using a hybrid system. One class period will be reserved to allow students to introduce themselves to the class, present any potential project ideas, list interests, and talk about their particular strengths. You will be allowed to specify one person you want to be on your project team and optionally, one person youd rather not. These votes will be kept strictly private. The instructor and TA will then match up teams of approximately four individuals and try to accommodate all requests, but these requests are not guaranteed.