Workflow

This page gives you an overview of how you work with MICROSAR Adaptive - from setting up a project to running it as part of an integrated system. Each phase below links to the chapter that covers it in detail; use this page as your map, not as the full instructions.

New to MICROSAR Adaptive? Complete Getting Started first - it walks you through installing the toolchain and building your first application end to end. Come back here afterwards; this page is the map you will reuse for every feature you build next.

workflow-diagram

This is a loop, not a one-way line - see Iterate and Update below.

Project Setup

Before you can configure anything, you need a working MICROSAR Adaptive delivery and a build environment. This covers extracting your BSW Package, understanding the delivery structure, and setting up TACO/CMake or Pesto/Bazel.

Configure

Define your application’s ports, communication, and deployment. Forge is the recommended, code-first way to do this: you author plain Python and get a diff-friendly, versionable configuration.

If you work with ARXML files, there are two ways to convert them into a Forge configuration:

Generate

Once your configuration is in place, generate the code and configuration files your application builds and runs against. The generators turn your configuration into C++ code (API) that matches the interfaces you defined, so your implementation and your configuration never drift apart.

  • With Forge, you use standalone Java code generators, which you trigger from a Python script using your Forge configuration as input.

  • With DaVinci Developer Adaptive, you generate code directly from your ARXML model, either from the graphical interface or from its command-line interface.

Re-run generation whenever your configuration changes.

Implement

In this step you write the C++ business logic of your application against the static and generated APIs of MICROSAR Adaptive. The Hello World Application walks through a complete, minimal example of this step end to end.

Build

Compile your application with TACO/CMake or Pesto/Bazel, whichever build tool your project standardizes on. The build produces an installable package containing your application binary and the runtime dependencies it needs on the target. If you haven’t settled on a build tool yet, compare the two options before you start a new project.

Test

Before you integrate your application into a larger system, check that it does what you expect:

  1. Install and run your application together with the MICROSAR Adaptive daemons and the applications it depends on.

  2. Check its behavior and log output: the expected messages appear, and no errors or warnings are reported.

  3. Optionally, run the Vector Code Analyzer for static analysis as an additional quality gate.

Automated functional tests are specific to your application and outside the scope of what MICROSAR Adaptive provides.

Integrate

Integration happens in layers, widening in scope each time. Each layer follows its own cadence.

First, your application integrates with the operating system and with MICROSAR Adaptive’s own daemons on the same machine. You can do this as often as you need during development, for example whenever you want to verify a change on the target.

Once that works, your application integrates with the other applications and ECUs that make up the overall vehicle system. This layer happens at defined points, such as when a feature is complete or when your project schedules a system integration.

Iterate

The fast loop is Configure, Generate, Implement, Build, and Test. As requirements change or a test fails, you loop back from Test - or earlier, the moment you notice something needs adjusting - into Configure again. If only your implementation needs to change and your configuration is still correct, loop back straight into Implement instead and skip Configure and Generate. Integrate sits outside this loop. You don’t integrate after every iteration, but at defined points, for example when a feature is complete or for a scheduled system integration, once your change has passed Test.

Update

Separate from the day-to-day iteration loop, Vector periodically ships new MICROSAR Adaptive BSW Package deliveries. Updating to a new delivery is a project-level event, not a daily task. When it happens, it feeds back into Project Setup above.