Waterfall Methodology
With its introduction in 1970 by Dr. Winston W. Royce, the waterfall is the most traditional methodology in the IT industry. It is a classic approach and a very popular version of the system development life cycle in software engineering. The goals are pre-defined for each development phase.
Waterfall Model: pros and cons
It is linear in nature with all projects progressing in stages. The completion of one stage precedes the other. This methodology is rigid because once a stage is complete, no reversible changes can be made based on new requirements.
Straightforward with no complexity in use. colombia mobile database It requires little or no experience.
Testing is simple because it’s based on the use cases defined in the technical specification.
Time-saving. In this methodology, the stages are processed and completed one at a time.
It is effective for small projects in cases where the requirements are well-defined.
There is easy management due to the rigid nature of the model with each stage having a separate review process.
There is a fixed deadline for each of the development stages.
Considerations in Waterfall Methodology
Maintenance type of projects does not apply to this method.
The software under production only becomes functional at the last stage of the cycle.
It is best used with only well-defined requirements available up-front.
There can be no edits or changes once a project advances to the testing stage.
It’s an ideal method for small and medium-sized projects but not long-term or research and development projects.
Not applicable for projects that tend to have modifications along the way.