R0021/2026-03-25/Q005/SRC01/E01¶
NATO Software Engineering Conferences — aspirational use of "engineering"
URL: https://en.wikipedia.org/wiki/NATO_Software_Engineering_Conferences
Extract¶
The NATO Software Engineering Conferences were held in 1968 (Garmisch, Germany) and 1969 (Rome, Italy). International experts on computer software agreed on defining best practices for software grounded in the application of engineering.
The title "software engineering" was deemed deliberately provocative. It was accepted among the participants that "the name expressed a need rather than a reality."
The conferences addressed the "software crisis" — software systems getting larger, missing deadlines, going over budget, and being brittle to change. The term "software crisis" was coined by attendees at the 1968 conference.
The conferences played a major role in gaining general acceptance for the term "software engineering" and produced two reports defining how software should be developed.
Relevance to Hypotheses¶
| Hypothesis | Relationship | Strength |
|---|---|---|
| H1 | Supports | Documents the most famous case of aspirational engineering labeling |
| H2 | N/A | This is the known example; the question is whether others exist |
| H3 | Supports | Software engineering eventually formalized, but took decades |
Context¶
The NATO conferences are the most well-documented case of deliberately applying "engineering" to a discipline that lacked engineering methodology. The explicit acknowledgment that the label "expressed a need rather than a reality" is directly relevant to evaluating whether "prompt engineering" follows the same pattern.
Notes¶
Software engineering took approximately 30 years from the aspirational label (1968) to having mature formal methodologies (late 1990s-2000s with Agile, CMMI, etc.). Some argue it still does not fully meet the formal engineering definition.