{"id":37545,"date":"2016-09-02T09:09:00","date_gmt":"2016-09-02T14:09:00","guid":{"rendered":"https:\/\/kenscourses.com\/tc1019fall2016\/?guid=e626c3c68bea69e0a5797321c684d858"},"modified":"2016-09-02T09:11:52","modified_gmt":"2016-09-02T14:11:52","slug":"software-lifecycle-waterfall-method-2","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/software-lifecycle-waterfall-method-2\/","title":{"rendered":"Software Lifecycle – Waterfall Method"},"content":{"rendered":"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:
<\/a><\/td><\/tr>
Source<\/a><\/td><\/tr><\/tbody><\/table>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:<\/span>

<\/span>
<\/col><\/col><\/colgroup>
Advantages<\/span><\/div><\/td>
Disadvantages<\/span><\/div><\/td><\/tr>
  • Simple and easy<\/span><\/div><\/li>
  • Well-defined stages and deliverables<\/span><\/div><\/li>
  • Non-overlapping phases<\/span><\/div><\/li>
  • Good for small and well-understood projects.<\/span><\/div><\/li><\/ul><\/td>