search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
COMMENTARY


into account system supportability, testing can demonstrate that the system is not supportable or sustainable.


Te result could be to significantly increase program cost, because the materiel developer will have to develop solutions to support- ability problems later in the engineering process. Te requirements development process must consider the maintenance and repair requirements and conditions to ensure that those capabilities exist when the system is fielded.


CONCLUSION Te primary purpose of test and evaluation is to provide decision- makers the essential information needed to determine a system’s readiness to proceed to the next program milestone or fielding. Requirements need to lay a foundation that supports achieving this goal.


Requirements that are not focused on the desired operational capability can delay system fielding and increase test costs. Tey can add unnecessary testing as the test and evaluation commu- nity tries to confirm that a system meets a requirement that is not critical to the system’s desired capability. Poorly developed requirements can also increase the scope of existing tests.


Operationally linked requirements ensure that acquisition stake- holders are asking the correct questions and are focusing efforts on providing the desired capability that will help our Soldiers on the battlefield.


For more information, go to www.atec.army.mil and www.benning.army.mil/MCoE/CDID.


JOSHUA R. BARKER is the Armored Brigade Combat Team Division chief at the U.S. Army Test and Evaluation Command, Aberdeen Proving Ground, Maryland. He has nearly 17 years’ experience designing and executing test and evaluation strategies for Army combat vehicles and networked systems. He has a B.S. in mathematics from Bethany College. He is an Army Acquisition Corps member and is Level III certified in test and evaluation.


DON SANDO is director of the Maneuver Capabilities Develop- ment and Integration Directorate, U.S. Army Maneuver Center of Excellence, Fort Benning, Georgia. He was selected to the Senior Executive Service in February 2008 after retiring from the Army as a colonel with 26 years of active service. He has an M.S. in operations research from the U.S. Air Force Institute of Tech- nology, an M.S. in strategic studies from the U.S. Army War College and a B.S. from the United States Military Academy at West Point. He is a member of the Association of the United States Army.


Requirements define the system design that is necessary to fill the identified operational need. … Requirements identify the essential questions that testing must answer to verify that the system provides the desired capabilities.


https://asc.ar my.mil


151


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  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176