| CptS 443/580 Human-Computer Interaction |
| Released: | 15 January 2007 |
| Covers: | Lecture #6 |
| Readings: | Preece 7 & 9 |
| Last modified: | 15 January 2007 |
As you study this week's material, please ponder the following discussion questions. Post your responses in the appropriate threads in WebCT. I may call upon you to answer a question in class.
Preece et al. are careful to use the phrase "establish requirements," as opposed to "gather requirements," "capture requirements," and the like. Why is this?
There are many kinds of requirements. Which kind is most often focused on in traditional software engineering? Which kind is most important in user-centered design? Why?
Why is it important to state usability requirements in terms of observable, measurable criteria?
Suppose that you have only limited time, and you would like to reach a broad population of potential users distributed over great distances. Which data gathering technique(s) might you choose, and why?
Suppose you want to gain in-depth information on a few key stakeholders' perspectives. Which data gathering technique(s) might you choose, and why?
When might videotaping and audiotaping be appropriate?
In what ways do your data-recording methods influence the results of your data-gathering efforts?
What role do task descriptions like scenarios, use cases, and essential use cases play in establishing requirements?
What are the key differences between scenarios, use cases, essential use cases, and task analysis?