{"id":37171,"date":"2016-09-04T11:03:00","date_gmt":"2016-09-04T16:03:00","guid":{"rendered":"http:\/\/kenscourses.com\/tc1019fall2016\/?guid=2e8fc8a7002c0bc5d18586a17556a872"},"modified":"2016-09-04T11:03:21","modified_gmt":"2016-09-04T16:03:21","slug":"waterfall-method-2","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/waterfall-method-2\/","title":{"rendered":"Waterfall method"},"content":{"rendered":"Waterfall methodology is one of the first Software Development Processes, it was firsts used in hardware but now it has moved to software.

The steps of this methodology are followed in order one after another after checking that the previous steps are completed. The steps are:
  1. System and software requirements<\/b>: captured in a product requirements document.<\/li>
  2. Analysis<\/b>: resulting in models, schema, and business rules.<\/li>
  3. Design<\/b>: resulting in the software architecture.<\/li>
  4. Coding: the development<\/b>, proving, and integration of software<\/li>
  5. Testing<\/b>: It consists on debugging.<\/li>
  6. Operations: the maintenance<\/b>. <\/li><\/ol>Imagine a waterfall with different levels, here is an ilustration:

    <\/a><\/div>
    Now imagine that each level is a step and the development course is the water. It can only flow in one direction, passing through each level until it reaches the end that is the maintenance.

    I think that watefall methodolgy is one of the simplest one because it follows the normal software lifecycle. You think about the desgin, implement it, test it and then do the maintenace. The good part of the waterfall methodogy is that it takes it time to do well on each steps. Contrary to other methodogies that focus only on the developing, waterfall methodology cares about what is done before the coding because thats the plan and documentation you are going to follow. 

    Now enjoy the music:

    <\/div>
    <\/div>
    <\/div>