FIELDING THE FUTURE
developers are able to continue to refine the design, often within the next sprint depending on the scope of changes.
Te process also provides the team with a framework to bake in safety, cyber and performance requirements throughout development by assessing vulnerabili- ties and code issues and correcting them before they become problematic. Auto- mation tooling and code generation have also contributed significantly to the Agile process.
SOFTWARE-DEFINED RADIOS EPITOMIZE AGILE Te Army’s tactical network moderniza- tion effort includes new software-defined radios, which are radios that can be configured to any frequency by way of software versus having set hardware components. PEO C3T’s Project Manager Tactical Radios team is using a modi- fied Agile-Scrum framework to develop a critical capability called Black Sails, which simplifies and speeds up the abil- ity for separate units or coalition forces to join one network to complete a common mission.
Traditionally, the process to connect all of the radios onto a common network would take anywhere from four to six hours because the units’ signal officers would have to manually configure each radio. Black Sails has shortened the time to 30-40 minutes by connecting software- defined radios to end-user devices via a network broadcast similar to Wi-Fi.
Like CPCE and the Advanced Field Artillery Tactical Data System, the Black Sails project incorporates Agile with sprints to help manage the development process. However, because Black Sails includes several applications managed across many programs—applications that must, in turn, be integrated into
multiple hardware platforms—the Black Sails development team added a parallel process called the integration chain. (See Figure 1, Page 86.)
PM Mission Command has released cost- effective, robust mission- command software more frequently to meet the threat, while maintaining the approved acquisition processes.
Using this process, the team is able to conduct two-week sprints while also performing integration testing, which provides them the opportunity to contin- uously identify and correct issues with integration as part of the entire develop- ment cycle.
CONCLUSION As part of its modernization effort, the Army continues to use Agile software development processes to design and deliver cutting-edge capabilities. Iterative, collaborative software development—with a quick cadence of small releases—ensures that the system will be relevant when fielding. With the exponential pace of technology, modernization can occur only if developers have the flexibility to insert the latest software into Soldier solutions. Agile development provides that flexibility.
For more information, go to http://
peoc3t.army.mil, or contact the PEO C3T Public Affairs Office at 443-395-6489 or
usarmy.APG.peo-c3t.mbx.pao-peoc3t@
mail.mil.
LT. COL. SHAWN CHU-QUINN is the Product Manager for PM MC’s Tactical Mission Command. She holds an M.P.A. in national security affairs from Troy University, an M.S. in modeling and simulation from the University of Central Florida and a B.S. in environmental science from Creighton University. She is Level III certified in program management and Level II certified in engineering.
RICHARD BOODHOO is the AFATDS 7.0 chief engineer under PM MC. He holds an M.S. in software engineering from Stevens Institute of Technology and a B.S. in computer science from Florida Polytech- nic University. He is Level III certified in production, quality and manufacturing and Level II certified in engineering.
GEORGE SENGER is a computer scientist serving as the software and services assistant product manager for PEO C3T’s Product Manager Waveforms and is the lead engi- neer for Project Black Sails. He holds an M.S. in computer science from Montclair State University and a B.A. in communica- tions from William Patterson College. He is Level III certified in engineering.
JEFFREY KUDERNA is the CPCE project lead for the Tactical Effects, Protection and Interactive Technologies Directorate, Weap- ons and Software Engineering Center of the U.S. Army Combat Capabilities Develop- ment Command Armaments Center. He is also lead systems integrator to the Product Manager Tactical Mission Command. He holds an M.S. in information systems and technology management from the University of Delaware and a B.S. in biomedical engi- neering from the University of Miami. He is Level III certified in engineering.
https://asc.ar my.mil
87
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
