2 ms·
Waterfall means at least two things. I'll assume for my answer that it means only one of two things which I'll discuss. All development process models assume t
by Jtsummers 9y ago
Waterfall means at least two things. I'll assume for my answer that it means only one of two things which I'll discuss.
All development process models assume the following tasks:
Requirements collection
Analysis
Design
Development
Testing
Deployment
After the first iteration, you move to maintenance. The only difference for maintenance is that "requirements collection" is more focused on collecting problem reports and change requests. Most of the requirements are already established.
Waterfall:
One meaning, the original and literally the worst thing ever, is that each of those activities is completed essentially in whole before the next and without feedback from the successor activities. The only feedback is when you get to maintenance and collect PRs/CRs from the customer and start the whole thing again.
The practical versions introduce some feedback loops but typically only up one level at a time. So test obviously feeds back to development which feeds back to design, etc. The problem here is that this is still a very slow process.
The problem with waterfall (the practiced version) beyond the poor feedback loops is also the time delays involved. Your analysis board which decides which PRs/CRs to work on may only meet every 6 months. So the average PR will sit in a queue for 3 months before it's even considered for work. And the results of the analysis board may not make it to the developers for another 3 months so the average PR won't be worked on for 6 months. And because many PRs are collected and started at once, integration testing typically waits until they're all done. So it could be a year or two before a full integrated build is produced and an issue discovered which forces you back to the design phase to fix a critical issue.
And, while the developers and testers are doing their thing another analysis board meeting happens and introduces more PRs. By the time a product gets released it's often 1-3 years behind what the customer actually wants or needs.
Waterfall only works if you have trivial projects, or projects with very clearly defined scopes and requirements that are being planned on the order of years or even decades anyways. This isn't most software.