Down the Waterfall
Borrowed from the manufacturing and construction industry, the Waterfall Model of software development was described in 1970 by Winston Royce[3] as a series of stages for building software—but on the next page he said it wouldn’t work. Apparently, no one ever read that far.
Once the dominant methodology for building software, the Waterfall Model is simple in concept, providing these seven distinct steps to be followed in this order:
- Requirements
-
Information is gathered from subject matter experts and prospective users to create a requirements document. This is a written set of instructions that tells us what features we’re supposed ...
Get Beyond Legacy Code now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
