Journal Article10.1046/J.1365-2575.1996.00100.X
Formalized systems development methodologies: a critical perspective
218
TL;DR: 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 ofmethodologies in practice.
read more
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.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Whatever happened to information systems ethics? Caught between the devil and the deep blue sea
Alison Adam
- 01 Jan 2004
TL;DR: This paper explored the development of information systems and computer ethics along separate trajectories over the 20 years since the first Manchester Conference, and pondered how things might have been and could be different.
3.4K
Does Agile work? - A quantitative analysis of agile project success
Pedro Serrador,Jeffrey K. Pinto +1 more
TL;DR: In this article, the authors examined the effect of Agile use in organizations on two dimensions of project success: efficiency and overall stakeholder satisfaction against organizational goals, and found that the quality of the vision/goals is a marginally significant moderator of this effect.
768
Continuous software engineering: A roadmap and agenda
Brian Fitzgerald,Klaas-Jan Stol +1 more
TL;DR: It is argued a similar continuity is required between business strategy and development, BizDev being the term the authors coin for this, and a number of continuous activities are identified which together are labelled as ‘Continuous * ’ (i.e. Continuous Star) which are presented as part of an overall roadmap for Continuous Software engineering.
723
Principles of software engineering management
TL;DR: This most recent book of Mr. Gilb's may be destined to become part of APL's folklore; if it were to adopt these methods in a similarly serious-minded vein the authors might easily discover a lot about ourselves and just possibly find a new way of getting their message into wider environments.
512
References
Educating the reflective practitioner
Donald A. Schön
- 01 Jan 1987
TL;DR: Building on the concepts of professional competence that he introduced in his classic The Reflective Practitioner, Schon offers an approach for educating professional in all areas that will prepare them to handle the complex and unpredictable problems of actual practice with confidence, skill, and care.
•Book
Software Engineering: A Practitioner's Approach
Roger S. Pressman
- 01 Jan 1982
TL;DR: Software Engineering A Practitioner's Approach recognizes the dramatic growth in the field of software engineering and emphasizes new and important methods and tools used in the industry.
10.4K
•Book
Software Engineering Economics
Barry Boehm
- 01 Jan 1981
TL;DR: In this article, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
6K
Software engineering economics
Barry Boehm
- 04 Oct 1993
TL;DR: In this paper, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
5.9K
No Silver Bullet Essence and Accidents of Software Engineering
TL;DR: In this article, the authors examine both the nature of the software problem and the properties of the bullets proposed, and show that there is no single development, in either technology or in management technique, that by itself promises even one order-of-magnitude improvement in productivity, in reliability, in simplicity.