1. Part 2b: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding Out about Tasks and Work Chapter 5: Requirements Gathering: Knowledge of the User Interface Design Chapter 6: Thinking about Requirements and Describing Them Chapter 7: Case Study on Requirements, Part 1 Video: Paper Prototyping

2. Process Discovery Phase –What How –WhereWhen –WhoWhy Conceptual Design Physical Design Evaluation

3. Personas A persona is a fictional person who represents a major user group for your application. Good Web Reference for creating personas at Usability.gov –http://www.usability.gov/methods/analyze_current/http://www.usability.gov/methods/analyze_current/

4. Task Analysis Task analysis means learning about your users' goals –What they want to do with your program –How they currently achieve these goals Task analysis can also mean figuring out –More specific tasks users must do to meet those goals and –What steps they must take to accomplish those tasks. Along with user and task analysis, we often do a third type of analysis: –Understanding users' environments (physical, social, cultural, and technological environments) See Usability.gov at http://www.usability.gov/methods/analyze_current/analysis.html http://www.usability.gov/methods/analyze_current/analysis.html