1 PrototypingPrototyping CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 28, 2004

2 Outline Why prototype? Low-fidelity prototyping

3 Why Prototype? Visual Demonstrate sequences of events Investigate alternatives

4 Recall Story Boards Describe sequences of actions Low-fidelity: –details missing –not to scale –"unprofessional"

5 High-Fidelity Prototypes Advantages Complete functionality Fully interactive Look and feel of final solution Marketing and sales tool Disadvantages Expensive to develop Time-consuming to create Not effective for requirements gathering

6 Low-Fidelity Prototypes Advantages Lower development costs Evaluate many alternatives Useful for communication Proof-of-concept Disadvantages Limited utility after requirements Limited usefulness for usability tests Navigational and flow limitations

7 How to Paper Prototype Base pages –Static elements –One page per screen Stickies –Content before/after actions –Different placement of interface elements –Users may change these