THE IMPERATIVE


BENEFICIAL VISIT


Iyer paid a visit to a data center still under construction in South Korea, in March, to assess progress and problem areas in development of the center. (Photo by 8th Army Public Affairs Office)


working with Congress to find an endur- ing solution to the problem.


TEST AND EVALUATION FOR SOFTWARE Software that is embedded in weapon systems are required to go through extensive test and evaluation activities— developmental testing, independent operational testing, interoperability test- ing, Section 508 testing; and various certifications such as Army interoperabil- ity certification, before the software can be deployed into the weapon system plat- form. However, these activities follow a very waterfall approach and require a great deal of documentation to complete. Many of the test cases are duplicative and


repetitive, or non-value added. To deliver software in small increments we will need to reform the Army’s test and evaluation processes to become more agile.


Te only true measure of whether a soft- ware works as intended is to get it in the hands of real users early and often for real feedback. Using accredited development platforms and tools and a standard archi- tecture can ensure interoperability upfront, and keep the focus on delivering usable software to users. For tactical systems and deployments, leveraging modeling and simulation tools, virtual testbeds or even digital twins is how the Army can reduce the need for test and evaluation on phys- ical platforms. Te Army’s Joint Systems


Integration Laboratory is an example of how we must address testing and certifi- cations in the future.


CYBERSECURITY Cybersecurity for Army software contin- ues to be an afterthought as part of the system accreditation. System security plans too often focus on the risk manage- ment framework-driven waterfall process to accredit a system through authority to operate (ATO) rather than continually testing for cybersecurity vulnerabilities in the code during development. Cyber- security needs


to be an important


consideration in the development of the system architecture, and followed through with continuous testing such as static code


12


Army AL&T Magazine


Summer 2022


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  |  Page 121  |  Page 122