EMERGING TECHNOLOGY AND MODERNIZING THE ARMY
THE SAFE ADVANTAGE
Rapid sof tware development with DevSecSafOps integrates safety into modern sof tware development practices.
by Franklin J. Marotta, Camille E. Houston and Melissa Reinard Steffen, Ph.D. S
oftware is at the heart of many warfighting platforms. To meet Army transformation initiatives, software must be capable of being rapidly modified and deployed. Te Department of Defense Instruction (DoDI) 5000.87,
“Operation of the Software Acquisition Pathway,” describes how modern software development practices, such as agile and devel- opment, security and operations, or DevSecOps, deliver products at a speed of relevance. However, these development processes do not directly consider safety and can result in unsafe outcomes.
In an Army where autonomous, artificially intelligent and robotic systems operate with minimal human input, the ability of the software to operate safely and to notify users of an unsafe outcome is even more critical. Development, security, safety and operations, or DevSecSafOps, is a new approach for integrating software safety concepts into the DevSecOps process.
Reminiscent to how ‘security’ was inserted into the development and operations, or DevOps, process to improve the cyber resil- ience and timeliness of software delivery, DevSecSafOps ensures software impacts to safety are characterized and mitigated during product development. Software is a source of military advantage, a shift to a DevSecSafOps process is vital to keep pace with rapid software fielding timelines.
EVOLUTION OF SOFTWARE DEVELOPMENT Software development practices have evolved significantly over time. Te Waterfall model of the 1980’s developed software through linear sequential phases of requirements definition, design, coding, testing and maintenance; a method best used for creating predictable and well-defined software products. One of the disadvantages of this model is that government software testing does not occur until development is complete, result- ing in product delivery delays. Te Waterfall model also lacks the flexibility and user engagement which is needed to keep up with the pace of change in the defense industry. As a result, Agile principles began to be incorporated into product devel- opment in the early 2000s. Agile actively engages the user and allows the requirements, or user stories, to be continually refined throughout product development. Since Agile delivers soft- ware in increments, the users can test and provide feedback on functionality and use during development. In the later 2000s, the DevOps software development method applied the Agile concepts of customer engagement during software development to the deployment and maintenance operations that follow prod- uct delivery. Te DevOps concept removes the barriers between the developers and the deployment teams, ensuring customer feedback is used to improve the product throughout its life cycle. During the 2010s, the expansion of network and cloud-based
https://asc.ar my.mil
33
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120
