Where the waterfall methodology is used for stable, less complex projects with well-defined, stable requirements, management completes each phase before the next begins, from a requirements phase where stakeholders define the project through design, development, testing and implementation to maintenance, accepting its ease of use, earlier identification of coding issues and measurable status against the difficulty and cost of returning to earlier phases, the time to produce a product and the limits on stakeholder change.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.