4 ms·
I’m not sure why the above comment is being downvoted: I was reading The Practice of Cloud System Administration: Designing and Operating Large Distributed Sys
by ern 2y ago
I’m not sure why the above comment is being downvoted:
I was reading The Practice of Cloud System Administration: Designing and Operating Large Distributed Systems, and I came across this quote:
Royce’s 1970 paper, which is credited with “inventing” the model, actually identifies it so Royce can criticize it and suggest improvements. He wrote it is “risky and invites failure” because “design iterations are never confined to the successive step.” What Royce suggests as an alternative is similar to what we now call Agile. Sadly, multiple generations of software developers have had to suffer through waterfall projects thanks to people who, we can only assume, didn’t read the entire paper (Pfeiffer 2012) [p. 175].
https://www.jjinux.com/2015/07/the-waterfall-model-was-straw-man.html?m=1 https://www.jjinux.com/2015/07/the-waterfall-model-was-straw...
- cassianoleal 2y agoProbably because of exactly that. > Royce’s 1970 paper, which is credited with “inventing” the model, actually identifies it so Royce can criticize it and suggest improvements. That means people were doing waterfall then, just maybe not calling it so. > Sadly, multiple generations of software developers have had to suffer through waterfall projects That means even after it being given the name "waterfall", "multiple generations" kept using it. This is making observations, coming up with a model that fits the observations, giving it a name, and arguing against it. This is definitely not a strawman as GP or the author of the post you linked seem to think, which is why it's being downvoted (I didn't btw).
- luckydata 2y agoYou should try actually reading the paper.