A counter to this is "requirements change quickly, therefore the system needs to change quickly too." But the actual case is: most organizations don't really know how to do systems analysis. So this results in one of two scenarios: either the organization wastes a lot of time and money in the analysis phase struggling to do what they cannot, or they punt on requirements analysis altogether and wait for requirements to surface at implementation time. This is called "Agile" today, but was described by Milt in 1983: "do a superficial feasibility study, do some quick and dirty systems design, spend a lot of time in programming, install prematurely so you can irritate the users sooner, and then keep working on it till you get something accomplished."
PRIDE is like a textbook on how to build a system, from requirements analysis through design, implementation, and maintenance. It was the first methodology for doing so, and it transformed information systems from arcane art into a proven, repeatable science. It should be the industry standard, but is now at risk of being forgotten, largely due to programmers holding the industry hostage.
AI is taking programmers out of the equation. PRIDE is relevant again.