Work

Editorial

Year: 1996
Type: editorial
Abstract: As authors of a book on information systems development methodologies* it is sometimes assumed that we (the Editors) are avid proponents of methodologies in all circumstances.This is far from the case and in general we advocate a contingent approach to their use.We recognise their strengths and potential benefits but are also acutely aware of their weaknesses and limitations.This issue of the Journal provides us with the opportunity to extend the debate on methodologies which has recently seen what has been described as a backlash against their use with two papers which present a critical view of methodologies.The first by Brian Fitzgerald suggests that the solution to the software crisis should not necessarily be seen to lie in increased control and the more widespread adoption of rigorous and formalized methodologies.The paper stresses the problems associated with methodologies.It suggests that the pressures in favour of formalized methodologies are more to do with literature bias than actual experience.Arguments against these formalized methodologies include a lack of agreement of what exactly constitutes a methodology, a lack of adequate conceptual and empirical foundations in the generalizations made in methodology design, the assumption that there is orderly rational processes associated with systems development which is reflected in methodologies but is not well based in experience, and the fact that methodologies do not cater for factors critical to successful development such as individual creativity, intuition and learning over time.The paper concludes by arguing that there may be alternatives to the use of formal methodologies when developing information systems.David Wastell's paper suggests that the widely championed methodologies, particularly structured approaches, encourage a rigid and mechanical approach to information systems development which inhibits creative thinking.Wastell argues that they are used as a social defence, rather than contributing to better information systems.A case study is used in the paper to highlight the potential debilitating effects of using an information systems methodology.Wastell suggests that such methodologies are more about the aesthetics of diagramming rather than the meaning behind the diagrams.In other words concentrating on `doing the thing right' instead of `doing the right things'.Again, the much heralded user contribution focuses on details of the diagramming rather than the broader issues, and in the case study this leads to user disenchantment and dismay at the quality of the work.The methodology is used to provide a relief against anxiety, but the end result is to increase it in the long run.The third paper by Arthur ter Hofstede and Denis Verhoef is also critical of aspects of information systems development, in particular, the current generation of CASE tools.They argue that these are too inflexible to provide the modelling support that is required.They consider the case shells which are heralded as being potentially the solution to this problem.More frequently, CASE tools are sold to support a particular information systems development 1
Language: Spanish
Open Access status: bronze
OpenAlex ID: W4253882322
Cites:
Cited by: 2
Related to: 9