Master’s in Platform and Ecosystem Strategy Engineering for SDVs
Online master's programme of 1,900 hours in software-defined vehicle (SDV) platform and ecosystem strategy engineering. 12 modules covering SDV architecture, platform theory, digital business models, functional safety and cybersecurity, software operations, alliances, vehicle data regulation, product strategy and competitive scenarios, with an assigned technical tutor.
Take the controls.
Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.
What you will be able to do
Understand the technical architecture of the software-defined vehicle.
Analyse platforms and ecosystems using economic theory.
Design business models based on software and data.
Apply functional safety and cybersecurity requirements, including UN R155 and R156.
Assess the implications of the European Data Act.
Plan alliances and ecosystem governance.
Formulate long-term competitive strategies.
Who it's for
- Automotive digital product strategists shaping connected services and features on demand.
- Vehicle software architects working on zonal and centralised E/E architectures.
- Ecosystem and alliance managers negotiating with tech partners and Tier 1 suppliers.
- Connected mobility consultants advising manufacturers and fleets.
- Automotive cybersecurity leads who need a broader strategic view.
- Software platform directors at manufacturers and suppliers.
- Engineering or science graduates seeking to enter the automotive sector.
What you'll work with
- ISO 26262:2018 (road vehicles functional safety)
- ISO/SAE 21434:2021 (cybersecurity engineering)
- UN R155 (cybersecurity management system)
- UN R156 (software update management)
- ISO 24089:2023 (software update engineering)
- ISO 21448:2022 (safety of the intended functionality, SOTIF)
- Regulation (EU) 2023/2854 (Data Act)
- Automotive SPICE 4.0 (process assessment model)
- Vector CANoe
- MATLAB/Simulink
- Eclipse SDV
- dSPACE VEOS
- Enterprise Architect
12 modules · 1900 h
1.1From the distributed to the centralised vehicle1.2Zonal architectures and central computers1.3Decoupling hardware and software1.4Software life cycle in the vehicle1.5Over-the-air (OTA) updates1.6Features on demand1.7Fleet data as an asset1.8Changes in the automotive value chain1.9Technology players entering the sector1.10Case study: comparing the architectures of three manufacturers
2.1Control units and CAN and Ethernet networks2.2AUTOSAR Classic and Adaptive2.3Real-time operating systems2.4Hypervisors and virtualisation2.5SOME/IP and DDS middleware2.6Service-oriented architectures2.7The COVESA VSS data model2.8Central computing platforms2.9Vehicle-to-cloud connection2.10Lab: service modelling with SOME/IP
3.1Technology and transaction platforms3.2Complementors and external developers3.3Network effects in the automotive industry3.4Modularity and standard interfaces3.5Controlled openness strategy3.6Supplier ecosystems and alliances3.7Value capture in ecosystems3.8Mobile ecosystems as a benchmark3.9Risks of technology dependence3.10Case study: in-vehicle app ecosystem
4.1Recurring software revenue4.2Subscriptions and feature activation4.3In-vehicle app marketplaces4.4Usage-based insurance4.5Monetisation of driving data4.6Mobility and fleet services4.7Dynamic pricing and bundles4.8Customer acceptance and perceived value4.9Customer lifetime metrics4.10Workshop: business model canvas for a connected service
5.1Functional safety to ISO 262625.2Safety of the intended functionality to ISO 214485.3Cybersecurity engineering to ISO/SAE 214345.4UN R155 cybersecurity management system5.5Update management to UN R156 and ISO 240895.6TARA threat analysis5.7Secure boot and HSM modules5.8Fleet security monitoring5.9Manufacturer liability5.10Practical exercise: TARA of a connected function
6.1Automotive SPICE and process maturity6.2Continuous integration and deployment6.3SIL and HIL in-the-loop testing6.4Virtual vehicles and digital twins6.5Variant and configuration management6.6Open-source software in the automotive industry6.7Open-source licences and compliance6.8Fleet DevOps6.9Software quality metrics6.10Lab: CI pipeline with SIL testing
7.1Eclipse SDV and COVESA consortia7.2Alliances with big tech companies7.3Software joint ventures7.4Contracts and licensing agreements7.5Open API governance7.6Standards and standardisation bodies7.7Relationship with Tier 1 suppliers7.8Managing shared intellectual property7.9Conflict resolution in alliances7.10Case study: negotiating a software alliance
8.1The EU Data Act8.2Third-party access to data8.3Protection of drivers' personal data8.4EDPB guidelines for connected vehicles8.5Neutral data-access architectures8.6Consent and transparency8.7Data for maintenance and repair8.8Competition and access to the aftermarket8.9Data sovereignty and the European cloud8.10Practical exercise: mapping a vehicle's data flows
9.1In-cabin digital experience9.2Voice assistants and generative AI9.3Integration with mobile ecosystems9.4Driver personalisation9.5Interface design and distraction9.6Digital product life cycle9.7User research9.8Feature roadmaps9.9Usage and satisfaction metrics9.10Workshop: product definition for an infotainment system
10.1From manufacturer to software company10.2Attracting digital talent10.3Organising around internal platforms10.4Software procurement models10.5Agile culture in regulated environments10.6Software costs and budgets10.7Integrating technology acquisitions10.8Transformation indicators10.9Project risk management10.10Case study: reorganising a software division
11.1Market evolution scenarios11.2Chinese manufacturers and new entrants11.3Vertical integration strategies11.4Platforms shared across brands11.5Competitive analysis of ecosystems11.6Valuing software investments11.7Regulatory and geopolitical risks11.8Semiconductors and the supply chain11.9Ten-year strategic roadmap11.10Practical exercise: market scenarios for 2035
12.1Framing the strategic problem12.2Ecosystem and stakeholder analysis12.3Technology and competitive diagnosis12.4Business model design12.5Regulatory and risk assessment12.6Implementation plan12.7Economic and financial analysis of the plan12.8Validation with industry experts12.9Master's Thesis report12.10Master's Thesis: defence before a panel
How you'll learn
The programme is delivered 100% online on the SEIUM campus, with downloadable materials, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within each intake, so you can combine it with your job.
Each module combines theory, guided reading of the original standards and applied exercises. The working software is Vector CANoe, MATLAB/Simulink, Eclipse SDV, dSPACE VEOS and Enterprise Architect, in free, academic or evaluation versions. Exercises are based on real procedures: evaluating a features-on-demand business model, carrying out a TARA on a connected architecture and designing a technology alliance strategy. Assessment is continuous by module, plus the final Master's Thesis.
Standards covered: ISO 26262:2018, ISO/SAE 21434:2021, UN R155, UN R156, ISO 24089:2023, ISO 21448:2022 (SOTIF), Regulation (EU) 2023/2854 (Data Act) and Automotive SPICE 4.0.
Build it end to end
Your final project follows the real engineering workflow, step by step, reviewed by your tutor.
Where this takes you
Requirements
- A university degree in engineering, science or architecture, or equivalent demonstrable professional experience.
- An internet connection and a computer capable of running the programme's software.
- English sufficient to read technical standards.
Ready to start?
Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.
Frequently asked questions
The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.
You work with Vector CANoe, MATLAB/Simulink, Eclipse SDV, dSPACE VEOS and Enterprise Architect, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.
A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.
Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.
A university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the software and English sufficient to read technical standards.
Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.
Related programmes
Master’s in Technology Roadmapping and Competitive Intelligence Engineering
Online master's programme of 1,900 hours in technology roadmapping and competitive intelligence engineering. 12 modules covering innovation strategy, roadmapping, foresight, technology watch to UNE 166006, patent…
Master’s in Rail Policy, Regulation & Concessions Engineering
Online master's programme of 1,900 hours in railway policy, regulation and concessions engineering. 12 modules covering rail sector organisation, the EU railway packages, track access and…
Master’s in Technical B2B Sales and Complex Sales Engineering
Online master's programme of 1,900 hours in technical B2B sales and complex selling engineering. 12 modules covering technical selling, SPIN and MEDDICC, prospecting, bid engineering, customer…
More in Business, Management & Technology Policy
All Business, Management & Technology Policy programmes → · How to apply · Fees & financing · Scholarships