Answer:
Answer explained below
Explanation:
Depending upon the current situation we can switch. That means suppose the entire project is mid way that means we already implemented the project by Waterfall methodology then it would take lot of time to switch to Prototype model. Again if we see the efficiency I mean if we complete the project using prototype model and the outcome would be very well and robust then we should definitely switch to prototype model. So depending on the scenario we need to decide whether it would be beneficial to switch or not.
Further, we have the differences between Waterfall and Prototype :
I) In case of Waterfall model requirements should be very well known. On the other hand in case of prototype model if the user requirements are not complete then we can choose prototype model.
II) Technical issues should be cleared in case of Waterfall model, on the other hand technical requirements need not be clear.
Advantages of Waterfall:
I) Easy to understand this model and easy to use.
II) It provides structure to inexperienced staff
III) Milestones are well understood
IV) Set requirements stability
Disadvantages of Waterfall Model:
I) All requirements must be known upfront
II) Inhibits flexibility
III) Can give a false impression of progree
Advantage of Prototype Model:
I) Even if user requirements are not complete we can use
II) Even if technical issues are not clear we can use
Disadvantage of Prototype:
I) The Model is complex
II) Risk Assessment expertise is required
III)Time spent for evaluating risks too large for small projects.
