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


Requirements identify the essential ques- tions that testing must answer to verify that the system provides the desired capabilities. Te systems engineering “V” model demonstrates the importance of requirements and their relationship to testing. Te V model can also be described as a pyramid, with require- ments development and testing forming the base for delivering an effective system. (See Figure 1.) Requirements also estab- lish the level of statistical confidence and precision required for adequate verifica- tion of capabilities.


KNOWING YOUR ENVIRONMENT Te test and evaluation community has observed five common challenges to well- developed requirements. Tese enemies of sound requirements have stymied program development and increased the scope of testing. All acquisition stakeholders at all echelons must understand the risks these enemies carry with them and consider those risks while developing and staffing system requirements. Requirements devel- opment is a team effort, so requirements developers are encouraged to involve all stakeholders early in the process.


The following examples are actual requirements taken from recent Army requirements documents. Te intent is to foster a practical understanding of the risks in requirements development and their potential impacts. In many cases, these examples were revised as part of the document staffing process.


CHALLENGE #1: NOT OPERATIONALLY FOCUSED A best practice is to ask, “Do I still want this system if it can’t meet this require- ment?” Answering “yes” to this question probably means that the requirement is not linked to the operational need the system is intended to fill and should be revised or


FIGURE 1


Requirement design


System design


Architecture design


Modular design


Acceptance test


System test


Integration test


Unit test


Coding


THE ‘V’ MODEL OF SYSTEM DEVELOPMENT


The V model summarizes the stages of systems engineering. Requirements definition is key to all subsequent system development efforts, including testing. (Image by U.S. Army Acquisition Support Center (USAASC) and www.am7s.com)


deleted. As an example of a requirement that is not operationally focused, consider this key performance parameter (KPP) for an artillery round.


KPP: Artillery round is effective against moving targets.


It is certainly possible to fire artillery rounds against a moving target. However, this is not the primary purpose or mission


for artillery rounds; rather, it is something usually saved for extreme circumstances. Tis requirement increases the risk that the system fails the requirement in test- ing, potentially delaying system fielding. Te requirement also drives lengthy and expensive testing since there are many things, such as target type or range to target, that could affect whether the round is effective against moving targets.


https://asc.ar my.mil


147


Verification phases


Validation phases


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