Enterprise DevSecOps Reference Design from the DoD CIO – A Summary Content referenced from: https://dodcio.defense.gov/Portals/0/Documents/DoD%20Enterprise%20DevSecOps%20Reference %20Design%20v1.0_Public%20Release sForDefense/raw/master/Meetup/2019/2019-10%20DO4D%20- %20DevSecOps%20Reference%20Design.pdfContainerized Software Factory Reference DesignSoftware Factory using Cloud DevSecOps Services Sidecar Container

difficulties.”Solutions to Accidental Difficulties • High-level languages • The most a high-level language can do is to furnish all the constructs the programmer imagines in the abstract program • Time-sharing are they remainders of our accidental difficulties?”Silver bullets? • Ada and other high-level language advances • Object-oriented programming • Artificial intelligence • Expert systems • “Automatic” content, automatic programming has always been a euphemism for programming with a higher-level language than was presently available to the programmer • In essence, it is the solution method, not the

Way: First, that we have locked ourselves into a frame of reference that is getting in our way as we try to become Agile. This frame of reference includes the notions of project, systems, application,

of a capability valuable to a user  High-level description of features  Written in user language, not technical jargon  Provide information to help teams estimate level of effort  Worded orders.  Work with the contracting office to develop standard Performance Work Statement (PWS) language and proposal evaluation criteria.  Use past performance and relevant experience as source selection

1. Application code & dependencies 2. Environment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc.

that this is something to be ashamed of or that they need to be controlled, learn to speak the language of the business, or start wearing jackets and ties.The CIO’s Place at the Table IT leadership