| Recurring |
one_organization |
(a) The software failure incident having happened again at one_organization:
The F-35 stealth fighter jet has faced a significant software failure incident related to potentially lethal bugs, ambiguous threat displays, limited ability to respond to threats, and the requirement for off-board sources to provide accurate coordinates for precision attack [40499].
(b) The software failure incident having happened again at multiple_organization:
There is no specific mention in the provided article about a similar software failure incident happening at other organizations or with their products and services. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase can be seen in the case of the F-35 stealth fighter jet. The Pentagon report revealed a massive list of potentially lethal bugs still facing the jet, including serious problems with the computer software such as issues in fusion, electronic warfare, and weapons employment resulting in ambiguous threat displays and limited ability to respond to threats [40499]. Additionally, the computerized maintenance management system incorrectly authorized older/inappropriate replacement parts, indicating a design flaw in the software [40499].
(b) In terms of software failure incidents related to the operation phase, the F-35 jet faced issues such as failing to detect if it had been flying too fast and randomly preventing user logins into its computerized control system [40499]. These operational failures point to contributing factors introduced by the operation or misuse of the system. |
| Boundary (Internal/External) |
within_system, outside_system |
(a) The software failure incident related to the F-35 stealth fighter jet includes issues within the system. The Pentagon report highlighted serious problems with the computer software, such as ambiguous threat displays, limited ability to respond to threats, and the need for off-board sources to provide accurate coordinates for precision attack [40499]. Additionally, the computerized maintenance management system incorrectly authorized older or inappropriate replacement parts, indicating internal software issues [40499].
(b) On the other hand, the incident also involved failures originating from outside the system. For example, the F-35 jet had issues with the ejector seat, where pilots under certain weight limits faced a high risk of injury or death upon ejection due to the seat's design flaw [40499]. This external factor, related to the physical design of the aircraft, contributed to the overall software failure incident. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident occurring due to non-human actions:
The F-35 stealth fighter jet faced a significant software issue related to the computer software, including problems in fusion, electronic warfare, and weapons employment, resulting in ambiguous threat displays and limited ability to respond to threats [40499]. Additionally, the computerized maintenance management system incorrectly authorized older or inappropriate replacement parts, indicating a software failure in the authorization process [40499].
(b) The software failure incident occurring due to human actions:
The delays and escalating costs of the F-35 project were attributed to various factors, including engine problems causing a jet to burst into flames during take-off, simple mistakes such as wingtip lights not meeting FAA standards, and tires unable to cope with landings [40499]. These issues highlight software failures introduced by human actions during the development and production phases of the aircraft. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident occurring due to hardware:
- The article mentions that the F-35 stealth fighter jet faced serious problems with the computer software, including issues in fusion, electronic warfare, and weapons employment resulting in ambiguous threat displays and limited ability to respond to threats [40499].
- It is reported that the F-35's computerized maintenance management system incorrectly authorizes older/inappropriate replacement parts, indicating a hardware-related issue with the system [40499].
(b) The software failure incident occurring due to software:
- The article highlights that the F-35's computer software fails to detect if it has been flying too fast and randomly prevents user logins into its computerized control system, indicating software-related failures [40499].
- Additionally, the article mentions that the F-35's software issues include problems with the smart parts system incorrectly authorizing replacement parts, further emphasizing software-related failures [40499]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the F-35 stealth fighter jet includes various issues that can be categorized as non-malicious failures:
1. The Pentagon report revealed a massive list of potentially lethal bugs facing the jet, including serious problems with the computer software affecting fusion, electronic warfare, and weapons employment [40499].
2. The computerized maintenance management system incorrectly authorizes older/inappropriate replacement parts, indicating a software flaw [40499].
3. The software fails to detect if it's been flying too fast and randomly prevents user logins into its computerized control system [40499].
These incidents point to software failures that were not introduced with malicious intent but rather as a result of flaws or errors in the system. |
| Intent (Poor/Accidental Decisions) |
poor_decisions, accidental_decisions |
(a) The software failure incident related to poor decisions can be inferred from the article. The F-35 stealth fighter jet faced significant challenges due to a massive list of potentially lethal bugs in its computer software, including issues in fusion, electronic warfare, and weapons employment resulting in ambiguous threat displays and limited ability to respond to threats [40499]. Additionally, the computerized maintenance management system incorrectly authorized older or inappropriate replacement parts, indicating poor decision-making in the software management process [40499].
(b) The software failure incident related to accidental decisions can be seen in the article as well. The F-35 jet's software failed to detect if it had been flying too fast and randomly prevented user logins into its computerized control system, indicating unintended decisions or mistakes in the software functionality [40499]. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
(a) The software failure incident related to development incompetence can be seen in the case of the F-35 stealth fighter jet. The Pentagon report revealed a massive list of potentially lethal bugs still facing the jet, including serious problems with the computer software such as ambiguous threat displays, limited ability to respond to threats, and incorrect authorization of replacement parts by the computerized maintenance management system [40499].
(b) The software failure incident related to accidental factors includes issues such as the software failing to detect if the aircraft has been flying too fast and randomly preventing user logins into its computerized control system. These issues could be considered accidental in nature, as they may have been unintended consequences of the software design or implementation [40499]. |
| Duration |
permanent |
(a) The software failure incident related to the F-35 stealth fighter jet seems to be more of a permanent nature. The article mentions significant ongoing challenges with the computer software, including issues in fusion, electronic warfare, and weapons employment resulting in ambiguous threat displays, limited ability to respond to threats, and a requirement for off-board sources to provide accurate coordinates for precision attack [40499]. Additionally, the computerized maintenance management system incorrectly authorizes older/inappropriate replacement parts, and it fails to detect if it's been flying too fast and randomly prevents user logins into its computerized control system [40499].
(b) The software failure incident does not seem to be temporary as the issues mentioned in the articles are fundamental and ongoing challenges rather than isolated incidents caused by specific circumstances. |
| Behaviour |
crash, omission, value, other |
(a) crash: The software failure incident related to a crash is evident in the article when it mentions that the F-35 stealth fighter jet experienced significant ongoing challenges, including serious problems with the computer software, resulting in ambiguous threat displays, limited ability to respond to threats, and a requirement for off-board sources to provide accurate coordinates for precision attack [40499].
(b) omission: The software failure incident related to omission is highlighted in the article when it states that the computerized maintenance management system incorrectly authorized older/inappropriate replacement parts, indicating a failure of the system to perform its intended function correctly [40499].
(d) value: The software failure incident related to performing its intended functions incorrectly is seen in the article when it mentions that the software failed to detect if it had been flying too fast and randomly prevented user logins into its computerized control system, indicating incorrect behavior [40499].
(f) other: The software failure incident also exhibited other behaviors such as the system failing to live up to expectations despite being the most expensive weapon in history, experiencing delays of over eight years, and being over budget by billions of dollars. Additionally, the software issues led to concerns about the safety of pilots, with restrictions on pilot weight due to potential risks during ejection [40499]. |