Introduction: What is HCI?
Introduction: What is design? … and usability?
Design vs. Science
Capabilities: Model Human Processor
Design » foundations » overview
Design » foundations » affordances, mental models
Design » foundations » goals, actions
Design » foundations » direct manipulation
Design » methods » Paper prototyping
Design » methods » Prototyping
Design » problem solving » Introduction, guidelines
Design » problem solving » Brainstorming
Design » problem solving » Discovery
Design » problem solving » Contextual design
Design » formalisms » QOC notation for design rationales
Design » formalisms » cognitive dimensions of notations
Design » end-user programming
End-user programming, undo
Review of 5 facets of usability
chapter 2 in book
Heuristics » heuristic evaluation exercise
User goals, Keystroke-Level Model (KLM)
Keystroke-Level Model (KLM), exercise
Security » usable security, problems
Security » phishing
Evaluation » visualization insight
Evaluation » principles
Evaluation » planning a study
Evaluation » metrics
For each reading, write a response (≈150-300 words) and post it to Blackboard by 2:30pm on the day the reading is listed for. You may give a mini-review (i.e., what was strong and/or weak), a rebuttal, a detailed comparison to something you have worked on or read, or some combination of those. Your response should demonstrate that you read and understood it, without summarizing. You can also describe something you found surprising, but be clear about why it went against your expectations.
Responses should be readable and concise. Bullets and bold text are encouraged.
Responses are intended to spearhead discussion in class. We will frequently refer to individual responses.
- Do not summarize (e.g., “The paper says that __.”).
- Be specific and/or give reasons (e.g., “__ seems good.”).
- Avoid empty sentences (e.g., “I really like __.” or “__ is interesting.”)
- Comment on the ideas in the reading, not the writing (e.g., “The introduction is not clear.”) or superficial aspects of the presentation (e.g., “Figure ___ is hard to read when printed in B&W.”). Those things are important, but that's not what this excercise is about.
- Do not copy any text verbatim from anywhere, unless it is in quotation marks. If you quote from anything other than the reading you are writing about, be sure to site the source.
Most responses will get 1 point. Those that are exceptionally insightful and clear will get 2 points. Those that are very vague, inaccurate, or merely paraphrase the abstract will get 0 points.
Starting in week
2, there will be a couple very short questions to answer about each reading, regarding the contribution type. This will be explained on 1/12/2018.I am making the submission time (2:30pm) as late as possible, while still giving me time to read them before class. If that becomes a challenge, I might shift it earlier later on. Let's see how this goes.
How to read papers for this course
Many people find it easier to read papers if they have a purpose in mind. As you read each paper, you might find it helpful to focus on a few questions:
- What was the contribution type? (examples)
- What do the authors claim as their key contributions?
- What strategies, methods, and technologies were used?
- What generalizable knowledge does the work contribute? What research questions does it address? How will this benefit other researchers?
- Do you find the conclusions convincing? Are the results well-supported by data obtained with sound methods?
- What aspects of the work you find strongest? … and weakest?
- What would be a natural next step for the work?
Note: These questions are included to help guide your reading. They won't apply to all of the readings. Unless otherwise announced, you do not need to answer these questions in your response.