PNSQC 2014 - Dr. Richard Turner
summary
Argues that software and systems engineering must be bridged by a risk‑driven, evidence‑based process that balances agility and discipline, using the Incremental Commitment Spiral Model with anchorpoint milestones to steer development. Recommends small teams, limited WIP, continuous V&V and concurrent multi‑discipline work, multiple independent cadences, COTS wrapping and model‑based SE. Cites failures — Future Combat Systems, Tacoma Narrows — and messy procurements (55 contractors, ~$600M) to justify the approach.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:30The Systems Engineering Research Center
- 14:24Comparing Systems and Software Engineering
- 18:18Fundamental Concepts
- 19:26Boehm's Fundamental System Success Theorem
- 21:15Boehm's System Success Realization Theorem
- 21:56Fundamentals of Discipline
- 23:54Fundamentals of Agility...
- 24:18The Conundrum as of 2003
- 28:11A Decade Later: SW Development
- 36:41A Decade Later: Systems Engineering
- 40:04Observations on the components of success
- 43:33The Two Strong Piers of Our Bridge Substructure
- 44:02An Illustration of the Need for Balance
- 49:46A New Framework for Balancing The Incremental Commitment Spiral Model
- 53:36What is the ICSM?
- 54:49ICSM Nature and Origins
- 56:59Incremental Commitment in Gambling
- 57:41ICSM Phased View
- 59:19Different Risk Patterns Yield Different Processes
related talks
55mAgile Engineering
45mTaking Back "Software Engineering"
11mLeading software teams with systems thinking
01h 21mPNSQC 2013 - Michael Mah
33mThe Agile Way to Add Sec, Dev & Ops into Waterfall
28mPragmatic Agile at scale with safety-critical products
27m'The Art of Software Development'
46mA Systems Approach to Safety and Cybersecurity