Think! Interactive Systems Need Safety Locks

This paper uses a simple analogy. A gun is designed to shoot bullets, but it is obvious that accidentally shooting is a danger one should avoid if at all possible. Thus guns have safety locks, which aim to protect users and bystanders. Interactive computer systems sometimes accidentally do bad things too, but something like "safety locks" are not often enough implemented to help protect user or bystanders from harm. Worse, user interfaces often behave quite unpredictably with erroneous input - rather than blocking errors and requiring the user to correct them. This is a bit like guns that misbehave. Computers and computers embedded in everyday devices are not always as dangerous as guns, although there are many cases where they can be as dangerous. Medical devices may give patients undetected overdoses. In-car entertainment devices, like radios, may, through their badly-designed user interfaces, cause a driver to have an accident. A slip in a spreadsheet may be the first step towards an organisation going bankrupt. And so on. The solution should include better design, including the concept of safety locks, that block some forms of user error.

[1]  Harold Thimbleby,et al.  Reducing number entry errors: solving a widespread, serious problem , 2010, Journal of The Royal Society Interface.

[2]  C. V. Van Way Patient safety. , 2005, JPEN. Journal of parenteral and enteral nutrition.

[3]  Kim J. Vicente,et al.  Patient Safety, Potential Adverse Drug Events, and Medical Device Design: A Human Factors Engineering Approach , 2001, J. Biomed. Informatics.

[4]  Alla Keselman,et al.  Attitudes toward medical device use errors and the prevention of adverse events. , 2007, Joint Commission journal on quality and patient safety.

[5]  S. Syed,et al.  Morphine overdose from error propagation on an acute pain service , 2006, Canadian journal of anaesthesia = Journal canadien d'anesthesie.

[6]  Harold W. Thimbleby,et al.  User interface design , 1990, ACM Press Frontier Series.

[7]  Miriam Leeser,et al.  Area and performance tradeoffs in floating-point divide and square-root implementations , 1996, CSUR.

[8]  LeeserMiriam,et al.  Area and performance tradeoffs in floating-point divide and square-root implementations , 1996 .