FIT2001 Lecture Notes - Lecture 5: Scope Creep, Low Fidelity, High Fidelity
L5 - Investigating System Requirements - Prototyping, Developing Usable
systems
Prototyping
What: Process of quickly mocking up the future of a system
+ Explore ideas before investing in them → Saves time and money
+ Shows relationship between systems
+ Allows design exploration
- Risk users may thin system is developed
- Waste time → making it look good
- Create a system that doesn’t scale
Do’s:
- Work collaboratively with all stakeholders
- Avoid prototype creep
- Build in realistic delays for high-fidelity prototypes
- Reuse, save template for future projects
- Remind everybody - just a prototype!!
Don’ts:
- Prototype features that can’t be implemented
- Take every change from reviewing a prototype as a new requirement → scope creep
YIKES!
- Be a perfectionist
- Prototype everything! Just enough to understand what’s required
Fidelity:
- Visual fidelity: the level of styling
- Functional fidelity: level of interactivity
- Content fidelity: use of dummy text vs meaning content
Prototyping spectrum:
- Low fidelity: rough paper based mockups
- Medium fidelity: use computer based tools, simulates actions/ behaviour of application
- High fidelity: most realistic, food for developers and usability testing and often mistaken
for final product