ID+Ch+10+Qs


 * Questions for Chapter 10 of Interaction Design, "Establishing Requirements**" **by Yvonne Rogders, Helen Sharp, and Jennifer Preece:**
 * 1) What are //requirements// in the context of interaction design?
 * 2) What is the purpose of requirements in interaction design? How do requirements relate to the activities of designers and to users?
 * 3) What are some challenges that arise when establishing requirements? What are some methods for managing and overcoming these challenges?
 * 4) What is the //requirements activity//? What are at least two goals of this activity?
 * 5) Requirements are not necessarily represented as a document or an unchanging list of needs. What are some other forms of requirements? When might these be appropriate?
 * 6) What are some of the activities involved in the process of establishing requirements? When does this process occur in relation to the design and development processes?
 * 7) Why is it important to establish, correct, and refine requirements throughout the design and development process?
 * 8) What are some costs of correcting and refining requirements late in the design and development processes?
 * 9) What is the origin of requirements? Who comes up with them?
 * 10) What are some different kinds of requirements?
 * 11) What is the purpose of data gathering in the requirements activity?
 * 12) What are some of the data gathering activities that can be performed when establishing requirements?
 * 13) Why is it useful to study documentation and research similar products when gathering data in the requirements activity?
 * 14) What are //scenarios// and //use cases//?
 * 15) How is task analysis useful for establishing requirements? What kinds of information does it yield?
 * 16) What is hierarchical test analysis?
 * 17) What are some benefits and problems associated with hierarchical task analysis?