Who is responsible when software 'bugs' result in disaster?

Criterion B: IT background of the issue

The definition of software bug according to  is; an error or defect in software or hardware that causes a program to malfunction. According to folklore, the first bug was an actual bug. Discovered in 1945 at Harvard, a moth trapped between two electrical relays of the Mark II Aiken Relay calculator caused the whole system to shut down.

During the past few years it seems as though more and more bugs are being created either intentionally or accidentally. There are few laws protecting us from software bugs and few standards groups, all we the consumers can do is return the product and demand better. Despite many efforts from various companies set up to deal with and identify bugs and faulty software, there has not been much improvement software bugs are as common as colds. The likely reason why these bugs are so common that they do not test the software appropriately. Because they know that they can get away with it and that most people are more interested in features than stability. It is not too much to ask for both, but until we the consumers do something about it nothing will happen.        

In the past, computer ‘bugs’ have resulted in dire consequences because the only computers being used where expert systems, due to the fact that they were so expensive, un-versatile and large, few people owned them. So obviously, if they were only used for large projects and things went wrong, the consequences were dire. This has been minimized and software companies should follow the same example with their common software.

        

Criterion C: Analysing the impact of the issue

Software bugs have not only commonly annoyed but ruined and ended the lives of millions. Whenever a software bug is known and causes a malfunction, the user will understandably get very frustrated. Because they may have lost important work, lost ideas and had their time as well as the time of their companies wasted.

        Environmentally when bugs affect the printing process paper is wasted which damages the environment. Economically money is wasted through paper, having to buy new software, paying repairmen to fix the problem e.t.c. The affects of software bugs are endless; for example if a country is dealing with another and a bug changes exchanged data or allows unauthorised persons to view/alter the data it can result in not only feuds but wars.

        When expert systems are used their consequences are much more dire, resulting in not only damage but also losses of lives and huge losses in money. This makes society doubt the ability of this technology, resulting in a delay in the development of this relatively new method.

                

Criterion D: Solutions to problems arising from the issue

There already are and have been for a while solutions to software bugs;  are one of many companies providing fixes for many fault software. Other companies simply identify the problems in an attempt to warn people such as . Microsoft themselves are constantly providing fixes or “updates” as they prefer to call them for their windows versions, windows xp has a function that allows the user to send the error report.

A solution to this problem wont be anything technical, it will be a mild revolution. People will have to demand more, refuse to buy anything less than perfect, complain at the slightest problem and demand a free fix. The software companies will then have to compete with each other, to provide not only the ongoing latest features but also the best reliability. This would be effective, only if the consumers will be strong and do this, but the fact is that they need these programs for their business and life and cant work without them.

        Another solution would be to have a standards group, like there is with many electronics and cars. The software will have to pass certain strict regulations and requirements and if they don’t; they go back to the manufacturer to be repaired. This is another effective solution but the problem being seeking funds and implementing this standards group.

        Primarily, the radical “revolution” idea could be adopted, through protests, advertising and spreading the word because it is true that people don’t really know that they can get better quality merchandise. But if this had little or no effect, then the standards group would be implemented, a tax could be required which the companies paid to have their own products tested or they could be sent the bill directly for each testing. Either solution is effective, but the ‘revolution’ idea would probably be cheaper and more easily implemented.

Criterion E: Selecting and using sources

• Mark Minasi: “The software conspiracy”

10/6/02

 http://,

(12/3/02)

• Neil Gross, Marcia Stepanek, John Carey and Otis Port: “Software hell (int’l edition)        

                6/12/99

                

                (5/2/02)

• Mark Kuharich: “WHAT, ME WORRK2K?”

(5/2/02)

• Robert Lemos: “Group to set bug reporting standards”

22/2/02

(12/3/02)

• Staff: “Software bugs leave Microsoft legally vulnerable”

1/7/02

4/10/02