home

=**CMSC 434 - Intro to HCI - University of Maryland - Fall 2011**=
 * Prof. Ben Bederson**

and by appointment || 2117D Hornbake South Wing || Wed 3:30-4:30pm || 1112 AVW ||
 * Class hours:** Mon & Wed, 2pm - 3:15pm **Room:** 2107 CSIC
 * Contact information**
 * ~ Name ||~ Email (@cs.umd.edu) ||~ Office Hours ||~ Office ||
 * [|Prof. Ben Bederson] || bederson || Sign up: [|Thu, 11-12:30pm]
 * Mike Gubbels || mgubbels || Mon 12:30-1:30pm,
 * Book:** Rogers, Preece & Sharp, [|Interaction Design: Beyond Human-Computer Interaction, 3rd Ed.], Wiley, (2011)
 * Topics:** Science base (theories, models, and studies) and user interface design and development. Graphical user interfaces for desktop, web, and mobile devices. Assess usability by quantitative methods. Conduct task analyses, usability tests, expert reviews, and continuing assessments of working products by interviews, surveys, and logging. Apply design processes and guidelines to develop professional quality user interfaces. Build low-fidelity paper mockups, and a high-fidelity prototype using contemporary tools.
 * Discussion:** [|Piazza] (don't use Wiki discussion)


 * Web resources:** [|hcibib.org], [|usability.gov], [|useit.com], [|ibm.com/design], [|hcc.cc.gatech.edu], [|UCD Book], [|UX StackExchange]
 * Prototyping Tools:** [|Balsamiq], [|App Sketcher]
 * Web Tools/Refs:**[| Eclipse], [|JQuery], [|Python], [|SQLite,]W3Schools: [|HTML], [|JavaScript], [|CSS], [|JSON], [|Dive Into Python](book)
 * Grades:** [|Available online]


 * Student Homework:** People, Term Project

(group) ||~ Homework (individual) ||~ HOF/S || 8/31 ||<  [|Intro] & Usability ||< [|Norman] - Qs ||<  ||<   ||< xx / xx || 9/7 ||<  [|Qualitative Evaluation] ||< ID: Ch. 1 (Intro) - Qs [|Accessiblity] ||<  ||< 9/5: Bring in remote control 9/5: Sign up for HOF/S ||< xx / xx || 9/14 ||< [|Accessibility] [|Design process] ||< ID: Ch. 2 (Interaction) - Qs [|Kelley] - Qs [|Segal] (short) [|Stross] (short) ||<  ||< 9/12: Wiki self intro ||< YM / MM IK / TT || 9/21 ||< User needs Jen G.: Web software I ||< ID: Ch. 7 (Data gathering) - Qs ||<  ||< WED 9 /21: Accessibility ||< MO / CC xx / xx || 9/28 ||< [|Web Software II] [|JS examples.zip] [|JQuery examples.zip] Perception & Design I ||< ID: Ch. 8 (Data analysis) - Qs [|Ware] - Qs ||< 9/26: Proposal ||< WED 9/28:Critique ||< GA / KV / AP || 10/5 ||< [|Perception & Design] II [|Guidelines.pdf] ||< ID: Ch. 10 (Requirements) - Qs ||< WED 10/5: User needs ||<  ||< ZB / LF DC / SP || 10/12 ||< [|Prototyping] ||< ID: Ch. 11 (Prototyping) - Qs [|Schonfeld] ||<  ||< MON 10/10:HTML & CSS ||< AM / JS AA / RM || 10/19 ||< [|Natural UIs] WED 10/19: Midterm in class [|Old midterm] ||< ID: Ch. 6 (Interfaces) - Qs ||< WED 10/19: Design ||<  ||< MP / MK || 10/26 ||< Low-level models I ||< ID: Ch. 3 (Cognitive) - Qs ||<  ||< WED 10/26: JavaScript ||< -- / -- PA / MM || 11/2 ||< [|Low-level models] II High-level models ||< ID: Ch. 12 (Evaluation I) - Qs [|Card] - Qs ||< WED 11/2: Prototype ||<  ||< MS / VK WY / FA || 11/9 ||< [|Revisiting User Studies] [|Web Studies] ||< ID: Ch. 14 (Evaluation II) - Qs ||<  ||< Fitts' Law ||< -- / -- SB / JG || 11/16 ||< Quantitative Evaluation  ||< ID: Ch. 15 (Evaluation III) - Qs [|Hinton] [|Google Instant] ||< WED 11/16: Usability test ||<  ||< BB / TL || 11/23 - No class ||< [|Mobile] / [|Examples]  ||< [|Bergman] - Qs ||<  ||<   ||< AL [|/] PA || 11/30 ||< [|Social] 11/30: Guest [|Jen Golbeck] ||< ID: Ch. 4 (Social) - Qs ||<  ||<   ||< KW / EN DS hofs KH || 12/7 ||< Final Project Presentations ||<  ||< MON 12/5: Final prototype, Presentation & Report ||<  ||< xx / xx xx / xx || 12/14 - No class || [|Future of HCI]  || ID: Ch. 5 (Emotional) - Qs ||  || MON 12/12: Proj comment || AS AL || 1:30-3:30pm 2107 CSIC || Final Exam [|Old final] ||  ||   ||   ||   ||
 * ~ New ||~ Week ||~ Topic (slides) ||~ Reading ||~ Term Project
 * || 1: 8/29 - No class
 * || 2: 9/5 - No class
 * || 3: 9/12
 * || 4: 9/19
 * || 5: 9/26
 * || 6: 10/3
 * || 7: 10/10
 * ||< 8: 10/17
 * ||< 9: 10/24
 * ||< 10: 10/31
 * ||< 11: 11/7
 * ||< 12: 11/14
 * ||< 13: 11/21
 * ||< 14: 11/28
 * ||< 15: 12/5
 * || 16: 12/12
 * || Mon, Dec 19


 * Homework:** All done independently. Critiques, web development, analyze problem, design and create web solution. All homework is due by class time on the due date. All reading for the week should be done before Monday's class.


 * Term Projects:** (teams of 3-4): User needs assessment, design, build, usability test, and re-design. All project deliverables are due by class time on the due date.


 * 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.

**New (10/17):** Any writing that comes from anyone but you must be clearly and explicitly cited. That is, if you quote a web page, article, person (or anything), you must indicate which text is a quote, and where that quote comes from. If you use text from another source and do not cite it as such, I will interpret this as [|plagiarism] and will treat it as such, at least giving you a 0 for the assignment, and possibly referring you to the campus honor council.

Assignments: Exams:
 * 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 according to the rules below. Instructors are not obligated 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
 * -100%: No makeups are given

Any student who wants an excused absence to avoid the above late policy must follow the following rules:
 * 1) If the absence is for a non-medical reason, then it must be discussed with the instructor **in advance**, and the instructor will make a decision on a case by case basis.
 * 2) For medically necessitated absences, the student must make a reasonable attempt to inform the instructor of his/her illness prior to the class; and
 * 3) Upon returning to the class, present their instructor with a self-signed note attesting to the date of their illness. Each note must contain an acknowledgment by the student that the information provided is true and correct. Providing false information to University officials is prohibited under Part 9(h) of the Code of Student Conduct (V-1.00(B) University of Maryland Code of Student Conduct) and may result in disciplinary action.


 * Grading:** All regrade requests must be [|applied for online] within one week of when the grades are returned to the student.
 * Exams: (15 + 15)%
 * Homework, HOF/S, and class participation: 30%
 * Term Project: 40%

   [[ima
 * Feedback:** The department and I welcome feedback about the course. Feel free to communicate directly with me at any time. But please fill out the course evaluation at the end of the semester.