Why should you use waterfall model in software projects?

Answer 1

Waterfall model tends to consume a lot more time compared to other software development models though it is able to pinpoint definite starting and ending points for a given project. This model assumes the requirements to remain static during the life of the project, so there is little or no chance of incorporating new changes to the software once work begins. If changes are tried to be incorporated it leads to more confusion and further delays. Its strong points lie in the fact that it is sequential, so there would be no confusion on the steps and the processes are straight down--no need to worry about so many conditions while working on a project. Additionally, this type of model tends to pack up on so much documentation. Therefore, such tends to be useful for future code revisions and reference. However, its drawbacks become apparent in the length of time a project will be developed and the cost it is able to consume.

Answer 2

•Simple and easy to use

•Easy to manage due to the rigidity of the model - each phase has specific deliverables and a review process.

•Phases are processed and completed one at a time.

•Works well for smaller projects where requirements are very well understood

Answer 3

An Advantage is that it is reasonably good for new projects and it is a good model to teach

The Main Disadvantage of the waterfall model is that it does not allow for very much Iteration.

for example you are in the testing stage and you realize that something has not been designed correctly.

In theory if following the model as closely as possible and trying to make it iterative this would lead you back to the design stage and then through the implementation until you arrived back at testing again

Answer 4

Waterfall model has following advantages :

1) Each stage has well defined deliverable or milestones.

2) It acts as a template (guiding model) into which methods for analysis, design, code, test and maintenance can be placed.

Answer 5

• Time Consuming
• Costly
• Programmer can not move on to the next step unless the previous is completed

Answer 6

In water fall model we have to make a product in one go we cannot go back into previous phase. In prototype model we make test product that depicts what our end product will look like.