THE SAFE ADVANTAGE
DevSecSafOps ensures that software safety documentation is updated, safety analysis is conducted and necessary test cases are developed and executed as the software is developed and released.
Te DevSecOps principle of test case automation is also a key element in DevSecSafOps. All safety-significant software testing cases within the test suite are tagged to be reviewed for their robustness by the developer’s software safety engineer and other stakeholders. As new requirements are implemented for a given software release, the automated safety-significant test suite is also updated. Safety-significant test cases that cannot be automated are executed at the system level. Software safety is considered throughout the operations phase through real-time monitoring to ensure ongoing safety assurance during operation. Safety-significant outcomes during operations are automatically collected, reported and analyzed for resolution.
STAKEHOLDER ENGAGEMENT Te successful implementation of a DevSecSafOps environment requires the engagement stakeholders beyond the software devel- opers and software safety engineers. Te user, the U.S. Army Test and Evaluation Command (ATEC) and the program manager also play important roles in software safety. Te user provides essential feedback on the software’s function, helping to identify potential issues and improvements. To ensure Soldiers can safely use the system, ATEC is tasked with developing safety release and safety confirmation documents. Program managers oversee the acquisition process, from development to fielding, ensuring the system meets its contractual requirements and adheres to Army, DOD and industry standards. To enable DevSecSafOps prin- ciples during software development, program managers should specify security standards, safety regulations, operational best practices and contractual responsibilities in their contracts. In doing so, they can ensure that vendors adhere to secure, safe and reliable development, testing and deployment practices for their software-intensive systems. By incorporating DevSecSafOps principles early in the development process, stakeholders can gain efficiencies, improve Soldier interactions, reduce programmatic risk and expedite fielding timelines.
CONCLUSION To maintain a competitive edge on the battlefield, the Army must be able to rapidly develop, upgrade and deploy software to weapons and warfighting systems. Ensuring software safety risks are identified and eliminated or mitigated early in develop- ment will ensure fielding timelines can be met. DevSecSafOps combines best practices of Agile and DevSecOps software devel- opment processes with procedures for software safety found in
36 Army AL&T Magazine Fall 2024
MIL-STD-882E, resulting in an efficient software development process that mitigates safety risk, ultimately delivering software at a speed of relevance.
For more information, go to
https://www.atec.army.mil/atc.
FRANKLIN J. MAROTTA is a senior mathematician for
software safety and artificial of Rochester.
intelligence within the
Modeling, Simulation and Software Test Division, assigned to the U.S. Army Aberdeen Test Center. He holds a B.A. in mathematics from the University
He is a DAWIA Certified Practitioner in test and evaluation.
CAMILLE E. HOUSTON is the director of the Virtual Test and Advanced Electronics Directorate assigned to the U.S. Army Aberdeen Test Center at Aberdeen Proving Ground, Maryland. She holds an M.S. in systems engineering from Johns Hopkins University and a B.S. in mechanical engineering from Lawrence Technological University. She is a member of the Army Acquisition Corps and is a DAWIA Certified Practitioner in test and evaluation.
MELISSA REINARD STEFFEN, PH.D., is the technical director of the U.S. Army Aberdeen Test Center at Aberdeen Proving Ground, Maryland. She holds a Ph.D. in analytical chemistry from the University of Delaware and a B.A. in chemistry from Franklin & Marshall College. She is a member of the Army Acquisition Corps and is a DAWIA Certified Practitioner in test and evaluation.
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
