System Requirements Review (SRR)

In legacy practices, a review held within the government to determine whether A-specs adequately assigned technical requirements to the various government entities that would over-see the contractors of a large project (which may, or may not, be part of a single government program).

In modern uses, an excuse to make it look as if we somehow can foresee all of the requirements that will ever be needed to develop any little ol’ piece of the puzzle by trotting out viewgraphs purporting to be the detailed design which, if already that mature, we don’t really need any requirements for1.

Footnotes
  1. But, perhaps, I wax sarcastic again. Today, we use SRR’s to assure ourselves that all of the correct requirements have been allocated down the specification tree. But that is what the up-the-tree PDR’s are supposed to do, so that that such issues are considered in context. Apparently, we no longer know what PDR is really for, either.[]