Well, it does mean what I think it means because language is descriptive, not prescriptive :) I will never forget sitting in a 4-8 hour meeting for a day revie

Well, it does mean what I think it means because language is descriptive, not prescriptive :) I will never forget sitting in a 4-8 hour meeting for a day reviewing our entire dependency tree, and whether or not SJ-BCOMKA-4.11 had a dependency on SJ-TARGET-4.32. Management moved our "productive percentage time" from 80% to 85% to make the schedule look good to upper management. The scars of "waterfall" run very very deep. Second, it's clear you need to reapply anything written 35+ years ago to modern sw development. For example, "operations" as a stage of sw development, whereas today we have devops vs SRE vs production engineering vs whatever. Things like cleanroom development, zero defect software, etc are completely under utilized by software shops today, because we price the cost of maintenance & bugs far far too low. Which is was also unfortunately missing from the waterfall paper compared to Capers Jones or others analysis that showed it's not just that you should have preceding steps to "coding" - the preceding steps (aka "analysis") remove defects from your final product far far faster.