Couldn't disagree more. If it looks like a duck, and it quacks like a duck...
I've worked in waterfall shops. Sections I through V are very similar to what we aspired to do. Look, it's not like this knowledge is worthless. It's just that what is outlined in these sections is a very thorough but expensive ($$$ and labor) and time-consuming process that that when put into practice often insulates itself from the business problem at hand. Just because it looks good on paper does not mean it will look good when you start applying it to the real world with real people.
I'll say this: If you want to participate in an organization that is culturally waterfall and practices waterfall this certification will prove quite valuable. Anywhere else though, and you might give the impression you're not a good "culture fit" for the organization.
But "activities" are not "phases". You are always trying to get the requirements right, the difference is that some people get them while coding, and others before even start designing.
I've worked in waterfall shops. Sections I through V are very similar to what we aspired to do. Look, it's not like this knowledge is worthless. It's just that what is outlined in these sections is a very thorough but expensive ($$$ and labor) and time-consuming process that that when put into practice often insulates itself from the business problem at hand. Just because it looks good on paper does not mean it will look good when you start applying it to the real world with real people.
I'll say this: If you want to participate in an organization that is culturally waterfall and practices waterfall this certification will prove quite valuable. Anywhere else though, and you might give the impression you're not a good "culture fit" for the organization.