DaVinci TeamCollaboration and Continuous Integration for AUTOSAR Development
DaVinci Team - Standardized Automation Pipelines and Collaboration
DaVinci Team enables collaboration and Continuous Integration (CI) using standardized integration pipelines. In combination with the Vector tool DaVinci Configurator Classic and DaVinci Developer Classic, application software can be integrated into the AUTOSAR basic software MICROSAR Classic with a high degree of automation. Extensions for collaboration also enable efficient collaboration between globally distributed development teams and facilitate shortened release cycles.
- Automates manual steps in the integration of application software into the basic software
- Configurable and expandable CI pipelines
- Flexible integration into CI environments
- Enables optimization for collaboration in the development process
- Reduces merge conflicts
- Extension for DaVinci Configurator Classic
Read the White Paper to understand why traditional workflows and ECU development processes are facing new challenges and why DevOps oriented approaches with Continuous Integration are setting the new standard. This paper explains how the new approach can be easily implemented despite the monolithic structure of AUTOSAR Classic.
DevOps and continuous integration are having an increasingly strong impact on ECU development. For example, the number of project members in development projects from different departments or companies is constantly growing. The work groups are also distributed across several locations worldwide. This poses new challenges for software development. DaVinci Team supports developers of AUTOSAR Classic ECUs with an efficient collaboration as well as useful functions for Continuous Integration.
DaVinci Team can be deployed on servers, enabling developers to work on software artifacts largely independently. Standardized automation pipelines support the continuous integration of application software into the basic software.
Highlights of Version 1.0
- Customizable automation pipelines for different integration targets:
> vVIRTUALtarget - Basic Software Emulation
> vVIRTUALtarget - MCAL emulation
> Real target
- Executable locally or on the server
- Authoring support for editors with JSON schema completion
- Integration instructions for port, data, task mapping and NvM integration
- HTML report
- Automated creation and configuration of NvSWCs
- Instantiation of software components (SWC) and compositions
- Init value handling for optimized integration
- Back-in-time function for error analysis
- Optimized performance by saving compilation artifacts between integration runs
- Export of integration instructions from DaVinci Configurator Classic
Start a Conversation
Are you interested in more details about DaVinci Team or would you like to get a demo session? Then let’s talk!
Embedded Software expert
Helping to simplify AUTOSAR development
The optimized workflow of DaVinci Team enables developers to work more independently and collaboratively on the software artifacts. With AUTOSAR Classic, this allows the application software to be decoupled from the basic software.
The basic software is prepared as a "root configuration" and the application software is then enriched with integration instructions.
The integration of application software into the base software, as well as the creation of the RTE, is performed by the automation pipeline of DaVinci Team. This minimizes merge conflicts in the collaboration.
In a conventional approach, many manual steps are required to integrate application software into the basic software. The manual integration steps can take up a lot of time. In a development process with a centralized integration approach, where not every project member can perform the integration independently, blocking times can also occur.
The solution: DaVinci Team
- Integration can be performed by any developer through the pre-configured integration pipeline with a high level of automation. Without opening the tools.
- Deterministic execution of integration steps when changes are made to application software or basic software root configuration. Developers can efficiently deploy integrated ECU software, including its modifications, and run tests, all without delay.
The pipeline is achieved through a build system (gradle) and is available for the target controller or the virtualization software of Vector vVIRTUALtarget (basic software emulation) and vVIRTUALtarget (MCAL emulation).
The integration instructions define how DaVinci Team performs mappings or automated steps. These instructions can be attached to the app packages, for example. Alternatively, or additionally, integration instructions can also be defined centrally as global settings for the project. For efficient collaboration between the different roles in the project, different types of mapping instructions are available (Explicit Mapping, Mapping Rules or Auto-Mapping).
Enhanced Functionality for Collaboration
DaVinci Team is gradually being expanded with additional functions to make collaboration even more efficient. Among others, integrations in IDEs such as Visual Studio Code as well as a text-based diff/merge function for AUTOSAR artifacts (inline diff, 2-way, 3-way) are already under development. Also planned are collaboration extensions and automations for MICROSAR Adaptive.
DaVinci Team extends DaVinci Configurator Classic with Continuous Integration (CI) as a standardized integration pipeline for application software components, allowing software developers a fast and standardized integration of changed or new functionality. This opens the possibility of early function testing on ECU targets. In the development process, DaVinci Team reduces the blocking times caused by long integration intervals. Watch the video for more details.