Content
- Overview
- When to use?
- Iterative Process
- Kinds of Prototypes
- Tips
Overview
A limited version or small part of the system; quickly implemented.
- Requirement Elicitation
- Visualize part of the system
- Get feedback from stakeholders
- Stakeholders comment early on something tangible
When to use?
- Close the gap between user & developer
- Parts of the requirements still not clear after using other elicitation techniques
- Stakeholders can't describe what they want
- Stakeholders want to visualize use cases
- Multiple ways to deliver the required behavior, not sure which one most effective
- Full development technique when not sure requirements feasible
Iterative Process
Identify basic requirements ---> Build prototype ---> User evaluates prototype ---> Complete
Quick UI design ↑______ Improve design______|
Kinds of Prototypes
| Scope\Fate | Throwaway | Evolutionary |
|---|---|---|
| Horizontal | Clarify/refine requirements; Explore forms of UI | High-quality presentation layer; High-priority use cases first |
| Vertical | Demonstrate feasibility | Incremental development; Test, tune, & demonstrate performance |
- Both scopes are risk-reduction
- Decide the fate before constructing prototype
Tips
- Paper prototypes are useful for user critiques
- Watch users work with the prototype; ask specific questions
- Don't waste time making the prototype detailed & realistic; but use sensible data
- Don't prototype what you already know
- Make sure the stakeholders understand the purpose of the prototype