Abstract
In general, software systems are relatively error free and support us doing our work. We could not live without these systems if we want to maintain the level of service, to which our customers have become accustomed. Most users, however, from time to time experience problems. It seems that despite all improvement efforts in areas such as specification, usability, testing and so on, software in use will cause problems, and we must find ways to live with this fact.
From a user perspective a system is either in the phase of implementation or operation. This paper focuses on the problems encountered by users when a system is in the operational phase and the development organisation is not available for problem resolution. The goal must be to support the users to get the highest possible benefit from the system. We must help users find the best way to live with the system.
This paper describes how to record problems and the basic principles to follow when these problems are processed. Examples are used to show how the potential benefit can be estimated. This forms the base for a decision on whether it is worth to cure the problem or not. It is common sense to provide support in this way, but experience shows that many organisations do it in an unstructured way and without recording the costs and benefits. Many provide support only because the cost of task failure, due to system problems, is high.
The paper then presents various measures to be taken to help the users do their work efficiently and get the best out of the system. It will be demonstrated how many of the problems can be cured through better information to the users, better work procedures, and system tailoring — without modifying source code.
The original version of this chapter was revised: The copyright line was incorrect. This has been corrected. The Erratum to this chapter is available at DOI: 10.1007/978-0-387-35404-0_19
Chapter PDF
References
Boris Beizer: Software Testing Techniques, Second Edition, Van Nostrand Reinhold, New York, 1990
Software on the Interface between Systems and Software Engineering, proceedings of the 21st International Conference On Software Engineering, May 1999, Los Angeles, California, USA.
IEEE Std. 1044–1993, IEEE Standard Classification for Software Anomalies, December 1993.
IEEE Std. 1074–1997, IEEE Standard for Developing Software Life Cycle Processes, December 1997.
Roger S. Pressman: Software Engineering — A Practitioner’s Approach, Fifth Edition, McGraw-Hill, Berkshire, 2000.
Niklaus Wirth: Software — Quality or Quantity, That is the Question, Proceedings of conference on Managing Software Quality Engineering Success, January 1997, Baden, Switzerland.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2001 IFIP International Federation for Information Processing
About this paper
Cite this paper
Jeppesen, K.J. (2001). How To Live With Software Problems. In: Ardis, M.A., Marcolin, B.L. (eds) Diffusing Software Product and Process Innovations. TDIT 2001. IFIP — The International Federation for Information Processing, vol 59. Springer, Boston, MA. https://doi.org/10.1007/978-0-387-35404-0_14
Download citation
DOI: https://doi.org/10.1007/978-0-387-35404-0_14
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4757-4975-5
Online ISBN: 978-0-387-35404-0
eBook Packages: Springer Book Archive