Sign In
  • Question

    Is there a list of DoD mandated testing types? Our original plan had us executing very stringent "System Test" and "Interoperability Test" and "User Acceptance" etc. Anymore however, the lines of blurred together and our testing is becoming less effective as it is losing targeted objectives in favor of simply executing scripts. As such, I fear we are not efficiently bettering our software for production release.


    Answer

    QUESTION:  Is there a list of DoD mandated testing types? Our original plan had us executing very stringent "System Test" and "Interoperability Test" and "User Acceptance" etc.  Anymore however, the lines of blurred together and our testing is becoming less effective as it is losing targeted objectives in favor of simply executing scripts. As such, I fear we are not efficiently bettering our software for production release.

    ANSWER: DODI 5000.89, effective nov 19, 2020, "Purpose: In accordance with the authority in DoD Directive (DoDD) 5137.02 and DoDD 5141.02, this issuance establishes policy, assigns responsibilities, and provides procedures for test and evaluation

    (T&E) programs across five of the six pathways of the adaptive acquisition framework: urgent capability acquisition, middle tier of acquisition (MTA), major capability acquisition, software acquisition, and defense business systems (DBS). The sixth pathway, defense acquisition of services, does not require T&E policy and procedures." All the system tests are in this document, and the applicability of each test will be tailored into your program. Your system type and the functionality will determine if safety certs, cyber certification (most likely unless this is a standalone system), etc are required. You will notice that in the Software Acquisition Pathway the testing is in smaller batches and more continuous than a major program acquisition which focuses on large-scale DT or OT events. Automated testing is the preferred solution to become efficient and effective, and automated testing is fully in-line with DoD procedures found in the 5000.89 guide. However, there is significant investment required which is the only downfall. An the agile development principal is to prioritize working software over comprehensive documentation; instead of running the test scripts as a matter of internal policy, focus on ensuring every test is for the purpose of demonstrating working software.  As a side note, with a GOTS system there might be a set of tests required by the original developer and I would never recommend straying from their list.

    Open full Question Details
Chat with DAU Assistant
Bot Image