The prototyping model of software development is :
2017
The prototyping model of software development is :
- A.
a reasonable approach when requirements are well-defined.
- B.
a useful approach when a customer cannot define requirements clearly.
- C.
the best approach to use for projects with large development teams.
- D.
a risky model that rarely produces a meaningful product.
Attempted by 493 students.
Show answer & explanation
Correct answer: B
Answer: The prototyping model is a useful approach when a customer cannot define requirements clearly.
Why this is correct: prototyping produces a working or visual model that users can interact with, which helps discover and refine real requirements through feedback and iteration.
Allows stakeholders to see and test features early, revealing unstated needs and preferences.
Supports iterative refinement: each prototype cycle improves requirements and design.
Reduces the risk of building the wrong system by validating ideas with real users early.
Drawbacks and when to be cautious:
Can encourage informal design and insufficient documentation if not paired with proper engineering practices.
May lead to scope creep if prototype scope and purpose are not clearly defined.
Less suitable as the sole approach for very large, tightly coordinated systems that need strict architecture and documentation.
Recommendation: Use prototyping when requirements are unclear and early user feedback is essential; combine it with clear objectives, limited scope for each prototype, and complementary documentation to manage risks.
A video solution is available for this question — log in and enroll to watch it.