Prototyping (throwaway) is BEST when…
Answer options
A
UI/requirements are unclear and need quick visual feedback
B
Requirements are fixed and stable
C
Risk analysis is the main driver
D
The project is safety critical
Correct answer: UI/requirements are unclear and need quick visual feedback
Explanation
Quick AnswerThe correct answer is UI/requirements are unclear and need quick visual feedback because it directly addresses the core logic of Software Engineering.
Throwaway prototypes help elicit unclear requirements, then are discarded.