Tuesday reading group Nov Scenario-driven design for collaborative systems Specific points for today (based on my paper, 2008) - An attempt to address human factors, esp. for new ways of working with new applications - What is a scenario? (next slide) - When? (requirements capture & evaluation, but see Rossen & Carroll 2002) - How? (ensure quality of scenario is grounded on stakeholders contribution; capture the essential features; see examples in paper)

Tuesday reading group Nov An example of a scenario From Use and Refinement of a Teaching Aid. Jane is trying to facilitate more productive discussion in her graduate class. Students are required to annotate electronic copies of the weekly assigned readings. The prototype collects these, and merges them, enabling Jane to project and point to different versions on the 3 large displays in the teaching room, and start discussing why different students had highlighted or commented on different parts of the research paper. The next day Jane meets with the research team to review what happened when she tried out the prototype in class. They review the use log data, trying out different visualizations to help in understanding what worked well, what was awkward to use, or performed poorly, and why. Next they work on how they can improve the design before the next class. But there are variations ….see p.2 of paper

Tuesday reading group Nov Rosson & Carroll (2002): Scenario- based Usability Engineering

Tuesday reading group Nov Discussion points In general In Wichais case study