Recurring |
one_organization |
(a) The software failure incident related to the Chevrolet Corvette ZR1's SDM fault preventing airbag deployment happened within the same organization, Chevrolet. The incident was discovered during a media event hosted by Chevrolet at Road Atlanta and subsequently replicated at the automaker's Milford Proving Ground in Michigan [72793].
(b) There is no information in the provided article indicating that a similar software failure incident has happened at other organizations or with their products and services. |
Phase (Design/Operation) |
design |
(a) The software failure incident in the Chevrolet Corvette ZR1 was related to the design phase. The article mentions that the car's "Sensing Diagnostic Module" (SDM) might suffer a fault during intense track driving, leading to a situation where the airbags might not deploy in an accident. This issue was discovered during a media event and subsequently replicated in trials at the automaker's proving ground. Chevrolet developed new software and applied it on the production line to address this design-related fault [Article 72793].
(b) The software failure incident was not related to the operation phase or misuse of the system. |
Boundary (Internal/External) |
within_system |
(a) The software failure incident related to the Chevrolet Corvette ZR1's airbag deployment issue was within the system. The fault in the "Sensing Diagnostic Module" (SDM) was triggered by the intense track driving conditions the car was subjected to, causing the SDM to go into a fault mode and potentially preventing the airbags from deploying in an accident [Article 72793]. This indicates that the failure originated from within the system itself due to the specific operational conditions the car was designed to perform under. |
Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the Chevrolet Corvette ZR1 was due to non-human actions. The fault in the "Sensing Diagnostic Module" (SDM) occurred during intense track driving conditions, specifically under extremely hard braking and sustained acceleration events under certain track conditions. This fault mode in the SDM could prevent the airbags from deploying in an accident, indicating a failure introduced without human participation [72793]. |
Dimension (Hardware/Software) |
hardware |
(a) The software failure incident in the Chevrolet Corvette ZR1 was due to a hardware issue. The article mentions that the "Sensing Diagnostic Module" (SDM) in the car might suffer a fault during intense track driving, which could prevent the airbags from deploying in an accident. This fault in the SDM is a hardware issue that originates in the car's onboard electronics [72793]. |
Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident described in the article is non-malicious. The failure was due to the intense performance of the Chevrolet Corvette ZR1 during track driving, causing the "Sensing Diagnostic Module" (SDM) to suffer a fault, which could prevent the airbags from deploying in an accident. Chevrolet identified the issue during a media event and subsequent trials, leading to the development of new software and a recall to address the safety concern [72793]. |
Intent (Poor/Accidental Decisions) |
unknown |
(a) The software failure incident related to the Chevrolet Corvette ZR1 was not due to poor decisions but rather due to the intense performance of the car overwhelming its onboard electronics. The fault in the "Sensing Diagnostic Module" (SDM) was triggered during intense track driving, specifically under extremely hard braking and sustained acceleration events under certain track conditions. This was not a result of poor decisions but rather a consequence of the extreme capabilities of the vehicle exceeding the software's limits [72793].
(b) The software failure incident was also not due to accidental decisions but rather a result of the car's performance exceeding the capabilities of the onboard electronics. The fault in the SDM was discovered during a media event at Road Atlanta and subsequently replicated during trials at the automaker's Milford Proving Ground in Michigan. The issue was not caused by accidental decisions but rather by the extreme nature of the driving conditions the Corvette ZR1 was subjected to [72793]. |
Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in the Chevrolet Corvette ZR1 was not due to development incompetence. The issue was identified during intense track driving and was specifically related to the Sensing Diagnostic Module (SDM) going into a fault mode under certain track conditions, which could prevent the airbags from deploying in an accident. Chevrolet addressed the issue by developing new software and applying it on the production line to recalibrate the module for more aggressive driving conditions [72793].
(b) The software failure incident in the Chevrolet Corvette ZR1 can be categorized as accidental. The fault in the SDM that could prevent airbag deployment was discovered during track driving events and replicated during trials at the automaker's testing grounds. It was not a result of intentional actions but rather an unintended consequence of the extreme driving conditions the car was subjected to during testing [72793]. |
Duration |
temporary |
The software failure incident related to the Chevrolet Corvette ZR1's SDM fault causing potential airbag deployment issues can be categorized as a temporary failure. The article mentions that the fault in the Sensing Diagnostic Module (SDM) occurs specifically during intense track driving conditions, such as "extremely hard braking and sustained acceleration events under certain track conditions" [Article 72793]. This indicates that the software failure is triggered by certain circumstances (intense track driving) rather than being a permanent issue affecting the system under all circumstances. |
Behaviour |
crash, value, other |
(a) crash: The software failure incident in the Chevrolet Corvette ZR1 was related to a fault in the "Sensing Diagnostic Module" (SDM) that could prevent the airbags from deploying in an accident. The SDM could go into a fault mode during intense track driving, leading to a situation where the airbags don't function. This can be considered a crash behavior as the system fails to perform its intended function of deploying airbags in the event of an accident [72793].
(b) omission: The software failure incident in the Corvette ZR1 was not specifically described as an omission where the system completely omits to perform its intended functions at an instance(s) [72793].
(c) timing: The timing of the software failure incident was not highlighted as a specific issue where the system performed its intended functions correctly, but too late or too early [72793].
(d) value: The software failure incident in the Corvette ZR1 can be considered a value behavior as the system was performing its intended function of monitoring the vehicle's status, but it was doing so incorrectly due to the fault in the SDM, leading to the airbags potentially not deploying when needed [72793].
(e) byzantine: The software failure incident in the Corvette ZR1 was not described as exhibiting a byzantine behavior where the system behaves erroneously with inconsistent responses and interactions [72793].
(f) other: The other behavior exhibited by the software failure incident in the Corvette ZR1 could be classified as a fault in the system's monitoring and response mechanism under extreme driving conditions, leading to a critical safety issue related to airbag deployment [72793]. |