Software Lifecycle - Waterfall Method

If you remember last week's Software Lifecycle post, at the end I wrote that there are methodologies to follow the steps defined in the SDLC.

Today in this TC1019's express blog post, I will write about the Waterfall Model (WM), a software development methodology. This is a very simple topic.

The WM is called like that because each step is executed lineally and individually, with the output of one step being the input of the other, if you put it in a diagram, it would look like this:

Source

Hence the name waterfall method, it is the most basic and widely used model, also the first one to appear. Its application is recommended when the software requirements are well defined, the project is short and customer input is not usually required. The software definition must be stable.

Here are the advantages and disadvantages of this model:

Advantages	Disadvantages
Simple and easy Well-defined stages and deliverables Non-overlapping phases Good for small and well-understood projects.	Once finished, the application cannot be changed easily. The product is delivered at the end, no minimum viable product to test. Not good for complex and long-running projects. Specification changes are not easily incorporated.

Hope you learned something today :) 

Sources:

http://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm

http://istqbexamcertification.com/what-is-waterfall-model-advantages-disadvantages-and-when-to-use-it/