Contrasting Embedded Software Development for the Space Shuttle and the Orion MPCV
summary
Shuttle flight software spans about 500,000 lines of code and reports fewer than a thousand defects over 35 years yielding roughly one defect per 400,000 lines per flight; testing is multi-level (peer review, unit, component, integration, verification). Orion uses a PowerPC 750‑based flight computer (200–300 MHz, GBs of memory, FPGA with redundant boards) and software in C/C++ compiled with Green Hills + Integrity for flight and GCC for testing; three uncrewed flights validate FDIR and expose needed unit‑test and coverage improvements.
AI-written summary · about
chapters (14)
- 0:00Spacecraft software development
- 7:53Hardware constraints
- 11:28Programming languages evolution
- 17:43Embedded flight software challenges
- 24:16Near-perfect software necessity
- 29:10NASA disasters lessons
- 37:45Flight software safety factors
- 41:59Documentation's critical role
- 47:55Shared safety responsibility
- 51:34Multi-level testing
- 54:33Space shuttle success
- 1:00:21Testing mindset
- 1:03:40Unit testing metrics
- 1:05:50Key takeaways
related talks
01h 31mOn the Future of Flight Software
01h 13mRecipe for Testing Spacecraft Ground Software
41mSoftware in Space: Lessons Every Developer Can Learn From
34mFrancois Martin: One Small Test for Man, One Giant Leap for Software Quality
50mSoftware archaeology - Learning from the landing on the moon!
49mThe Charming Genius of the Apollo Guidance Computer
55mSpace Shuttle
49mHARDWARE in SPACE! The Kernel at the Edge of the Universe