| Recurring |
one_organization, multiple_organization |
(a) The software failure incident has happened again at ExamSoft, the software provider for the remote bar exam. In 2015, ExamSoft paid $2.1 million to settle a class action lawsuit related to delays in uploading essay responses during the July 2014 bar exam [118253].
(b) The software failure incident has happened again at multiple organizations as well. The article mentions that jurisdictions hired ExamSoft to deliver the remote bar exam, and some test takers experienced technical difficulties such as computer crashes or freezes during the exam. This indicates that similar incidents have occurred with ExamSoft's products and services across different organizations administering the bar exam [118253]. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase can be seen in the article where ExamSoft, the software company that provided the bar exam software, faced technical problems during the remote bar exam. Some test takers experienced their computers crashing or freezing during the exam, leading to disruptions and loss of exam time [118253].
(b) The software failure incident related to the operation phase is evident in the same article where examinees reported having to reboot their computers during the test sessions, resulting in a loss of exam time. Some were even locked out of the test for extended periods due to technical difficulties [118253]. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident during the remote bar exam was attributed to computer memory issues on certain user devices, as stated by ExamSoft initially [118253]. This indicates that the failure was within the system, specifically related to the software and its interaction with the users' devices. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the remote bar exam was attributed to computer memory issues on certain user devices, indicating a non-human action as the contributing factor [118253]. Additionally, ExamSoft, the software provider, mentioned that they are investigating the cause of the technical difficulties, suggesting that the issue was not intentionally caused by human actions [118253].
(b) The article does not provide specific information indicating that the software failure incident was due to contributing factors introduced by human actions. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident related to hardware:
- Some examinees experienced technical difficulties during the remote bar exam when their computers crashed or froze, leading to loss of exam time [118253].
- ExamSoft initially attributed the problems to computer memory on certain user devices, indicating a hardware-related issue [118253].
(b) The software failure incident related to software:
- The software provider ExamSoft was responsible for delivering the exam, and some examinees faced issues with the software during the test [118253].
- ExamSoft has a history of software-related issues during bar exams, as evidenced by a previous settlement in 2015 due to tech glitches in uploading essay responses [118253]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the remote bar exam appears to be non-malicious. The issues experienced by test-takers, such as computers crashing or freezing during the exam, were attributed to technical difficulties and computer memory problems [118253]. The software provider, ExamSoft, stated that they do not believe there is any merit to or basis for a lawsuit, indicating that the failure was not intentional but rather a result of technical issues [118253]. Additionally, the previous incident in 2014 where ExamSoft had to settle a class action lawsuit for delays in uploading essay responses during the bar exam was also non-malicious in nature, as it was a technical glitch affecting multiple test-takers in 43 states [118253]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident related to the remote bar exam appears to be more aligned with poor_decisions. The incident involved technical problems that impacted some examinees during the exam, leading to their computers crashing or freezing, causing them to lose exam time. This issue was attributed to computer memory problems on certain user devices by ExamSoft, the software provider for the exam. Additionally, ExamSoft had a history of similar issues in the past, as evidenced by a $2.1 million settlement in 2015 for delays in uploading essay responses during a previous bar exam [118253]. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
(a) The software failure incident related to development incompetence is evident in the article as ExamSoft, the software company responsible for delivering the bar exam, has faced similar issues in the past. In 2015, ExamSoft paid $2.1 million to settle a class action lawsuit over tech glitches during the July 2014 bar exam, where test takers encountered delays in uploading their essay responses [118253].
(b) The software failure incident related to accidental factors is also highlighted in the article. ExamSoft initially attributed the technical problems during the recent remote bar exam to computer memory issues on certain user devices, indicating that the failure was not intentional but rather accidental in nature [118253]. |
| Duration |
temporary |
The software failure incident related to the remote bar exam can be categorized as a temporary failure. Test takers experienced technical difficulties such as their computers crashing or freezing during portions of the licensing exam, leading to some examinees having to reboot their computers and losing exam time in the process [118253]. The software provider, ExamSoft, initially attributed the problems to computer memory on certain user devices and stated that they were investigating the cause of the technical difficulties [118253]. This indicates that the failure was temporary and not a permanent issue affecting all circumstances. |
| Behaviour |
crash, other |
(a) crash: The software failure incident in this case involved crashes where some examinees' computers crashed or froze during portions of the licensing exam, leading to loss of exam time [118253].
(b) omission: There is no specific mention of the software failure incident being related to omission in the articles.
(c) timing: The software failure incident did not involve timing issues where the system performed its intended functions but too late or too early.
(d) value: The software failure incident did not involve the system performing its intended functions incorrectly.
(e) byzantine: The software failure incident did not involve the system behaving erroneously with inconsistent responses and interactions.
(f) other: The software failure incident involved technical difficulties experienced by exam-takers, leading to some having to reboot their computers during test sessions and losing exam time in the process. Some were even locked out of the test for a half hour or more due to the software issues [118253]. |