of the waterfall developmental model comes from Dr. Winston W. Royce’s 1970 paper “Managing the Development of Large Software Systems,” in which he described the waterfall model as “risky” and noted that it “invites failure,” recom- mending an incremental model instead. At best, though,
incremental models
provide an opportunity for endless cycles of user evaluation and fixes based on an interpretation of user needs.
Agile software development often includes a user representative to provide that validation perspective in real time, but representation does not guarantee that the process owner and software developer understand each other, any more than a requirements document does.
SWAPPING ROLES Te gulf of expectation can be better bridged by exchanging the traditional roles of developer and user. Te more we create opportunities to see a prob- lem through the other’s perspective, the better our communication about require- ments and expectations.
Te user can become more involved in the development process, for both business systems and weapon systems, by evaluat- ing mock-ups and prototypes through user juries and Soldier feedback, as the Army has done successfully with its situational awareness and friendly force-tracking tool Joint Battle Command – Platform (JBC-P) and its network backbone, Warfighter Information Network – Tactical (WIN-T); and through the semiannual test and evaluation process known as the Network Integration Evalu- ation (NIE).
Te Army evolved JBC-P as the succes- sor to Joint Capabilities Release and Force XXI Battle Command Brigade and Below/Blue Force Tracking by
PROVIDING THE USER PERSPECTIVE Soldiers with the 3rd Armored Brigade Combat Team, 3rd Infantry Division evaluate upgrades to JBC-P, the Army’s next-generation situational awareness capability, during a user jury in August 2013 at Fort Benning, GA. Soldiers were involved early in the process of developing JBC-P, evalu- ating mock-ups and prototypes and providing feedback as the system evolved. (U.S. Army photo by Nancy Jones-Bonbrest, PEO C3T Public Affairs)
ALL SYSTEMS OPERATIONAL
Using a joystick similar to one found on a video game console, a Soldier remotely maneuvers equipment at the Expeditionary Base Camp during NIE 16.1, held in September 2015 at Fort Bliss, TX, and White Sands Missile Range, NM. NIEs give Soldiers the opportunity to use and critique emerging technology; feedback from the exercises has been used to mature or restructure some programs and to reallocate resources to other priorities. (U.S. Army photo by Vanessa Flores, Assistant Secretary of the Army for Acquisition, Logistics and Technology System of Systems Engi- neering and Integration Directorate Public Affairs)
ASC.ARMY.MIL
149
COMMENTARY
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
