Last week Dassault hosted the 3DEXPERIENCE conference in Eurocentral in Darmstadt/Germany. Two days of exciting content, exhibition and technical presentation sessions showing the latest product innovations helping enterprises become more competitive in their daily work. I also had the pleasure to talk about a highly compelling trend in the automotive industry, Software-Defined Vehicles and how Dassault solutions can help support this important technology evolution in automotive.

A key part of this presentation was the continuity between systems engineering and software engineering. Nowadays functional innovations for a new mobility experience are defined in the upstream systems engineering part of the process. This analysis and specification step can be done very nicely using the MagicGrid. However, once the detailed vehicle system specification has been worked out it should serve as a starting point and requirements input for the downstream detailed engineering. In particular for SW-Defined Vehicles their is strong need to establish a continuity into the SW engineering process. This continuity will be needed to ensure consistency and compliance of the software implementation with the upstream functional innovation specified in the systems engineering process as well as enabling efficient change management processes.

In order to facilitate this continuity Dassault released a new product called Systems Software Production Engineer (SOP) that generates from CATIA Magic models (SysML and UML) software artifacts in form of source code (C, C++), AUTOSAR XML files, FMUs, etc. that can be re-used in the software engineering process.

I have attached the complete presentation that I have done at the 3DEXPERIENCE conference as well as a demo video that shows SOP in action to form a complete process from SysML specification over AUTOSAR Embedded Software Architecture into detailed software code.