Traditional requirements documentation for software-intensive military systems (e.g., command and control; intelligence, surveillance, reconnaissance, and targeting; and information operations) are insufficient, especially when the usual method of requirements decomposition and analysis takes years. The new Department of Defense (DoD) Software Acquisition Pathway, thankfully, affords most new software systems a ‘pass’ on the traditional requirements definition process (defined through the Joint Capabilities Integration and Development System), possibly accelerating this process. If their weapons are any indication, U.S. adversaries can outpace the DoD’s ability to design, develop, and field software applications. Although these new policies allow for rapid prototyping and acquisition, and software developers are extremely willing to embrace industry best practices, many DoD acquisition program offices are reluctant to change their culture.