Waterfall Methodology Page 1

Advantages And Disadvantages

The Waterfall Methodology

Waterfall Methodology Page 2

The waterfall methodology is a model used by designers and developers of software products. It's a process that is made up of six steps that aims to cover everything from requirement analysis to maintenance.

This model is a popular center of software-related talks, especially as different people have different views on it. One of the most particular points being debated about the model is the issue of waterfall methodology advantages vs disadvantages.

If you don't have any idea which side to take up, this discussion below of the framework's advantages and disadvantages may be of significance. Advantages The waterfall methodology is a framework that closely follows all of its six phases. Designers and developers, then, need to make sure that the expected milestones of all the phases would be satisfied at their pre-defined time. This makes discipline an essential trait that all designers and developers must have. Also, as the methodology aims to expect and then define issues and fix them before they manifest, clients can have a product that would perform the best way that it could, especially if the whole process has been planned comprehensively well. The whole team would also be able to tell the clients when they can get their software product. This would be really great for those who want to see how the product can fit into their network, and what it can do for their business. Also, the waterfall methodology is a framework that is built on a foundation of early definition and pre-determination. The team, thus, can ensure that they would work according to what they intend to achieve and make the whole process work out.

Waterfall Methodology Page 3

Disadvantages The waterfall methodology gives a lot of focus on getting what clients want out of the software product, and some people think this is problematic primarily

because clients don’t know what they really want, in the first place. Customers only begin to have an idea of what they need the product to do until after they have seen the things they don’t want the product to do. The model does not readily go back phases to correct earlier issues which may impede the progress

of the other phases, and the whole process. Also, the division of labor between the different people in the team is insisted upon by the framework, but most companies find that it isn’t what happens during the actual design and development process.