| Recurring |
one_organization |
(a) The software failure incident related to the Beresheet spacecraft hitting the reset button is an example of a glitch that occurred within the same organization, SpaceIL. The incident caused the on-board computer to reset, leading to the cancellation of a maneuver [81422].
(b) The article does not mention any similar incidents happening at other organizations or with their products and services. |
| Phase (Design/Operation) |
design |
(a) The software failure incident related to the design phase can be seen in the article. The incident occurred when a glitch caused the on-board computer of the Beresheet spacecraft to reset, leading to the cancellation of a maneuver [81422]. This glitch was a contributing factor introduced during the system development phase of the spacecraft.
(b) The software failure incident related to the operation phase is not explicitly mentioned in the provided article. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident with the Beresheet spacecraft hitting the reset button was within the system. The glitch causing the on-board computer to reset and the subsequent cancellation of a maneuver were internal issues with the spacecraft's software [81422]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the Beresheet spacecraft was not explicitly attributed to non-human actions. The article mentions a glitch that caused the on-board computer to reset, leading to the cancellation of a maneuver. This glitch could be considered a contributing factor introduced without human participation [81422].
(b) The article does not provide information indicating that the software failure incident was due to contributing factors introduced by human actions. |
| Dimension (Hardware/Software) |
hardware |
(a) The software failure incident occurring due to hardware:
- The article mentions that the Beresheet spacecraft experienced a glitch that caused the on-board computer to reset, leading to the cancellation of a maneuver [81422].
- Additionally, there was an issue with the star tracker used for navigation being susceptible to blinding by the sun's rays [81422].
(b) The software failure incident occurring due to software:
- The article does not specifically mention any software-related issues as the cause of the failure. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident described in the article does not indicate any malicious intent. The incident was attributed to a glitch that caused the on-board computer to reset, leading to the cancellation of a maneuver. The article mentions that the spacecraft's systems were checked, and the canceled burn was successfully completed later. The focus was on addressing technical issues and overcoming challenges faced by the spacecraft during its mission to the moon [81422].
(b) The software failure incident can be categorized as non-malicious, as it was described as a glitch that caused the reset of the on-board computer, leading to the cancellation of a maneuver. The article highlights that such technical challenges are common for spacecraft in their initial stages of operation, referring to them as 'teething problems' that need to be overcome. The team involved in the mission worked to address the issues and ensure the spacecraft continued its journey towards the moon [81422]. |
| Intent (Poor/Accidental Decisions) |
unknown |
The software failure incident related to the Beresheet spacecraft hitting the reset button was not explicitly attributed to poor decisions or accidental decisions in the articles provided [81422]. The incident was described as a glitch that caused the on-board computer to reset, leading to the cancellation of a maneuver. The focus was more on addressing the technical challenges and overcoming the issues faced during the mission rather than attributing the failure to specific decision-making processes. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in the article seems to be more related to accidental factors rather than development incompetence. The glitch that caused the on-board computer to reset and the subsequent cancellation of a maneuver were described as "teething problems" that are quite normal for a spacecraft in its early days [81422]. The incident was not attributed to a lack of professional competence but rather to the challenges typically faced during the initial stages of a space mission. |
| Duration |
temporary |
The software failure incident described in the article is temporary. The incident involved a glitch that caused the on-board computer to reset, leading to the cancellation of a maneuver. However, after checking the spacecraft and finding all systems operational, the canceled burn was successfully completed on a later date. The article mentions that the spacecraft had some 'teething problems' in its first days, which were overcome, indicating that the software failure was temporary and not permanent [81422]. |
| Behaviour |
crash, other |
(a) crash: The software failure incident in the article can be categorized as a crash. The Beresheet spacecraft's on-board computer experienced a glitch that caused it to reset, leading to the cancellation of a planned maneuver [81422].
(b) omission: There is no specific mention of the software failure incident being related to the system omitting to perform its intended functions at an instance(s) in the provided article.
(c) timing: The software failure incident is not related to the system performing its intended functions correctly but too late or too early.
(d) value: The software failure incident is not related to the system performing its intended functions incorrectly.
(e) byzantine: The software failure incident is not related to the system behaving erroneously with inconsistent responses and interactions.
(f) other: The behavior of the software failure incident in the article can be categorized as a crash, where the system lost state and did not perform its intended functions as a result of a glitch [81422]. |