Software Engineering: An Idea Whose Time Has Come and Gone?writing

software-engineeringessayself-reflectionmethodology-critique
2009-01-01 · 3 min read · Edit on Pyrite

"Software Engineering: An Idea Whose Time Has Come and Gone?" (2009), published in ieee-computer-society's IEEE Software, is DeMarco's most significant single essay and one of the most discussed pieces of self-critical writing in the history of software development methodology. In it, DeMarco publicly recants his earlier faith in software engineering as a discipline capable of systematically improving software outcomes, questioning whether the decades of investment in the field he helped build actually delivered on its promises.

The recantation

The essay's core argument is a statement of doubt about the foundational premise of the structured-methods-era: that software development could be managed and improved through rigorous engineering discipline — defined processes, formal methods, measurement programs, and systematic controls. DeMarco had been a central figure in building that premise. structured-analysis-and-system-specification was a foundational text; controlling-software-projects was among the most rigorous attempts to put software project management on a measurement basis. The 2009 essay subjects that body of work to skeptical re-examination.

DeMarco notes that software projects continue to fail at roughly the rates they always have, that cost and schedule overruns remain endemic, and that the enormous methodological investment of the preceding decades has not produced the improvements that were promised or expected. His explanation is consistent with the argument he had been developing since peopleware: the problems of software development are primarily sociological and organizational, not technical and methodological. Applying engineering discipline to the wrong part of the problem cannot fix the right part.

The self-critical dimension

What makes the essay historically significant is not the critique itself — similar arguments had been made by others — but who is making it and what it cost him to make it. DeMarco had spent his career building the structured methods tradition. edward-yourdon, larry-constantine, and DeMarco were the intellectual architects of the structured analysis and design framework that defined software engineering methodology through the 1970s and 1980s. For DeMarco to question whether that tradition had delivered on its promises was an act of genuine intellectual honesty rather than the kind of contrarian posturing that is common in technology discourse.

The essay is not a wholesale rejection. DeMarco does not argue that engineering discipline is worthless, or that structured methods produced nothing of value. The argument is more precise: that the discipline focused on the tractable (process formalization, artifact standardization, measurement) at the expense of the intractable (organizational culture, working conditions, the human factors that actually dominate outcomes). The peopleware-thesis was always implicit in his work; the 2009 essay makes it the basis for evaluating the entire enterprise.

Relationship to the broader bibliography

The essay represents the reflective-era of DeMarco's work at its most concentrated. The trajectory from structured-analysis-and-system-specification (1978) to peopleware (1987) to slack (2001) to this essay (2009) is a coherent intellectual arc: from building the formal methodology tradition, to discovering its limits through empirical research, to developing an alternative organizational framework, to finally questioning the adequacy of the original project from the outside.

The ieee-recantation-essay event is the culmination of this arc. DeMarco did not leave the field — he continued to contribute through atlantic-systems-guild work and speaking — but the essay marked a kind of intellectual settling of accounts with his own earlier commitments.

The essay provoked substantial discussion in both the software engineering academic community and the practitioner community. Some readers found it a capitulation; others found it a belated acknowledgment of what the empirical evidence had long suggested. Its importance lies less in the novelty of its arguments than in the integrity of its authorship — a founder questioning the foundations.