| Recurring |
one_organization |
(a) The article mentions that Roscosmos, the Russian space agency, has suffered a series of mishaps and corruption scandals, including the recent software glitch that briefly threw the International Space Station out of control. This indicates that similar incidents have happened before within the same organization [117271].
(b) The article does not provide information about similar incidents happening at other organizations or with their products and services. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident on the International Space Station was attributed to a software glitch and a possible lapse in human attention. This indicates that the failure was due to contributing factors introduced during the system development or system updates [117271].
(b) The operation phase also played a role in the incident as the mishap occurred a few hours after docking, suggesting that the failure was influenced by the operation or misuse of the system [117271]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident on the International Space Station was within the system. Russian space officials attributed the mishap, which caused the entire space station to pitch out of its normal flight position, to a software glitch and a possible lapse in human attention [117271]. NASA's account of the incident also mentioned that engineers on the ground struggled to restore stability to the research satellite, indicating an internal system issue [117271]. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident on the International Space Station was attributed to a software glitch and a possible lapse in human attention, indicating that non-human actions played a role in the failure [117271]. NASA's account mentioned that engineers on the ground had to work to restore stability to the space station after the incident occurred, further emphasizing the non-human aspect of the failure. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident on the International Space Station was attributed to a software glitch and a possible lapse in human attention, indicating contributing factors that originated in software [117271]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the International Space Station (ISS) was non-malicious. Russian space officials attributed the mishap, which caused the entire space station to pitch out of its normal flight position, to a software glitch and a possible lapse in human attention [117271].
The incident was not caused by malicious intent but rather by technical issues and human error, highlighting the importance of robust software testing and human vigilance in critical systems like the ISS. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident on the International Space Station was attributed to a software glitch and a possible lapse in human attention, indicating that poor decisions or contributing factors introduced by poor decisions played a role in the mishap [117271]. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
The software failure incident on the International Space Station was attributed to a software glitch and a possible lapse in human attention, indicating a combination of factors related to development incompetence and accidental causes [117271]. The incident caused the entire space station to pitch out of its normal flight position, highlighting the critical impact of software failures in such high-stakes environments. |
| Duration |
temporary |
(a) The software failure incident on the International Space Station was temporary. It was caused by a software glitch and a possible lapse in human attention, which led to the space station briefly being thrown out of control after the Nauka module docked [117271]. The incident required engineers on the ground to work on restoring stability to the space station, and the crew members were declared to be never in immediate danger. |
| Behaviour |
crash, omission, other |
(a) crash: The software glitch caused the entire space station to pitch out of its normal flight position, indicating a failure due to the system losing state and not performing its intended functions [117271].
(b) omission: The software glitch and possible lapse in human attention were to blame for the mishap, suggesting a failure due to the system omitting to perform its intended functions at that instance [117271].
(c) timing: There is no specific mention of the failure being related to the system performing its intended functions but too late or too early.
(d) value: The articles do not indicate that the failure was due to the system performing its intended functions incorrectly.
(e) byzantine: The articles do not mention the failure being related to the system behaving erroneously with inconsistent responses and interactions.
(f) other: The software failure incident involved a software glitch that led to the space station going out of control, which could be categorized as a system behavior not falling into the specific options mentioned [117271]. |