Soft systems and systems engineering: on the use of conceptual models in information system development

Abstract

Abstract. Many recent studies have shown that computer‐based systems continue to ‘fail’ at a number of different levels (Romtec, 1988; KPMG, 1990) and it is increasingly apparent (Maclaren et al., 1991) that the most serious failures of information technology (IT) lie in the continuing inability to address those concerns which are central to the successful achievement of individual, organizational and social goals. It is the contention of this paper that this failing is precisely because these are the areas which are ignored or inadequately treated by conventional system development methods.There is, of course, a vast body of literature concerned with the understanding of complex human activity systems. This literature often reflects a mass of contradictions at the epistemological and the ontological level about the behaviour of such systems and has also spawned numerous methods (and methodologies) which seek to guide the individual in making successful interventions into organizational situations (Rosenhead, 1989).Despite this multiplicity of viewpoints many writers have posited a dichotomy between so‐called 'soft and ‘hard’ approaches to problem situations and use this dichotomy to inform the choice of an appropriate problem‐solving methodology (Checkland, 1985). In this paper we characterize these two approaches as being concerned with either the purpose(s) of the human activity system (i.e. ‘doing the right thing’) or with the design of the efficient means of achieving such purpose(s) (i.e. ‘doing the thing right’).It is our belief that much of the literature and work in either area has not concerned itself with the issues of the other. Writers on ‘hard’ engineering methods often assume the question of purpose to be either straightforward (e.g. given in the project brief) or, paradoxically, too difficult (e.g. it is not our concern as mere systems analysts). Writers on ‘soft’ methods on the other hand rarely have anything to say about the design and implementation of well‐engineered computer‐based systems, giving the impression that this is a somewhat mundane activity better left to technical experts.This paper, therefore, attempts to set out a rationale for the bringing together of principles from both ‘hard’ engineering and ‘soft’ inquiry methods without doing epistemological damage to either. To illustrate our argument we concentrate on JSD (Jackson system development) as an example of system engineering (Cameron, 1983) and SSM (soft systems methodology) as an example of system inquiry (Checkland, 1981; Checkland & Scholes, 1990). Our general thesis, however, does not depend upon either of these two approaches per se but applies to the overall issue of bringing together insights from two apparently opposed epistemological positions in an effort better to harness the power of IT in pursuit of purposeful human activity.