Transforming Car Development
summary
Automotive software now costs more than any single component and grows from 100 million to 300–400 million lines by the decade’s end, causing accelerating software-related recalls and integration failures (eg. Bluetooth issues with iPhone 7). Carmakers face sprawling software supply chains — one customer integrates 70 suppliers — and must adopt layered integration: defect unification, integration operations, patterns, process frameworks and lifecycle architecture to achieve a connected value stream with traceability, continuous engineering, and metrics that let defects route to the correct supplier fast.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:30The first computer in a car
- 2:06Cars are becoming computers
- 2:49Elon Musk Tesla
- 3:17Why is the car industry attractive
- 4:24Infrastructure model disruption
- 8:19CB Insights
- 9:14Volkswagen
- 9:29Software
- 10:04Cost of Software
- 10:52Software Recalls
- 11:39Software Supply Chains
- 12:18Job Security
- 13:24BMW iPhone 7
- 13:43Why is this happening
- 14:03Lean concepts
- 14:34Boeing Dreamliner
- 15:52Manual processes
- 16:12Time to resolution
- 18:53How do we fix it
- 19:56Integration
- 20:55Integration Layers
- 24:25Defect Unification
- 25:28Integration Patterns
- 29:58Value Stream Mapping
- 31:57ISO Compliance
- 34:27Summary
- 35:16Contact Information
related talks
41mThe Evolving Software Landscape in Automotive and How Open Source Can Foster Cont...
17mperspective on automotive software and Eclipse SDV
20mDriving Intelligence: The Software Shift Shaping Tomorrow’s Cars
34mJourney towards a software-driven company
41mSW Mindset revolution in an Automotive Companye
34mDriving industry transformation
23mFrom Auto Parts Manufacturer to Productized Cloud Service at a Large Automotive Supplier
27mTransforming Traditional Enterprise Software Development Processes