Incident: BlackBerry Storm 2 Buttons and Camera Failure Incident

Published Date: 2010-03-04

Postmortem Analysis
Timeline 1. The software failure incident with the BlackBerry Storm 2 occurred when the updated Storm was announced back in October of the previous year [1304]. 2. Published on 2010-03-04 08:00:00+00:00. 3. The software failure incident with the BlackBerry Storm 2 likely occurred in October 2009.
System 1. BlackBerry Storm 2 buttons at the base of the screen 2. BlackBerry Storm 2 camera application
Responsible Organization 1. Research In Motion - The software failure incident with the BlackBerry Storm 2, including issues with the buttons and camera crashing the phone, can be attributed to Research In Motion, the company behind the BlackBerry devices [1304].
Impacted Organization 1. Users of the BlackBerry Storm 2 were impacted by the software failure incident reported in Article 1304. The issues with the buttons not working properly and the camera causing the phone to crash would have directly affected the users of the device [1304].
Software Causes 1. The software cause of the failure incident with the BlackBerry Storm 2 was related to the malfunctioning of the four buttons at the base of the screen, which sometimes did not work properly, requiring repeated poking or tapping to function [1304]. 2. Another software cause was the issue with the camera application, where starting up the camera would crash the phone, leading to arbitrary reboots, especially after a few days of not using the camera [1304].
Non-software Causes 1. Hardware issues with the four buttons at the base of the screen not working properly [1304]. 2. Hardware issue with the camera causing the phone to crash and reboot when starting the camera application [1304].
Impacts 1. The software failure incident with the BlackBerry Storm 2 resulted in the four buttons at the base of the screen sometimes not working, particularly the buttons used to make and end calls, causing inconvenience and frustration for users [1304]. 2. Another impact was the issue with the camera application causing the phone to crash and reboot when starting up the camera, which occurred after a few days of not using the camera, disrupting the user experience and potentially leading to data loss or missed photo opportunities [1304].
Preventions 1. Conducting thorough and rigorous testing before releasing the software could have potentially prevented the software failure incident. This includes comprehensive testing of all functionalities, including the buttons and camera features, to identify and address any issues prior to launch [1304]. 2. Implementing a more robust quality assurance process that includes user feedback and beta testing could have helped in identifying and resolving the flaws in the software before it reached the end-users [1304]. 3. Regular software updates and patches to address known issues and improve the overall performance and stability of the software could have mitigated the reported problems with the BlackBerry Storm 2 [1304]. 4. Collaborating with users and actively listening to their feedback regarding the software's performance and issues could have provided valuable insights for Research In Motion to proactively address and prevent such software failures in the future [1304].
Fixes 1. Implementing a software update or patch specifically targeting the issues with the four buttons at the base of the screen and the camera application could potentially fix the software failure incident [1304]. 2. Conducting a thorough analysis of the software code related to the button functionality and camera application to identify and rectify any underlying bugs or defects causing the failures [1304]. 3. Enhancing the quality assurance and testing processes during the development of future software updates to ensure that such critical issues with buttons and camera functionality are identified and resolved before the release of the product [1304].
References 1. Personal experience of the user with the BlackBerry Storm and Storm 2 [1304]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident related to the BlackBerry Storm 2 occurred within the same organization, Research In Motion (RIM). The article mentions that the original BlackBerry Storm was widely panned for its shortcomings, and the Storm 2 also had its own set of flaws. The specific issues mentioned include the four buttons at the base of the screen not working properly and the camera causing the phone to crash and reboot when starting up. These problems were experienced by the user who had been using both the original Storm and the Storm 2, indicating a recurrence of software failure within the same organization [1304].
Phase (Design/Operation) design, operation (a) The software failure incident related to the design phase is evident in the article. The BlackBerry Storm 2 experienced flaws in its design, particularly with the four buttons at the base of the screen. The buttons sometimes did not work properly, causing issues such as the inability to make or end calls. This design flaw was persistent and not easily resolved, even temporarily, by rebooting the phone. Additionally, the camera application would crash the phone, leading to arbitrary reboots, indicating a design issue with the camera functionality [1304]. (b) The software failure incident related to the operation phase is also highlighted in the article. The problems with the buttons not working properly and the camera causing the phone to crash were issues that occurred during the operation of the BlackBerry Storm 2. These operational failures were experienced by the user during regular use of the phone, such as making calls or trying to use the camera application. The user's experience with these operational failures indicates issues introduced during the operation or use of the system [1304].
Boundary (Internal/External) within_system The software failure incident reported in Article 1304 includes issues both within the system and outside the system: (a) within_system: The article mentions internal issues within the BlackBerry Storm 2 software, such as the persistent problem with the four buttons at the base of the screen not working properly, causing inconvenience for the user. Additionally, the problem with the camera causing the phone to crash when starting up is another internal software issue mentioned in the article [1304]. (b) outside_system: While the article primarily focuses on internal software issues, it does not provide explicit information about any external factors contributing to the software failure incident. Therefore, there is no clear indication of external factors causing the reported software failures in this specific case.
Nature (Human/Non-human) non-human_actions (a) The software failure incident related to non-human actions in this case includes the persistent problems with the buttons at the base of the screen and the camera on the BlackBerry Storm 2. The article mentions that the buttons sometimes don't work, requiring repeated poking or tapping in a precise location to make them function. Additionally, starting up the camera can cause the phone to crash and reboot, especially after a few days of not using the camera. These issues are described as persistent problems that occur without any direct human intervention, indicating a failure related to non-human actions [1304]. (b) The software failure incident related to human actions is not explicitly mentioned in the article. There is no indication that the issues with the buttons or the camera on the BlackBerry Storm 2 are caused by human actions or errors. The problems seem to be inherent to the device or software design rather than being introduced by human actions [1304].
Dimension (Hardware/Software) hardware, software (a) The software failure incident related to hardware: - The article mentions issues with the four buttons at the base of the screen on the BlackBerry Storm 2, indicating a hardware-related problem where the buttons sometimes don't work properly [1304]. (b) The software failure incident related to software: - The article highlights a persistent problem with the camera on the BlackBerry Storm 2, where starting up the camera application causes the phone to crash and reboot, indicating a software-related issue [1304].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident described in Article 1304 does not indicate any malicious intent behind the issues faced with the BlackBerry Storm 2. The problems mentioned, such as the non-functioning buttons at the base of the screen and the camera causing the phone to crash, appear to be technical flaws or defects in the device rather than intentional actions to harm the system. The user's frustration with the phone's performance suggests a non-malicious software failure incident [1304].
Intent (Poor/Accidental Decisions) unknown The software failure incident described in Article 1304 does not explicitly point to either poor decisions or accidental decisions as the intent behind the failure. The issues mentioned, such as the malfunctioning buttons and the camera causing the phone to crash, seem to be related to technical flaws or defects in the BlackBerry Storm 2 rather than decisions made during the development or design process. Therefore, the specific intent behind the software failure incident in this case is unknown.
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident related to development incompetence is evident in the article. The BlackBerry Storm 2 was criticized for having flaws such as the four buttons at the base of the screen not working properly, with the user experiencing persistent issues with these buttons, especially when making or ending calls. The problem was not easily fixed, and rebooting the phone only provided a temporary solution. Additionally, the camera application would cause the phone to crash and reboot, indicating a lack of professional competence in ensuring the stability and functionality of the camera feature [1304]. (b) The software failure incident related to accidental factors is also present in the article. The issues with the buttons and the camera on the BlackBerry Storm 2 seem to have occurred unintentionally rather than as a deliberate design choice. The user mentions that the problems with the buttons and the camera were persistent and not easily resolved, indicating that these issues were accidental rather than intentional [1304].
Duration temporary (a) The software failure incident described in the article is more of a temporary nature. The article mentions that the problem with the buttons at the base of the screen and the issue with the camera causing the phone to crash are persistent problems but are only fixed temporarily by rebooting the phone. The article states, "And, in my experience, the problem is only fixed temporarily by rebooting the phone" and "This typically happens after a few days of not using the camera" [1304].
Behaviour crash, value, other (a) crash: The software failure incident related to the BlackBerry Storm 2 involves a crash. Specifically, starting up the camera causes the phone to crash, leading to an arbitrary reboot. This crash occurs after a few days of not using the camera, indicating a failure due to the system losing state and not performing its intended function [1304]. (b) omission: The article does not mention any specific instances of the system omitting to perform its intended functions at an instance(s). (c) timing: The article does not describe any failures related to the system performing its intended functions correctly but too late or too early. (d) value: The software failure incident does involve a failure due to the system performing its intended functions incorrectly. For example, the four buttons at the base of the screen sometimes do not work as expected, requiring repeated poking or tapping in a precise location to make or end a call. This indicates a failure in the system's performance [1304]. (e) byzantine: The article does not mention any behaviors of the software failure incident related to the system behaving erroneously with inconsistent responses and interactions. (f) other: The other behavior related to the software failure incident is the temporary fix by rebooting the phone. The problem with the buttons not working is only temporarily resolved by rebooting the phone, which is not considered an acceptable solution as the "fix" is fleeting, indicating a unique behavior in response to the failure [1304].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence no_consequence (a) death: There is no mention of any deaths resulting from the software failure incident in the provided article [1304].
Domain information (a) The failed system in the article is related to the information industry as it discusses the flaws and issues with the BlackBerry Storm 2 phone, which is a device primarily used for communication, accessing information, and utilizing various applications like Yahoo Messenger and Google Maps [1304].

Sources

Back to List