Reflections around SW obsolescence
summary
Missile programs run a decade, products must last ~50 years, and 60–70% of development is now software, so reproducing a build environment 10+ years later becomes critical; virtualization helps but creates virtualization of virtualization problems, RTOS vendors lag on C++11/14/17, and some vendor tools are cloud-only. Proposal: a common component model with traced requirements, tests and ownership, cross‑project backlogs that flow across segmented networks, and MBSE/Digital Twin integration. Early pilots exist but full rollout needs funding, SLA rules, license control and organizational change.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:41Who am I
- 2:12DevOps and cloud
- 4:59Influencers
- 10:28Strategies
- 15:38Cross Collaboration
- 18:12Example
- 20:40Component model
- 23:55Maintenance
- 26:11Development
- 30:10Why
- 42:47Conclusion
