06.documenting the task
Read this to prepare for class discussion
-
Universal principles of design
Hick's Law, 120
Fitt's Law, 98 -
from Sharp, Rogers, & Preece,
Chapter 10, Establishing requirements- Section 10.6, Task description, 373-383
- Section 10.7, Task analysis, 383-387
-
Gruen, D., Rauch, T., Redpath, S., & Ruettinger, S. (2002).
The use of stories in user experience design.
International Journal of Human-Computer Interaction, 14(3&4), 503-534.
⇒ Focus on the first two sections, pages 503-511; skim section 3. -
Go, K., & Carroll, J.M. (2004).
The blind men and the elephant: Views of scenario-based system design.
interactions, 11(6), 44-53
⇒ Focus on pages 45-50. [ACM Digital Library]
Optional readings which may come up in class discussions
-
Carroll, J. M. (2000).
Five reasons for scenario-based design.
Interacting with Computers, 13(1), 43-60. -
Diaper, D. (2002).
Discussion: Task scenarios and thought.
Interacting with Computers, 14(5), 629-638. -
Sutcliffe, A. (2003).
Symbiosis and synergy? Scenarios, task analysis and reuse of HCI knowledge.
Interacting with Computers, 15(2), 245-263.
Useful, but not available online
-
Cockburn, A. (2000).
Writing Effective Use Cases.
Reading, MA: Addison-Wesley Professional. [QA76.76.A65 C63 2001]
⇒ Section 1.1, What is a use case (more or less)?, p1-6
⇒ Section 2.1, Interactions between actors with goals, p23-29
⇒ Section 7.2, Action steps, p90-97
[top]