Prototyping and Scenarios

1
Prototyping and Scenarios

2
Agenda

• Questions?
• Poster session upcoming
• Talk about Markus Keil
• Prototyping
• Scenarios
• Continuation of Norman Errors?
• Feedback on Part I

3
Poster session

• This Friday
• Things to present- prototypes (scenarios,
  storyboards, sketches, models)
• Also, domain information including usability
  criteria
• Visually appeal not too much text! Make people
  want to talk to you

4
Your thoughts on CONFIG
5
Prototyping Iterative Design

• Chicken egg problem
• Solution build partial systems, evaluate, repeat
• Facilitates iterative design

6
Dimensions of Prototypes

• Representation
• Scope
• Executability
• Maturation

7
Prototype representation

• How to represent the prototype?
• Mockup
• Storyboard
• Sketches
• Scenarios
• etc.

8
Prototype scope

• How much to represent?
• Deep prototyping
• Broad prototyping

9
Prototype executability

• Non-functional prototypes
• Functional prototypes
• Partially functional prototypes

10
Prototype maturation

• Level of polish should reflect maturity of the
  prototype
• Why?

11
Prototyping Issues

• Throw-away or incremental?
• Time and planning
• Non-functional features
• Clients contracts
• Design inertia
• Understand reasons behind usability problems

12
Techniques

• Storyboards, Sketches
• Models
• Scenarios
• Limited functionality
• Wizard of Oz
• High-level programming support

13
Storyboards

• Graphical representation of outward appearance of
  system
• Illustrate physical aspects of system
• Depict sequence of interaction

14
Sketches

• Generally for depicting physical aspects of system

15
Scenarios

• Fictional stories with characters, products,
  events and environments.
• Narratives, videos, simulations

16
Why Use Scenarios

• Focus on future and synthesis instead of present
  and analysis
• Another persons shoes
• Engaging - focus on user needs
• Alternate visions - compare
• Share with different audiences
• Explore errors and mistakes

17
Levels of Interaction

• Embody information about environment, people,
  interface, other objects and activities
• Logical, multi-sensory and emotional paths
• Detailed ideas expressed simultaneously

18
Part I feedback

• Quality mixed overall
• Common problems
• User data not reflected in descriptions of users,
  tasks, environments
• Wrong task analysis method, task analysis at too
  high a level to be interesting
• Descriptions leaning too much towards a single
  system
• Usability criteria not justified for the
  task/domain
• Over-reliance on personal experience

19
Execution Evaluation Cycle

• Norman (DOET, p.46)
• Simple idea
• Perform
• Assess
• 7 stages

20
(No Transcript)
21
You try it

• Think of a slip youve made
• What kind of slip is it?
• Where did it occur in the 7-stage cycle?

22
Part I feedback

• See CyberWaiters for excellent task analysis
• See Computer Lab Management for excellent user
  data
• See Parking Trap for excellent description of
  current system

23
Part I Grading

• Numbers correspond roughly to
• 5 A/A-
• 4 A-/B
• 3 B
• 2 C
• 1 D

24
Upcoming

• Universal design
• DFAB 10.1-10.3
• Poster session Friday