Opinion: F-35 Software Fixes Likely To Take Time
Lessons from JSF software glitches
Bill Sweetman
There are two levels of concern about the latest critical memo on the F-35 Joint Strike Fighter (JSF) from the Pentagon’s director of operational test and engineering (DOT&E), Michael Gilmore.
[Story here http://aviationweek.com/defense/testing-chief-warns-jsf-software-delays ]
The first is that it is time for the Defense Department to resolve the friction between the F-35 Joint Program Office (JPO) and DOT&E, which has now reached the status of public flaming. The second is the question of whether late and defective software is a feature, rather than a bug, of any defense system as complex as the JSF.
The JPO has responded in detail to the DOT&E’s report. It suggests that some of the problems are not as bad as Gilmore paints them, but that in some cases it is up to the customer whether to fix every bug. In the case of the interim Block 2B and 3i releases, that may not be a good use of time or money because they will not be around for long.
But there is an undercurrent of harsher criticism. A uniformed JPO manager retorted on the Defense News public Facebook page that the latest memo was “whining. Operational testing is a formality. Only the Kingdom of DOT&E cares—they have to feel important.”..
Essential JSF software runs on at least four platforms: the airplane; the Autonomic Logistics Information System (ALIS), which is supposed to manage maintenance and support; reprogramming laboratories, which develop the mission data file (MDF) software that allows fused sensors to identify threats and targets; and simulators used for training and mission rehearsal.
All are functionally interlinked: ALIS and training devices need to reflect the configuration of the aircraft hardware and software on the ramp. Simulators and the airplane run on updated MDFs. The latter connection becomes crucial as air forces move toward live, virtual, constructive training, where pilots fly against synthetic threats and targets, because the MDFs determine how those objects are detected and displayed. All have suffered delays, according to Gilmore’s reports.
There is no end-state to development. The goal is to update the software on a two-year cycle, so there will usually be two standards in service at any one time in the U.S., plus customized MDFs for export customers [emphasis added].
Much of the software must be validated to a life-or-death level. Aircraft-borne code changes will require some level of regression testing (to ensure they don’t disrupt flight-critical functions). The intelligence that allows the system to distinguish a missile launcher from the village market bus resides in the MDFs...
http://aviationweek.com/defense/opinion-f-35-software-fixes-likely-take-time