Waterfall Model is simple and straightforward software process model that guides software stakeholders to develop system is organized way. It is suitable mainly for projects with low budgets. It comprise of variable stages that depend on project. Common stages of basic waterfall model are:
- Defining Requirements
Main disadvantage of this model is that requirements must be clear in prior as it can’t be changed once the system development process begins. It’s so called as waterfall as it depicts the phenomenon of water falls where one can’t move directly to previous stage for necessary adjustments. In other words, “Backtracking is not possible” in this model of software development.
Prototype is a quick design or a blueprint that we present to client before actual system development begins. And, prototyping model is refinement/improvisation of waterfall model which focuses on satisfying clients by addressing all their requirements before actual development starts. It shows overall system flow, what pages are included and how it will look like in future. We can easily modify it as per client’s feedback as it’s not actual design. Changes in actual system takes considerable time and cost so it’s better idea to follow prototyping model if client’s requirement is not so clear(or very complicated) in prior to system development.