Scenario Plus
List of Prototyping Techniques

 

Prototyping simply means trying something out. Good prototyping

Prototyping is most likely to be successful if planned for, and done early.

Playfully creating a set of many small prototypes is better than laboriously (and wastefully) polishing a few large ones.

Technique Purpose Suitable Tools Risks

"Screen" Mockup

  1. discover functional requirements

  2. agree user interface design (Warning: this can be a distraction)

  • Flipchart and coloured marker pens

  • Blanket and pieces of coloured felt

  • A presentation tool
    (eg Powerpoint)

  • A User Interface tool
    (eg Visual Basic)

  • Wasting time on appearance of prototype

  • Being distracted into user interface design and debates on house style

  • Designing the actual software (especially if software tools are used)

Scenarios, Stories,
Use Cases

  1. discover functional requirements

  2. discover threats, hazards, exceptions

  • Workshop

  • Flipchart and pens

  • Spreadsheet

  • Templates

  • Storyboards

  • Acted scenes, etc

  • "Rabbit holes" (wasting time on details)
Simulation, Breadboard, etc
  1. demonstrate feasibility
  • Simulation tool
  • Custom software or hardware (not of production quality)
  • Wasting time making model "perfect"
  • Wasting time on error-handling, user interface of custom software
  • Management wanting to reuse throwaway software as the actual product
Analogy
  1. discover functional requirements
  2. stimulate creativity
  • Workshop
  • Products (from other areas) with relevant features
  • Techniques from other fields
  
...      

Many other special techniques are possible and occasionally useful.

Contact

Home

(c) Scenario Plus 1997-2007