Abstract
This paper has developed from the SoFEA project at The Open University which is studying the non-technical aspects of quality in software. This involves seeing the technical elements of software development as very much part of a wider context. The culture of an organization as a whole, particularly its management strategies, are regarded as driving and shaping the technology. A particular challenge for management we have observed is how to harmonize a skilled individualist (affectionately dubbed a ‘maverick’) and a quality management system. We explore the characteristics of an individualist programmer and discuss the options for managing such a person. Some of the experiences of a scientific organization are reported.
Similar content being viewed by others
References
R.M. Belbin.Management Teams. Heinemann, 1987.
British Computer Society/Department of Trade and Industry. TickIT making a better job of Software.Guide to Software Quality Management System Construction and Certification using EN29001. Department of Trade and Industry, London, February 1992, Issue 2.
BS 5882: Specification For A Total Quality Assurance Programme For Nuclear Installations. BSI, 1990
HMSO.Organizing For Safety: ACSNI Study Group On Human Factors, Third Report, 1994.
F.M. Hovenden, S. Yates, M. Woodman and H.C. Sharp. The use of ethnography with discourse analysis in the study of software quality management systems, inProceedings Software Quality Management Conference, Edinburgh, July 1994.
ISO 9001: Quality Systems: Model For Quality Assurance In Design, Development, Production, Installation And Servicing. ISO, 1987.
R.J. Maddison, P.C. Miller, and S.D. Walker. The answers service for the quality management of scientific software for the nuclear industry, inProceedings Software Quality Management Conference, Southampton, March 1993.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Hovenden, F.M., Walker, S.D., Sharp, H.C. et al. Building quality into scientific software. Software Qual J 5, 25–32 (1996). https://doi.org/10.1007/BF02420942
Received:
Issue Date:
DOI: https://doi.org/10.1007/BF02420942