1. SBD: Analyzing Requirements Chris North cs3724: HCI

2. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders, field studies Usability specifications Activity scenarios Interaction scenarios iterative analysis of usability claims and re-design metaphors, information technology, HCI theory, guidelines formative evaluation DESIGN ANALYZE PROTOTYPE & EVALUATE

3. Analyzing Requirements Goal: understand users’ current activities well enough to reason about technology-based enhancements

4. Analyzing Requirements 1.Root concept 2.Field studies (ethnography) Contextual inquiry (ask during) Participatory analysis (ask after) Explicit vs tacit knowledge 3.Summaries 4.Problem scenarios Story of current activity 5.Claims analysis +/- impacts

5. Categories People hypotheticals Activities HTA subgoals Artifacts usage Social context relationships

6. Summaries: stakeholder, task, and artifact analyses, general themes Root concept: vision, rationale, assumptions, stakeholders Problem scenarios: illustrate and put into context the tasks and themes discovered in the field studies Claims analysis: find and incorporate features of practice that have key implications for use Field studies: workplace observations, recordings, interviews, artifacts SBD and Requirements Analysis

7. Grocery Shopping

8. HW 1 HTA Kroger’s checkout