In my last post I discussed how there are many great advantages to using the waterfall model in software development. But like in many situations in life there are also some disadvantages to using the waterfall model.
- Ironic as it may sound one of the models biggest advantages is also its biggest disadvantage. When a step is constructed, completed and reviewed and you move onto the next stage you can not go back and make alterations. This proves a disadvantage as it is difficult to go back and make an alteration if something goes wrong in a future stage.
- Another disadvantage would be that there is no physical software produced until late in the development process. The user then does not get to see the software. This is bad as if the user is not happy with it, it is too late.
- Aswell as that, the waterfall model only works well on smaller projects. It is not suited to large scale, complex models.
- This model also does not suit when the user is not fully sure what he is looking for at the end of it, if the user is partial to some changing requirements throughout the project the developer can not go back on the stages that have already been completed.
I hope this shows you how as well as advantages there are also disadvantages to this model.