| Recurring |
one_organization |
(a) The software failure incident having happened again at one_organization:
- The article reports that Apple's self-driving car program experienced its very first reported autonomous collision on California roads [74866].
- This incident involved an Apple test vehicle in autonomous mode being rear-ended while preparing to merge onto a road [74866].
- The collision occurred when the Apple test vehicle was traveling less than 1 mph and was hit by a 2016 Nissan Leaf traveling at approximately 15 mph [74866].
- The incident resulted in damage to both vehicles, but no injuries were reported [74866].
(b) The software failure incident having happened again at multiple_organization:
- There is no information in the provided article indicating that a similar incident has happened at other organizations or with their products and services. |
| Phase (Design/Operation) |
operation |
(a) The software failure incident in the article does not seem to be related to a design phase issue. The incident was described as a rear-end collision involving Apple's self-driving car being hit by another vehicle while preparing to merge onto a road. The report filed by Apple suggested that the autonomous vehicle was barely moving at less than 1 mph, waiting for a safe gap to complete the merge when it was rear-ended by a 2016 Nissan Leaf traveling at approximately 15 mph. This incident does not indicate a failure due to contributing factors introduced by system development, system updates, or procedures to operate or maintain the system [74866].
(b) The software failure incident in the article appears to be more related to an operation phase issue. The incident occurred during the operation of Apple's self-driving car on the road. The collision happened while the autonomous vehicle was in autonomous mode, preparing to merge onto a road. The incident involved the operation of the self-driving car and the interaction with another vehicle on the road, resulting in a rear-end collision. This indicates a failure due to contributing factors introduced by the operation or misuse of the system [74866]. |
| Boundary (Internal/External) |
within_system, outside_system |
(a) The boundary of the software failure incident within the system is evident in this case. The incident involved Apple's self-driving car, which was in autonomous mode when it was rear-ended by another vehicle while preparing to merge onto a road. The report filed by Apple indicated that the Apple test vehicle was traveling at less than 1 mph and was waiting for a safe gap to complete the merge when it was hit by a 2016 Nissan Leaf traveling at approximately 15 mph. This indicates that the software failure incident occurred within the system of Apple's autonomous driving technology [74866]. |
| Nature (Human/Non-human) |
unknown |
(a) The software failure incident in this case was not attributed to non-human actions. The incident involved a rear-end collision where Apple's self-driving car, operating in autonomous mode, was hit by another vehicle while preparing to merge onto a road. The Apple test vehicle was reportedly traveling at less than 1 mph when it was rear-ended by a 2016 Nissan Leaf traveling at approximately 15 mph. Both vehicles sustained damage, but no injuries were reported. The incident was described as a collision between the autonomous vehicle and another vehicle, indicating a failure resulting from the interaction between the two vehicles rather than non-human actions [74866].
(b) The software failure incident was not directly linked to human actions either. The report filed by Apple suggested that the collision was not Apple's fault, indicating that the software or autonomous system in the Apple test vehicle was not the primary cause of the accident. The incident occurred while the Apple test vehicle was waiting for a safe gap to complete a merge, and it was rear-ended by another vehicle. The article did not mention any human error or actions contributing to the software failure incident [74866]. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident in the article does not seem to be related to hardware issues. The incident described involves a collision between Apple's self-driving car and another vehicle, with the Apple test vehicle being rear-ended while preparing to merge onto a road. The report filed by Apple suggests that the collision occurred when the Apple test vehicle, operating in autonomous mode, was traveling at less than 1 mph and was rear-ended by a 2016 Nissan Leaf traveling at approximately 15 mph. Both vehicles sustained damage, but no injuries were reported [74866].
(b) The software failure incident in the article is related to software factors. The incident involves Apple's self-driving car operating in autonomous mode when it was rear-ended by another vehicle. The report filed by Apple indicates that the Apple test vehicle was barely moving, waiting for a safe gap to complete the merge, when it was struck by the Nissan Leaf. This suggests that the software controlling the autonomous mode of the Apple test vehicle may have been a contributing factor to the collision [74866]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident in this case was non-malicious. The incident involved Apple's self-driving car being rear-ended by another vehicle while in autonomous mode, with Apple stating that their vehicle was barely moving at less than 1 mph and was preparing to merge onto a road when the collision occurred. Both vehicles sustained damage, but no injuries were reported, indicating that the failure was not due to malicious intent but rather an accidental collision [74866]. |
| Intent (Poor/Accidental Decisions) |
accidental_decisions |
(a) The intent of the software failure incident related to poor_decisions:
- The incident involved Apple's self-driving car being rear-ended by another vehicle while in autonomous mode.
- Apple's test vehicle was traveling less than 1 mph, waiting to merge onto a road when it was hit by a 2016 Nissan Leaf traveling at approximately 15 mph.
- The report filed by Apple suggested that it wasn't Apple's fault, indicating that the decision-making process or actions taken by Apple's autonomous system were not the cause of the collision [74866]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in the article does not indicate any development incompetence as the collision was described as not being Apple's fault. The incident was attributed to a rear-end collision where the Apple test vehicle was barely moving in autonomous mode and was hit by another vehicle [74866].
(b) The software failure incident in the article appears to be accidental. The report filed by Apple suggested that the collision was not Apple's fault and occurred when the Apple test vehicle was rear-ended by a 2016 Nissan Leaf while preparing to merge onto a road. Both vehicles sustained damage, but no injuries were reported [74866]. |
| Duration |
temporary |
The software failure incident described in the article is temporary. The incident involved Apple's self-driving car being rear-ended while in autonomous mode, indicating a specific circumstance where the failure occurred due to the interaction with another vehicle [74866]. |
| Behaviour |
crash |
(a) crash: The software failure incident in the article can be categorized as a crash. The Apple self-driving car was rear-ended while in autonomous mode, resulting in a collision. The system lost its state and was not able to perform its intended function of safely merging onto the road, leading to the accident [74866].
(b) omission: There is no indication in the article that the software failure incident was due to the system omitting to perform its intended functions at an instance(s) [74866].
(c) timing: The software failure incident was not related to the system performing its intended functions correctly but too late or too early [74866].
(d) value: The software failure incident was not due to the system performing its intended functions incorrectly [74866].
(e) byzantine: The software failure incident was not characterized by the system behaving erroneously with inconsistent responses and interactions [74866].
(f) other: The behavior of the software failure incident, not falling into the categories of crash, omission, timing, value, or byzantine, is that the system was involved in a collision due to being rear-ended while in autonomous mode, waiting to merge onto the road [74866]. |