| Recurring |
one_organization |
(a) The software failure incident related to the draining of a section of the River Avon due to a fault with a sluice gate has happened before with the same organization. Boat owners who became stranded criticized the Environment Agency for not acting soon enough and mentioned that the problem had happened before [104834].
(b) The software failure incident related to the sudden drop in water levels on the River Avon in Bath due to a fault in the software operating a vertical sluice gate has not been explicitly mentioned to have occurred at multiple organizations in the articles provided. |
| Phase (Design/Operation) |
design |
(a) The software failure incident in the article was related to the design phase. The incident occurred due to a fault in the software that operates a vertical sluice gate, causing it to open suddenly, which led to the water levels plunging on a stretch of the River Avon in Bath [104834]. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident, which caused the water level to drop in the River Avon, was attributed to a fault in the software that operates a vertical sluice gate. The fault within the software caused the gate to open suddenly, leading to the unplanned drainage of the river section [104834]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in this case was attributed to a fault in the software that operates a vertical sluice gate, causing it to open suddenly. This indicates a non-human action as the contributing factor to the failure [104834].
(b) The article does not provide information suggesting that the software failure incident was due to contributing factors introduced by human actions. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident occurred due to a fault in the software that operates a vertical sluice gate, causing it to open suddenly. This fault led to the water level drop in the River Avon in Bath, impacting a boat tour company and causing financial losses [104834].
(b) The software failure incident was specifically attributed to a fault in the software that controls the operation of the sluice gate. This software fault resulted in the sudden opening of the gate, leading to the unintended draining of the river section and subsequent financial implications for the boat tour company [104834]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident in this case was non-malicious. The incident was attributed to a fault in the software that operates a vertical sluice gate, causing it to open suddenly, leading to a drop in water levels on the River Avon in Bath [104834]. The Environment Agency acknowledged the fault and expressed regret for the distress caused by the incident, indicating that it was not a deliberate act to harm the system. |
| Intent (Poor/Accidental Decisions) |
accidental_decisions |
(a) The software failure incident in this case was not due to poor decisions but rather an accidental decision or mistake. The incident occurred due to a fault in the software that operates a vertical sluice gate, causing it to open suddenly, leading to the draining of a section of the River Avon [Article 104834]. The Environment Agency admitted that they "could have done better" and that the situation was "distressing," indicating that the failure was not a result of intentional poor decisions but rather an unintended mistake. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in this case was not explicitly attributed to development incompetence. The article mentions that the fault with the software operating the vertical sluice gate caused it to open suddenly, leading to the drop in water levels on the River Avon in Bath. However, there is no indication that this fault was due to a lack of professional competence by humans or the development organization involved.
(b) The software failure incident was described as accidental in nature. The article states that the drop in water levels on the River Avon was caused by a fault in the software that operates the vertical sluice gate, leading to the unplanned draining of the river section. This indicates that the incident was accidental rather than intentional. |
| Duration |
temporary |
(a) The software failure incident in this case was temporary. The article mentions that the fault in the software that operates the vertical sluice gate caused it to open suddenly, leading to a drop in water levels on the River Avon in Bath. The Environment Agency planned to slowly raise the water levels to rectify the situation, indicating that the incident was not permanent but rather a temporary issue caused by the software fault [104834]. |
| Behaviour |
value |
(a) crash: The software failure incident in the article was not described as a crash where the system loses state and does not perform any of its intended functions [104834].
(b) omission: The software failure incident in the article was not described as a failure due to the system omitting to perform its intended functions at an instance(s) [104834].
(c) timing: The software failure incident in the article was not described as a failure due to the system performing its intended functions correctly, but too late or too early [104834].
(d) value: The software failure incident in the article was described as a failure due to the system performing its intended functions incorrectly. The fault in the software that operates a vertical sluice gate caused it to open suddenly, leading to a drop in water levels on the River Avon [104834].
(e) byzantine: The software failure incident in the article was not described as a failure due to the system behaving erroneously with inconsistent responses and interactions [104834].
(f) other: The software failure incident in the article was not described with any other specific behavior not covered by the options provided [104834]. |