Abstract
The information systems discipline appears not to recognise the possibility of failure and, consequently, makes little effort to gain from failure when it does occur. This is in contrast to other design disciplines, which not only allow for failure, but often improve their own practice by performing some sort of failure analysis.
Rather than ignoring the possibility of failure, information systems practitioners need to appreciate that an active study of failure can provide many benefits. These include avoiding the same mistakes, discovering errors in the design process, gaining insights that might have been impossible to obtain in any other way and preventing similar kinds of failures in related systems. In addition to this, the study of historical cases of information system designs can act as a valuable learning aid in its own right.
For the information systems discipline to achieve these benefits, however, changes are needed in design methodologies. New methodologies must be developed which not only allow for the possibility of failure, but are able to evolve as a result. In this way, the whole discipline will gradually improve because valuable experiences gained from failure will be captured through continually improving methodologies. Such an approach will not only improve information systems practice, and the quality of the artefacts that are constructed, but also contribute positively to the professional standing of the discipline.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Alter, S. (1992) Why Persist with DSS when the Real Issue is Improving Decision Making? in Decision Support Systems: Experiences and Expectations. Proceedings of IFIP TC8/WG8.3, NH.
Bayes K (1976) About Design, Design Council Publications
Beynon Davies (1995) Information Systems ‘Failure’: The case of the London Ambulance Service’s Computer Aided Dispatch project, European Journal of Information Systems, Vol.4, pp 171–184
Bignell V and Fortune J (1984) Understanding systems failures, Manchester University Press
Boehm W (1989) Software Risk Management, IEEE Computer Society Press
Brinkkemper S (1996) Method Engineering: Engineering of Information Systems Development Methods and Tools, Proceedings of the Fifth International Conference on Information Systems Development, Gdasnk, Poland, September 24–26
Dahlbom B and Mathiassen L (1995), Computers In Context, Blackwell
Eaves D (1992) The Prospects of a Formal Discipline of Software Engineering, Proceeding s of the Third Conference on Information Systems, Wollongong, October 5–8
Feynman R (1988) What Do You Care What Other People Think?, Norton.
Jacky J (1990) Risks in Medical Electronics. Communications of the ACM, Vol. 33, p 138.
Leveson N (1995) Safeware System Safety and Computers, Addison-Wesley
Littlewood B and Strigini L (1995) The Risks of Software, In D Johnson and H Nissenbaum, (eds) Computers, Ethics & Social Values, Prentice Hall, New Jersey
Lyytinen and Hirschheim R (1987), Information Systems Failure–A Survey and Classification of the Empirical Literature, Oxford Surveys in Information Technology, Vol 4
McNeill P (1990) Research Methods; 2nd. ed., Routledges, London.
Norman (1990) Commentary: Human error and the design of computer systems, Communications of the ACM, Vol. 33, Number 1
Peterson I (1995)Fatal Defect, Times Books
Petroski H ( 1992) To Engineer is Human, Vintage Books
Petroski H (1994) Design Paradigms: Case Histories of Error And Judgement in Engineering, Cambridge University Press
Poulymenakou A and Holmes A (1996) A Contingency Framework for the Investigation of Information Systems Failure, European Journal of Information Systems, Vol. 5, pp34–46
Pressman R (1992) Software Engineering. A Practitioner’s Approach, McGraw-Hill
Ryan R and Spayner K (1996), A History of Aerospace Problems, Their Solutions, Their Lessons, Internet Document
Sauer, C (1993), Why Information Systems Fail: A Case Study Approach, Alfred Waller Ltd
Schlager N (1994) When Technology Fails, Gale Research Inc
Schon, D (1986). The Reflective Practitioner, Basic Books
Spector and Gifford ( 1986), A Computer Science Perspective of Bridge Design, Communications of the ACM, Vol. 29, Number 4
Svensson N (1981) Introduction To Engineering Design, NSW University Press Ltd.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1997 Springer Science+Business Media New York
About this chapter
Cite this chapter
Linger, H., Baker, J., Eaves, D. (1997). Failure Analysis in Information Systems Design. In: Wojtkowski, W.G., Wojtkowski, W., Wrycza, S., Zupančič, J. (eds) Systems Development Methods for the Next Century. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-5915-3_9
Download citation
DOI: https://doi.org/10.1007/978-1-4615-5915-3_9
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4613-7712-2
Online ISBN: 978-1-4615-5915-3
eBook Packages: Springer Book Archive