Progress Toward an Engineering Discipline of Software
summary
Argues that software has gained codified techniques—statics and strength of materials analogs arrive around 1700–1900 for bridges; bridge design now uses mandated state DOT software for spans 18 to 200 feet—but software still lacks consistent public-assurance practices. Cites concrete failures: Toyota model years 2002–2010 throttle faults, settlement >$1.5B, watchdog failures and cyclomatic complexity in the three digits with 10,000 global variables; 2014 US data shows 783 breaches exposing ≥85 million records. Calls for searchable, task‑specific codified knowledge and scaled engineering where consequences demand it.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:41What is "engineering"?
- 3:38Characteristics of engineering
- 7:39Craft of bridges
- 10:20Ironbridge at Coalbrookdale, 1779
- 11:09Dee Bridge disaster, 1847
- 12:00Business of bridges
- 14:57Engineering of bridges 1700: good theories
- 15:3021st century
- 16:21Evolution of civil engineering
- 17:28Software engineering as engineering
- 20:27Craft practice, 1968
- 21:49Production techniques
- 22:55Commerce drives science
- 24:08Codified knowledge
- 28:55Software architecture ...
- 33:03Sample idioms / Styles / patterns
- 33:39Explanations for practitioners N-Tier architecture
- 34:14Commercial practice
- 35:06Maturation of scientific ideas
- 36:04Maturation of software architecture
- 36:21Basic research, 1985-1993
- 36:33Development & extension: 1995-2000
- 38:21Architectural styles and reasoning
- 41:20Toyota unintended acceleration
- 49:17Civilize the electronic frontier
- 50:06There are lots of casual developers
- 52:35Civilizing the electronic frontier
- 53:26Recapitulation
related talks
42mwhy software development is an engineering discipline
58mIs Software Engineering Still an Oxymoron?
55mEngineering for Software- 42mwhy software development is an engineering discipline
01h 00mEngineering Software
27m'The Art of Software Development'
28mSoftware Engineering - Development in 100 Years Time
32mSoftware Craftsmanship