Formalized systems development methodologies: a critical perspective

Abstract. Systems development issues occupy a position of central importance in the information systems field and much has been prescribed in the quest for successful systems development. However, given the well‐documented ‘software crisis’, success is far from guaranteed for systems development projects. Many researchers see the solution to the software crisis in terms of increased control and the more widespread adoption of rigorous and formalized system development methodologies. This paper presents some arguments and pressures which support the use of methodologies and some evidence of the literature bias which favours methodologies is provided. However the problems associated with the use of methodologies have not perhaps received as much attention in previous research. This paper identifies a number of arguments and pressures which question the value of methodologies, and reports the results of a field study which investigated the role of methodologies in practice. The critical perspective adopted throughout shows that, contrary to the predominant view in literature, the assumption that increased adoption of methodologies addresses the problems inherent in systems development is by no means proven.

[1]  Edsger W. Dijkstra,et al.  The humble programmer , 1972, CACM.

[2]  William M. Taggart,et al.  A Survey of Information Requirements Analysis Techniques , 1977, CSUR.

[3]  William J. Raduchel.  Managing software development , 1978, SOEN.

[4]  Richard J. Boland,et al.  Control, causality and information system requirements , 1979 .

[5]  Thomas A. Standish,et al.  Initial thoughts on rapid prototyping techniques , 1982, Rapid Prototyping.

[6]  Robert Balzer,et al.  On the inevitable intertwining of specification and implementation , 1982, CACM.

[7]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[8]  Gary W. Dickson,et al.  Problem solving for effective systems analysis: an experimental exploration , 1983, CACM.

[9]  Mel A. Colter.  A Comparative Examinati on of Systems Analysis Techniques , 1984, ICIS.

[10]  István Kiss,et al.  Future Methodology Based on Past Assumptions , 1984 .

[11]  M. Lynne Markus,et al.  Rituals in Information System Design , 1984, MIS Q..

[12]  Justus D. Naumann,et al.  Empirical investigation of systems development practices and results , 1984, Inf. Manag..

[13]  Janis A. Bubenko,et al.  Information System Methodologies - A Research View , 1986, Information Systems Design Methodologies: Improving the Practice.

[14]  Peter Checkland,et al.  Systems theory and information systems , 1986, Trends in Information Systems.

[15]  Atul Prakash,et al.  Programming in the large , 1986, IEEE Transactions on Software Engineering.

[16]  D. Schoen.  Educating the reflective practitioner , 1987 .

[17]  Merle P. Martin.  Designing systems for change , 1987 .

[18]  Itzhak Shemer,et al.  Systems analysis: a systemic analysis of a conceptual model , 1987, CACM.

[19]  John W Verity.  The oops revolution , 1987 .

[20]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[21]  Jahangir Karimi,et al.  A Framework for Comparing Information Engineering Methods , 1988, MIS Q..

[22]  Trevor Wood-Harper,et al.  Information Systems Development: A Tool Kit is not Enough , 1988, Computer/law journal.

[23]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[24]  Ed Downs,et al.  Structured systems analysis and design method , 1988 .

[25]  Ronald K. Stamper.  Analysing the cultural impact of a system , 1988 .

[26]  Tom DeMarco,et al.  Software development: state of the art vs. state of the practice , 1989, ICSE '89.

[27]  Simon Holloway,et al.  Methodology handbook for information managers , 1989 .

[28]  E. J. Chikofsky.  How to Lose Productivity with Productivity Tools , 1990 .

[29]  Rudy Hirschheim,et al.  Symbolism and Information Systems Development: Myth, Metaphor and Magic , 1991, Inf. Syst. Res..

[30]  Terry Bollinger,et al.  A critical look at software capability evaluations , 1991, IEEE Software.

[31]  Raymond T. Yeh.  System Development as a Wicked Problem , 1991, Int. J. Softw. Eng. Knowl. Eng..

[32]  Watts S. Humphrey,et al.  Software process improvement at Hughes Aircraft , 1991, IEEE Software.

[33]  Sachidanandam Sakthivel.  Methodological requirements for information systems development , 1992, J. Inf. Technol..

[34]  Susan Folkes,et al.  Accelerated systems development , 1992, BCS practitioner series.

[35]  Richard Baskerville,et al.  Systems Without Method: The Impact of New Technologies on Information Systems Development Projects , 1992, The Impact of Computer Supported Technologies in Information Systems Development.

[36]  Christiane Floyd,et al.  Outline of a Paradigm Change in Software Engineering , 1993 .

[37]  Donald Hough.  Rapid Delivery: An Evolutionary Approach for Application Development , 1993, IBM Syst. J..

[38]  Jorgen P. Bansler,et al.  A reappraisal of structured analysis: design in an organizational context , 1993, TOIS.

[39]  D. Wastell,et al.  The behavioral dynamics of information system development: A stress perspective , 1993 .

[40]  Prashant Palvia,et al.  A field examination of system life cycle techniques and methodologies , 1993, Inf. Manag..

[41]  Brian Fitzgerald.  The systems development dilemma: Whether to adopt formalized systems development methodologies or not? , 1994, ECIS.

[42]  Erik Stolterman,et al.  The 'transfer of rationality': Acceptability, adaptability and transparency of methods , 1994, ECIS.

[43]  Joscha Bach,et al.  The Immaturity of the CMM , 1994 .

[44]  Jorgen P. Bansler,et al.  Information systems development with generic systems , 1994, ECIS.