F35 fails to solve Pentagon software problems

In a report released by the Pentagon's Operational Test and Evaluation Office, Chief Tester Robert Behler makes critical and at least problematic judgment regarding the evolution and bugfixing procedure for the F35 system, whether it is acts from the on-board system as from the ALIS system. Indeed, according to him, the developers in charge of these missions do not manage to correct and develop programs without generating, in turn, a large number of malfunctions, this explaining the number of bugs identified in this program has changed little for several years, despite the efforts and the considerable funds allocated to it.

Two main reasons are identified by the OTEO to explain this. First of all, the deadlines given to correct and implement the new functionalities, in increments of 6 months, are considered too short to be able to assess their effects on the entire system, and lead to the discovery of these malfunctions directly in the operational units. . Secondly, the ambition of the program, and in particular the integration of the simulation technologies of the Joint Simulation Environment, adds significant complexity and captures a significant portion of development budgets, even though the core program is not stabilized.

The F35's embedded computer system is based on 8 million lines of code, 4 times more than that of the F22 raptor.

The rest of this article is for subscribers only

Full-access articles are available in the “ Free Items“. Subscribers have access to the full Analyses, OSINT and Synthesis articles. Articles in the Archives (more than 2 years old) are reserved for Premium subscribers.

From €6,50 per month – No time commitment.

Related posts