Thanks for your blog. I found it by Google alert.
Every time I see the phrase “Requirements management” I wonder why people are so excited about RM, RM tools and traceability. I know from my defence experience that RM is important, but I see very little excitement about the requirements themselves, that form the start/basis of RM. If these requirements are incomplete or inconsistent, then how will RM help us during the requirements analysis phase?

So, I would like put emphasis in the requirements themselves, and the analysis of these requirements, before we do any RM. Admitted, there is self-interest too, since I developed a tool Requirements Assistant (see my Website). The tool analyses 1) each requirement as a sentence, 2) each requirement as part of a paragraph, and 3) each requirement as part of the whole set.
The aim is to assess completeness, consistency, vagueness, ambiguity, etc early in the Lifecycle.
The tool was recently evaluated by NASA IVV and it is being used on their Orion and Juno programs.

Have fun!
Herman.