SBD:Analyzing Requirements

Chris North

cs3724: HCI

Problem scenarios

summativeevaluation

Information scenarios

claims about current practice

analysis ofstakeholders,field studies

Usability specifications

Activityscenarios

Interaction scenarios

iterativeanalysis ofusability claims andre-design

metaphors,informationtechnology,HCI theory,guidelines

formativeevaluation

DESIGN

ANALYZE

PROTOTYPE & EVALUATE

Analyzing Requirements

• Goal: understand users’ current activities well enough to reason about technology-based enhancements

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 andRequirementsAnalysis

Categories

• People

• Activities

• Artifacts

• Social context

The ethnographic method

Field studies, not lab experimentsComes from anthropologyGeneralize from the few and the particularIt’s just one possible method

Explicit vs tacit knowledge Approaches:

• Contextual inquiry (ask during)

• Participatory analysis (ask after)

Some suggestions on how to see

Leave your categories at home…Forgetting is seeing things anew.

ListenTalkReflect on what you’ve seen and heard

Does it make sense?Can you tell a complete story?

Representations

• How to represent the problem?

• Scenarios

• Video, pictures, storyboard

• HTA: hierarchical task analysis

Grocery Shopping

ProjectW/Th: teams & topics

2 weeks: Requirements AnalysisYour mission: find out about your users

• Who are they? • What matters to them?• What do they do in their work? • What is unexpected?• How do they now get to the information your project will

present to them?• What is the scenario of their current work practice?• Can you imagine alternate scenarios?

Start NOW!