Developing AUTOSAR Applications with Model-Based Design

Name: Developing AUTOSAR Applications with Model-Based Design
Rating: 4.7 (8 reviews)

AUTOSAR Classic, Simulink Modeling, ARXML, and Practical Mapping in a Model-Based Design Workflow

Created byOS Academy

Last updated 2/2026

English

English [Auto],

What you'll learn

Understand the AUTOSAR architecture (Classic Platform) and its core layers: Application, RTE, and BSW, and how they interact within automotive software systems.
Build and model AUTOSAR Classic Software Components using Simulink and AUTOSAR Blockset within a Model-Based Design workflow.
Apply Simulink to AUTOSAR mapping concepts, including mapping model elements to AUTOSAR elements such as Runnables, Ports, and Interfaces.
Perform practical AUTOSAR mappings from Simulink models to AUTOSAR components and analyze the generated code and ARXML files.
Understand the role of ARXML files in AUTOSAR systems, their structure, and how they represent software architecture and configuration data.
Integrate Model-Based Design concepts into AUTOSAR application development workflows used in real automotive projects.

Course content

2 sections • 22 lectures • 5h 47m total length

From Legacy ECUs to AUTOSAR-Based Architectures16:00
Introduces autosar as an automotive open system architecture that unifies software interfaces, enabling hardware-independent, reusable software components and easier integration across legacy ecus and car models.
AUTOSAR Overview: Definition, Types, and Vehicle Integration6:00
Explore AUTOSAR as a standard automotive architecture with classic and adaptive platforms, enabling cross-OEM integration, software reuse, and features like OTA updates, V2X, and automated driving.
AUTOSAR Architecture: Application, RTE, and BSW Layers22:24
Discover how AUTOSAR architecture separates software from hardware using a three-layer stack—application software, runtime environment, and basic software—where components communicate through the RTE while maintaining abstraction.
Role of Vector and MathWorks in AUTOSAR Architecture13:14
Discover how Vector and MathWorks enable Autosar: Vector configures the basic software and generates the rte, while MathWorks provides model-based design with Matlab, Simulink, and Embedded Coder.
Roles of Embedded and Model-Based Design Engineers in AUTOSAR Architecture8:10
Define the roles of the embedded system engineer and the model-based design engineer within AutoZore architecture, outlining application layer models, runnables, interfaces, and auto code generation.
ARXML in AUTOSAR: Definition, Usage, and Contents11:32
Explore how the ERXM AR XML file defines AUTOSAR software components, interfaces, ports, data types, and runnables, and how it enables exporting and importing the .ar.xml between tools.

AUTOSAR Blockset: Tools and Methods for Classic Component Modeling15:10
Use the Autosar blockset to convert a Simulink model into a classic Autosar component, generate Autosar compliant C code and an ARXM file, and map runnables, ports, and interfaces.
Mapping Simulink Elements to AUTOSAR Components18:44
Translate Simulink elements to Autosar components to connect modeling with architecture, turning subsystems into runnables and mapping ports, memory, and data read axes for Autosar compliance.
Mapping Example: Entry-Point Function to Runnable with Generated Code and ARXML14:05
Map Simulink elements to AutoZoom elements using runnable and atomic subsystems, generate C code and arxm files, and explore the Interpoint function in the first example.
Practical Mapping: From Model I/O to AUTOSAR Ports and Interfaces26:14
Define ports and interfaces, map input to a receiver port and output to a sender port, then show how runnables read and write via RtRead and RtWrite in Autosar.
Overview of AUTOSAR Software Component Creation Steps16:52
Learn the steps to create an AUTOSAR software component by configuring the classic platform, selecting the application software component, and defining runnables, ports, interfaces, and internal memory for AUTOSAR compliance.
Practical AUTOSAR Classic Configuration via Model Configuration Parameters26:07
Configure AutoZar Classic Platform for a Simulink model to be AutoZar aware using model configuration parameters. Compare methods with AutoZar Component Designer and review AR XML, runables, and scripting.
AUTOSAR Classic Platform Configuration via AUTOSAR Component Designer Part_17:42
Compare the graphical AutoZore Component Designer workflow with the parameter-based configuration. Set up the model map, fix interfaces with AutoZore Aware, and generate AutoZore compliant code in Simulink.
AUTOSAR Classic Platform Configuration via AUTOSAR Component Designer Part_28:20
Apply the high-level autosar classic platform configuration workflow using AutoZawar Component Designer to configure a Simulink model, generate ARXM and AutoZawar compliant C code, and set AutoZawar.tlc with default mappings.
AUTOSAR Component Types: How to Choose the Right One17:25
Choose the right AUTOSAR component type to define what is allowed, how the RTE interacts, and how the application software component acts as reusable lego blocks via ports and interfaces.
Understanding AUTOSAR Component Types and Use Cases9:16
Learn Autosar component types—application, sensor actuator, complex driver, ecu abstraction, and service proxy—and how they connect through rte and basic software in model-based design.
AUTOSAR Component Types Use Cases and Selection Part 321:19
Explore Autosar component types, including application software components, sensor actuator, and complex device driver; learn how edc signals become physical values via io restriction and service proxy.
Introduction to AUTOSAR Ports and Interfaces13:17
Explore Autosar ports and interfaces, detailing required and provided ports, sender and receiver interfaces, and how to map them in Simulink for reusable software components.
Ports & Interfaces (Part 2): Types and Details23:35
Explains ports and interfaces in Autosar model-based design, detailing provided vs. required ports, sender-receiver, client-server interfaces, mode switch, non-volatile data, parameter interfaces, triggers, and inter-runnable variables.
AUTOSAR Dictionary and Code Mappings Editor: Configuration and Mapping10:34
Configure AutoZare elements and properties in Simulink using the AutoZare Dictionary and the Code Mapping Editor, define ports, interfaces, runnables, and IRVs, and map them to ARXML representations.
Practical Example: Sender and Receiver Ports with Sender-Receiver Interface18:13
Sender-Receiver Interface : Bus Element Ports and Multiple DataElements23:29
Explore the sender-receiver interface with bus element ports and multiple data elements in a runnable atomic subsystem, and map sensor data like speed and acceleration in Simulink for AutoZAR.

