I was trying to tie the SRS to the "Big R" requirements, because tying your digital your transformation to an approved acquisition policy is a great way to obtain stakeholder buy-in.

Using the Software Acquisition Policy helps get you a "Big R" requirement that you can rally your team around and decompose into your product backlog. The Capability Needs Statement (CNS) inside DoD 5000.87 is defined as “Capability Needs Statements identify mission deficiencies, or enhancements to existing operational capabilities, features, interoperability needs, legacy, interfaces and other attributes required for new software intensive systems or upgrades to existing systems.”. These should be treated a "statements", only 1-3 pages long and how Senior Leaders should view the success of the project. Too often Senior Leaders get sucked into technology discussions when they should be focused on warfighter outcomes.