Question

A throwaway prototype is most appropriate when:

A. Users need to judge whether the requirements will enable the necessary business processes
B. Have difficulty envisioning the system from the requirements alone
C. reaching a better understanding thelogical requirements
D. The gaps between customers and developers in the requirements
E. the team faces uncertainty. ambiguity. incompleteness. or vagueness in the requirements

Answer 1

A throwaway prototype is most appropriate when the team faces uncertainty, ambiguity, incompleteness, or vagueness in the requirements.

Step-by-step explanation:

A throwaway prototype is most appropriate when the team faces uncertainty, ambiguity, incompleteness, or vagueness in the requirements. This type of prototype is used to quickly explore potential solutions and gather feedback. It is not intended to be a final design, but rather a tool for learning and refining the requirements.