Digital Engineering, Understanding the Policy and the Engineering in the Minimal Viable Product Approach

Abstract

This analysis endeavors to clarify the dichotomy of policy and engineering in DoD system acquisition. It considers the Software Acquisition Pathway (DoDI 5000.87) in current DoD policy, approaching that policy from the perspective of good systems engineering practice. It endeavors to provide a bit of guidance on the following: distinguishing policy from engineering – using DoDI 5000.97 Digital Engineering as an example, distinguishing engineering writ-large from software coding, and understanding the importance of working closely with the stakeholder through the minimal viable product (MVP) process. It defines through allusion two distinct flavors (definitions) of MVP – the flavor practiced in commercial industry by many large software companies (systems engineering goal development), and the flavor directed specifically by DoDI 5000.87 (policy). This analysis attempts to show how to use them respectively in the acquisition policy flow and in the systems engineering process.