Software Crisis Inquiry
An example of software failure was the one that occurred at FirstEnergy Corp. It was the Alarm and Event Processing Routine (AEPR) error which occurred on August 14, 2003. The AEPR is a major software programme that enables operatives to see and hear signs that show the progression on their field of work.
FirstEnergy Corp is a company that generates, transmits and is also involved with the distribution of energy power in the U.S. Thus, when the alarm system ceased from functioning, the operatives could not be in a position to take precautionary steps. This malfunction led to a blackout engulfing a huge portion of the Northeast U.S corridor and some portions of Canada. The cause of the blackot is attributed to a periodic trigger on the software that was disconnected so as to have a manual test on the network. Unfortunately, the engineer who had disconnected forgot to engage again the periodic trigger and went for lunch.
The cautionary measures could not be performed because a number of companies don’t have knowledge pertaining the electric systems that are out of their direct management.
The AEPR failure could have been cause by the FirstEnergy not using decent dynamic mapping and data distribution devices (Dan). The AEPR error could also be contributed by the lack of the FirstEnergy’s personnel having knowledge out of their immediate fields. Also, from another perception, it could have resulted from unsecure internet connections to the Supervisory Control and Data Acquisition (SCADA).
To cushion FirstEnergy Corp against such incidents in the future, it should install IT systems that detect intrusion-bearing in mind that a terror group, Al Qaeda, claimed responsibility- which can are compatible to the systems of SCADA. Companies such as FirstEnergy should train their personnel tasks that are out of their immediate field. (Stephen) Lastly, professional should be sued for their professional negligence (such as the engineer who forgot to reengage the periodic trigger and went for lunch.

Work cited
Dan, Verton. ComputerWorld. 20 November 2003. 14 October 2011 <http://www.computerworld.com/s/article/87400/Software_failure_cited_in_August_blackout_investigation>.
Stephen, Flowers. Software failure, management failure: amazing stories and cautionary tales. New Jersey: Wiley, 2009.