CS&P meeting 16 Jan 2012 1

Scenario-driven approach - what is it good for?

Lydia LauCollaborative Systems and

Performance Research Group Seminar

CS&P meeting 16 Jan 2012 2

My research problem space

• CSCW (Computer Supported Collaborative Work)– Evolved from “office automation” to “community collaboration”– From process automation (with human in the loop) to knowledge sharing and

discovery (trying to tackle tacit knowledge)• Infrastructure to support the above – Need to identify components• Design - How do we know the design is/was good? Need domain input + evaluation!

designreal world in action requirements

technical requirements

world of gadgets

cool designfor new practice

design

CS&P meeting 16 Jan 2012 3

The designer-developer-adopter gaps• Who are adopters? (not always end users)?• Who are developers? (and in open-source environment)?• Who are designers? (is there such an explicit role)?

Tim Berners-Lee Mark Zuckerberg What’s common between:

Concept of ‘value chain’ (Porter) to help positioning?

CS&P meeting 16 Jan 2012 4

Today’s topic: Scenario-driven approach!

• What is it? Why? How? When?– Sutcliffe’s chapter

• Reflection / discussion– Good and bad scenario?– Right / wrong expectation?– How do we know we are on the right track?

CS&P meeting 16 Jan 2012 5

What and Why

Scenario-driven approach• story telling (plot / actor / actions) for• capturing– Tacit knowledge– Context – Intention (goals)– Outcome

from• Designers / developers / adopters / end users

CS&P meeting 16 Jan 2012 6

Rosson & Carroll (2002): Scenario-based Usability Engineering

CS&P meeting 16 Jan 2012 7

Sutcliffe (2012)Fig. Use of scenarios in different phases of the Requirements Engineering-Software

Engineering process

CS&P meeting 16 Jan 2012 8

Scenarios sampled at random

• medical traininghttp://www.gp-training.net/training/educational_theory/pbl/scenario.htm

• usage scenario for a use casehttp://www.agilemodeling.com/artifacts/usageScenario.htm

• part of software development (product scenarios)

http://publib.boulder.ibm.com/infocenter/esbsoa/wesbv7r5/index.jsp?topic=%2Fcom.ibm.websphere.wesb.programming.doc%2Ftopics%2Fesbprog_bomapper_xslt_scen.html

CS&P meeting 16 Jan 2012 9

Some tips

• http://www.infodesign.com.au/ftp/Scenarios.pdf • http://dannorth.net/whats-in-a-story/ Reading• Online excerpt from Rossen & Carroll (2002)http://ldt.stanford.edu/~gimiller/Scenario-Based/scenarioIndex2.htm

• Alistair G. Sutcliffe (2012), "Requirements Engineering", in Soegaard, Mads, et al. (Eds). Encyclopedia of Human-Computer Interaction.

http://www.interaction-design.org/encyclopedia/requirements_engineering.html

• L.M.S. Lau (2008) http://www.comp.leeds.ac.uk/llau/publications/final-scenario.pdf

CS&P meeting 16 Jan 2012 10

Today’s topic: Scenario-driven approach!

• What is it? Why? How? When?– Sutcliffe’s chapter

• Reflection / discussion– Good and bad scenario?– Right / wrong expectation?– How do we know we are on the right track?

CS&P meeting 16 Jan 2012 11

From the discussion:Pros• human can remember / telling a story better, but not details - good for eliciting

knowledge from user• help with temporal aspects + social aspects + context• help non-domain people understand Cons• unsure of assumptions - • possibility discovery of new knowledge• time consuming• not everyone a good story teller• approach to getting problem scenario is different from getting visioning

scenario (prototype is natural next step)

Main point: Skills of the analyst are important!