Prototyping Flashcards
What is Prototype ?
It is a preliminary version of a product or system used to test and visualize its functionality and design
Describe how prototype can be used in requirements gathering ?
1) Visualize concepts: tangible representation of proposed products, easier for stakeholders to understand and discuss.
2) Clarify requirements: identify gaps in initial requirements , clearer project scope.
3) Collect Feedback: allow users to interact with model, insights for improvements and refinements.
4) Validate requirements: demonstrate how the requirements will be met, and aligns with stakeholder goals.
5) Detect issues early before resources are invested.
6) Mitigate risks: Identify technical , functional, and usability issues to minimize project failure.
7) Enhance documentation: contribute to more accurate users’ stories, user cases, and specifications.
Evolutionary Prototype
System built using well understood requirements.
Throwaway Prototype
System built mainly focusing on poorly understood requirements.
Not intended for final product but used as requirement gathering tools
Advantages of Prototyping
→reduce development time
→ reduce development cost
→ developers understand requirements
→ User Participation: they can see, touch & feel the model.
→ can increase creativity as users give feedback.
Disadvantages of Prototyping
→ not suitable for large applications.
→ developers lose focus on real purpose of the prototype.
→ quality of system compromised.
How can prototype be used in stages of SDLC ?
》 In feasibility
》In design
- evaluating design
-evaluate the implementation platform or DBMS
》In test
- to test loading/ response time
High Fidelity Prototyping
• resembles final product in appearance and functionality, realistic graphics
• for usability testing
• time-consuming, costly to advanced software
• detail feedback on final design
Low Fedelity Prototyping
• basic, simple representation without intricate details, colors, functionality
• used for brainstorming, quick exploration of ideas, identify issues
• quick and cost-effective, basic tools
• for rapid testing, iteration, flexible exploration of design concepts
Why does throwaway prototype can be used as ‘requirements gathering tools’
- iterative process
- risk reduction
- clarification and validation
- flexibility
- requirements exploration
smooth transition
cost efficiency
Horizontal Prototyping
Provides an in depth view of the system’s interface and overall functionality.
It aims to showcase multiple features without going into depth.
Vertical Prototyping:
Focuses on detailed implementation of a specific functionality or module, across all system layers.
Used to validate complex or critical features.