Requirements

Basic knowledge of MATLAB and Simulink.
Familiarity with C programming concepts is recommended (but not mandatory).
No prior experience with AUTOSAR is required — the course starts from the fundamentals and builds up progressively.
A PC or laptop capable of running MATLAB/Simulink and AUTOSAR Blockset.
MATLAB/Simulink with AUTOSAR Blockset installed (trial or licensed version).

Description

This course provides a structured and practical introduction to AUTOSAR application development using a Model-Based Design (MBD) approach. It is designed for engineers who want to understand how AUTOSAR Classic is applied in real automotive software development workflows using MATLAB/Simulink.

You will start by building a solid foundation in AUTOSAR architecture, including a clear understanding of the Application Layer, Runtime Environment (RTE), and Basic Software (BSW), and how these layers interact within modern automotive systems. The course then transitions from architecture to practice by introducing AUTOSAR Blockset and the tools used to model AUTOSAR Classic software components in Simulink.

A core focus of this course is the Simulink to AUTOSAR mapping process, where you will learn how model elements are translated into AUTOSAR elements such as Runnables, Ports, and Interfaces. Through step-by-step practical examples, you will see how entry-point functions are mapped to AUTOSAR runnables, how model inputs and outputs are mapped to AUTOSAR ports and interfaces, and how these mappings are reflected in the generated code and ARXML files.

You will also gain a clear understanding of ARXML files, their role in AUTOSAR systems, their structure, and how they represent software architecture and configuration data in AUTOSAR-based projects.

By the end of this course, you will not only understand AUTOSAR concepts theoretically, but you will be able to model, map, and analyze AUTOSAR Classic software components using a real Model-Based Design workflow, preparing you for practical automotive software development environments used in industry.

This course is ideal for engineers who want a clear, structured, and hands-on pathway into AUTOSAR application development using modern model-based engineering practices.

Who this course is for:

Embedded Systems Engineers who want to understand and work with AUTOSAR Classic in real automotive software projects.
Model-Based Design (MBD) Engineers who want to integrate AUTOSAR into their Simulink-based development workflows.
Automotive Software Engineers seeking a practical, model-based approach to AUTOSAR application development.
Engineering students and fresh graduates interested in automotive embedded systems and AUTOSAR-based development.
Control and systems engineers who want to transition from pure modeling to AUTOSAR-based software architectures.
Not intended for: Complete beginners with no background in engineering, embedded systems, or MATLAB/Simulink.
Not intended for: Learners looking for theoretical-only AUTOSAR content without practical modeling and mapping.

Developing AUTOSAR Applications with Model-Based Design

What you'll learn

Explore related topics

Course content

Introduction to AUTOSAR Architecture for Model-Based Design6 lectures • 1hr 17min

Modeling AUTOSAR Classic Components and Elements in Simulink16 lectures • 4hr 30min

Requirements

Description

Who this course is for: