No Silver Bullet—Essence and Accidents of Software Engineering.¶
Brooks, F. P. J. (1986). No Silver Bullet—Essence and Accidents of Software Engineering. Information Processing 86, 1069-1076.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Accidental Vs Essential Complexity
- The distinction was formalized in software engineering with the argument that no single advance would deliver an order-of-magnitude improvement, because the essential complexity — the conceptual structure of the problem itself — was already dominant and could not be eliminated by tooling.
This sourceFormalizes the essential/accidental complexity distinction and argues that, accidental complexity having been substantially attacked, the dominant essential complexity precludes any single advance delivering an order-of-magnitude productivity gain.
Supported in partVerified against the publisher's abstract
The abstract states Brooks's no-silver-bullet thesis (no single advance promises an order-of-magnitude gain) but does not state the essential-complexity-dominance or tooling-elimination clause.
“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.”
- The distinction was formalized in software engineering with the argument that no single advance would deliver an order-of-magnitude improvement, because the essential complexity — the conceptual structure of the problem itself — was already dominant and could not be eliminated by tooling.
Mechanisms¶
- Essential-Accidental Complexity Audit
- Its four-way scheme is a direct descendant of the essential-versus-accidental distinction that has organized thinking about software difficulty for decades.
This sourceThe audit's rubric operationalizes exactly that split, adding "mixed" and "unresolved" to handle the cases Brooks's binary leaves ambiguous.
- Its four-way scheme is a direct descendant of the essential-versus-accidental distinction that has organized thinking about software difficulty for decades.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 2 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:fd11a00e8617 · see in the full table