|
What is interaction design? |
|
|
1 | (34) |
|
|
1 | (1) |
|
|
2 | (4) |
|
|
4 | (2) |
|
What is interaction design? |
|
|
6 | (6) |
|
The makeup of interaction design |
|
|
6 | (3) |
|
Working together as a multidisciplinary team |
|
|
9 | (1) |
|
Interaction design in business |
|
|
10 | (2) |
|
What is involved in the process of interaction design? |
|
|
12 | (1) |
|
The goals of interaction design |
|
|
13 | (7) |
|
|
14 | (4) |
|
|
18 | (2) |
|
More on usability: design and usability principles |
|
|
20 | (11) |
|
Heuristics and usability principles |
|
|
26 | (5) |
|
Interview with Gitta Salomon |
|
|
31 | (4) |
|
Understanding and conceptualizing interaction |
|
|
35 | (38) |
|
|
35 | (1) |
|
Understanding the problem space |
|
|
36 | (3) |
|
|
39 | (16) |
|
Conceptual models based on activities |
|
|
41 | (10) |
|
Conceptual models based on objects |
|
|
51 | (3) |
|
|
54 | (1) |
|
|
55 | (5) |
|
|
60 | (4) |
|
From conceptual models to physical design |
|
|
64 | (6) |
|
Interview with Terry Winograd |
|
|
70 | (3) |
|
|
73 | (32) |
|
|
73 | (1) |
|
|
74 | (16) |
|
Applying knowledge from the physical world to the digital world |
|
|
90 | (2) |
|
Conceptual frameworks for cognition |
|
|
92 | (9) |
|
|
92 | (4) |
|
|
96 | (2) |
|
|
98 | (3) |
|
Informing design: from theory to practice |
|
|
101 | (4) |
|
Designing for collaboration and communication |
|
|
105 | (36) |
|
|
105 | (1) |
|
Social mechanisms used in communication and collaboration |
|
|
106 | (23) |
|
Conversational mechanisms |
|
|
107 | (3) |
|
Designing collaborative technologies to support conversation |
|
|
110 | (8) |
|
|
118 | (4) |
|
Designing collaborative technologies to support coordination |
|
|
122 | (2) |
|
|
124 | (2) |
|
Designing collaborative technologies to support awareness |
|
|
126 | (3) |
|
Ethnographic studies of collaboration and communication |
|
|
129 | (1) |
|
|
130 | (8) |
|
The language/action framework |
|
|
130 | (3) |
|
|
133 | (5) |
|
Interview with Abigail Sellen |
|
|
138 | (3) |
|
Understanding how interfaces affect users |
|
|
141 | (24) |
|
|
141 | (1) |
|
What are affective aspects? |
|
|
142 | (1) |
|
|
143 | (4) |
|
|
147 | (6) |
|
Dealing with user frustration |
|
|
152 | (1) |
|
A debate: the application of anthropomorphism to interaction design |
|
|
153 | (4) |
|
Virtual characters: agents |
|
|
157 | (8) |
|
|
157 | (3) |
|
|
160 | (5) |
|
The process of interaction design |
|
|
165 | (36) |
|
|
165 | (1) |
|
What is interaction design about? |
|
|
166 | (4) |
|
Four basic activities of interaction design |
|
|
168 | (2) |
|
Three key characteristics of the interaction design process |
|
|
170 | (1) |
|
|
170 | (12) |
|
|
171 | (1) |
|
What do we mean by ``needs''? |
|
|
172 | (2) |
|
How do you generate alternative designs? |
|
|
174 | (5) |
|
How do you choose among alternative designs? |
|
|
179 | (3) |
|
Lifecycle models: showing how the activities are related |
|
|
182 | (16) |
|
A simple lifecycle model for interaction design |
|
|
186 | (1) |
|
Lifecycle models in software engineering |
|
|
187 | (5) |
|
|
192 | (6) |
|
Interview with Gillian Crampton Smith |
|
|
198 | (3) |
|
Identifying needs and establishing requirements |
|
|
201 | (38) |
|
|
201 | (1) |
|
|
202 | (2) |
|
What are we trying to achieve in this design activity? |
|
|
202 | (1) |
|
|
202 | (1) |
|
Why bother? The importance of getting it right |
|
|
203 | (1) |
|
Why establish requirements? |
|
|
204 | (1) |
|
|
204 | (6) |
|
Different kinds of requirements |
|
|
205 | (5) |
|
|
210 | (9) |
|
Data-gathering techniques |
|
|
211 | (4) |
|
Choosing between techniques |
|
|
215 | (1) |
|
Some basic data-gathering guidelines |
|
|
216 | (3) |
|
Data interpretation and analysis |
|
|
219 | (3) |
|
|
222 | (9) |
|
|
223 | (3) |
|
|
226 | (3) |
|
|
229 | (2) |
|
|
231 | (5) |
|
Hierarchical Task Analysis (HTA) |
|
|
231 | (5) |
|
Interview with Suzanne Robertson |
|
|
236 | (3) |
|
Design, prototyping and construction |
|
|
239 | (40) |
|
|
239 | (1) |
|
Prototyping and construction |
|
|
240 | (9) |
|
|
240 | (1) |
|
|
241 | (2) |
|
|
243 | (2) |
|
High-fidelity prototyping |
|
|
245 | (1) |
|
Compromises in prototyping |
|
|
246 | (2) |
|
Construction: from design to implementation |
|
|
248 | (1) |
|
Conceptual design: moving from requirements to first design |
|
|
249 | (15) |
|
Three perspectives for developing a conceptual model |
|
|
250 | (7) |
|
Expanding the conceptual model |
|
|
257 | (2) |
|
Using scenarios in conceptual design |
|
|
259 | (3) |
|
Using prototypes in conceptual design |
|
|
262 | (2) |
|
Physical design: getting concrete |
|
|
264 | (11) |
|
Guidelines for physical design |
|
|
266 | (2) |
|
Different kinds of widget |
|
|
268 | (7) |
|
|
275 | (4) |
|
User-centered approaches to interaction design |
|
|
279 | (38) |
|
|
279 | (1) |
|
Why is it important to involve users at all? |
|
|
280 | (5) |
|
|
281 | (4) |
|
What is a user-centered approach? |
|
|
285 | (3) |
|
Understanding users' work: applying ethnography in design |
|
|
288 | (18) |
|
|
293 | (2) |
|
|
295 | (11) |
|
Involving users in design: Participatory Design |
|
|
306 | (7) |
|
|
307 | (2) |
|
|
309 | (4) |
|
Interview with Karen Holtzblatt |
|
|
313 | (4) |
|
|
317 | (22) |
|
|
317 | (1) |
|
What, why, and when to evaluate |
|
|
318 | (6) |
|
|
318 | (1) |
|
|
319 | (4) |
|
|
323 | (1) |
|
|
324 | (12) |
|
How the team got started: early design ideas |
|
|
324 | (3) |
|
How was the testing done? |
|
|
327 | (6) |
|
|
333 | (1) |
|
|
334 | (2) |
|
|
336 | (3) |
|
|
339 | (20) |
|
|
339 | (1) |
|
Evaluation paradigms and techniques |
|
|
340 | (8) |
|
|
341 | (4) |
|
|
345 | (3) |
|
Decide: A framework to guide evaluation |
|
|
348 | (8) |
|
|
348 | (1) |
|
|
349 | (1) |
|
Choose the evaluation paradigm and techniques |
|
|
349 | (1) |
|
Identify the practical issues |
|
|
350 | (1) |
|
Decide how to deal with the ethical issues |
|
|
351 | (4) |
|
Evaluate, interpret, and present the data |
|
|
355 | (1) |
|
|
356 | (3) |
|
|
359 | (30) |
|
|
359 | (1) |
|
Goals, questions and paradigms |
|
|
360 | (4) |
|
|
361 | (2) |
|
Approaches to observation |
|
|
363 | (1) |
|
|
364 | (9) |
|
In controlled environments |
|
|
365 | (3) |
|
|
368 | (2) |
|
Participant observation and ethnography |
|
|
370 | (3) |
|
|
373 | (4) |
|
|
374 | (1) |
|
Audio recording plus still camera |
|
|
374 | (1) |
|
|
374 | (3) |
|
Indirect observation: tracking users' activities |
|
|
377 | (2) |
|
|
377 | (1) |
|
|
377 | (2) |
|
Analyzing, interpreting and presenting data |
|
|
379 | (8) |
|
Qualitative analysis to tell a story |
|
|
380 | (1) |
|
Qualitative analysis for categorization |
|
|
381 | (3) |
|
Quantitative data analysis |
|
|
384 | (1) |
|
Feeding the findings back into design |
|
|
384 | (3) |
|
|
387 | (2) |
|
|
389 | (40) |
|
|
389 | (1) |
|
|
390 | (8) |
|
Developing questions and planning an interview |
|
|
390 | (2) |
|
|
392 | (2) |
|
|
394 | (1) |
|
Semi-structured interviews |
|
|
394 | (2) |
|
|
396 | (1) |
|
Other sources of interview-like feedback |
|
|
397 | (1) |
|
Data analysis and interpretation |
|
|
398 | (1) |
|
Asking users: Questionnaires |
|
|
398 | (9) |
|
|
398 | (2) |
|
Question and response format |
|
|
400 | (4) |
|
Administering questionnaires |
|
|
404 | (1) |
|
|
405 | (2) |
|
Analyzing questionnaire data |
|
|
407 | (1) |
|
Asking experts: Inspections |
|
|
407 | (13) |
|
|
408 | (2) |
|
Doing heuristic evaluation |
|
|
410 | (2) |
|
Heuristic evaluation of websites |
|
|
412 | (7) |
|
Heuristics for other devices |
|
|
419 | (1) |
|
Asking experts: walkthroughs |
|
|
420 | (6) |
|
|
420 | (3) |
|
|
423 | (3) |
|
Interview with Jakob Nielsen |
|
|
426 | (3) |
|
Testing and modeling users |
|
|
429 | (32) |
|
|
429 | (1) |
|
|
430 | (8) |
|
|
432 | (6) |
|
|
438 | (5) |
|
Determine the goals and explore the questions |
|
|
439 | (1) |
|
Choose the paradigm and techniques |
|
|
439 | (1) |
|
Identify the practical issues: Design typical tasks |
|
|
439 | (1) |
|
Identify the practical issues: Select typical users |
|
|
440 | (1) |
|
Identify the practical issues: Prepare the testing conditions |
|
|
441 | (1) |
|
Identify the practical issues: Plan how to run the tests |
|
|
442 | (1) |
|
|
443 | (1) |
|
Evaluate, analyze, and present the data |
|
|
443 | (1) |
|
|
443 | (5) |
|
|
444 | (1) |
|
Allocation of participants to conditions |
|
|
445 | (1) |
|
|
446 | (1) |
|
Data collection and analysis |
|
|
446 | (2) |
|
|
448 | (9) |
|
|
449 | (1) |
|
The Keystroke level model |
|
|
450 | (3) |
|
Benefits and limitations of GOMS |
|
|
453 | (1) |
|
|
454 | (3) |
|
Interview with Ben Shneiderman |
|
|
457 | (4) |
|
Design and evaluation in the real world: communicators and advisory systems |
|
|
461 | (30) |
|
|
461 | (1) |
|
|
462 | (1) |
|
Designing mobile communicators |
|
|
463 | (19) |
|
|
463 | (1) |
|
Nokia's approach to developing a communicator |
|
|
464 | (10) |
|
Philip's approach to designing a communicator for children |
|
|
474 | (8) |
|
Redesigning part of a large interactive phone-based response system |
|
|
482 | (9) |
|
|
483 | (1) |
|
|
483 | (8) |
Reflections from the Authors |
|
491 | (2) |
References |
|
493 | (10) |
Credits |
|
503 | (6) |
Index |
|
509 | |