I just want to know if there is an issue with the development of a prototype using iterative waterfall model in comparison to using prototype lifecycle?
closed as unclear what you're asking by Todd A. Jacobs♦ Oct 11 '18 at 13:59
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
The goal of a prototype is to learn more about your product. An iterative waterfall method still puts the analysis and design up front and then iterates through building - you still assume you know what needs to be built. This pushes learning to the end. The prototyping lifecycle is cyclical and wraps learning in as you go. Given the purpose of the prototype, an iterative waterfall seems to work against that purpose.