Thanks, Ilya, this is an excellent comparative summary of the requirements KA of the two SWEBOK Guides (I haven't seen the v4).

You mentioned "stakeholder requirements" both in this article and in your earlier article on the distorted term of "business requirements," pointing out that Joy Beatty and I don't use that IIBA term in our book. There are two reasons why I don't use it.

First, nearly all requirements come from some stakeholder (except perhaps derived requirements, as you point out), so a category called simply "stakeholder requirements" is too broad and undescriptive to be meaningful. It's like defining "business requirements" as "anything someone from the business tells us they want," which is definitely not what we mean when we say "business requirements."

Second, in my 3-level requirements model, which I originated in 1999 in the first edition of my Software Requirements book, I termed the second-level "user requirements." Joy and I extensively discussed whether we wanted to change that to "stakeholder requirements," as is used in the second level of the BABOK's model. We decided no. In that category I am specifically referring to requirements that describe things the user needs to be able to do with the solution. Hence the term user requirements.