MAAB Guidelines Overview - Model-Based Development

MAAB: MathWorks Automotive Advisory Board

What Is MAAB?

MAAB 3.0 (Control Algorithm Modeling Guidelines) is published by a consortium of automotive OEMs and tier-1 suppliers (BMW, Bosch, Continental, Daimler, Ford, GM, Toyota, VW, ZF). It defines how Simulink and Stateflow models must be structured to be:

Readable by any MAAB-trained engineer across companies
Correct for Embedded Coder code generation (no silent type errors)
Reviewable and auditable for ASPICE and ISO 26262
Exchangeable between OEM and supplier without rework

Compliance with MAAB 3.0 is a contractual requirement in most European OEM supplier agreements for software deliverables.

MAAB Rule Categories

Category	Prefix	Example Rules
Block usage	db_	db_0140: No continuous-time blocks in production models
Signal naming	na_	na_0001: Signal names unique within model
Model structure	ar_	ar_0001: One root-level subsystem per function
Stateflow states	jc_	jc_0171: Every state reachable from default
Stateflow transitions	jc_	jc_0481: Transitions complete and exclusive
Data and types	jc_	jc_0021: All data must have explicit data types
Simulation	jm_	jm_0001: Model must run without errors at default params

MAAB Checks in CI/CD Pipeline

MATLABmaab_ci_check.m

% Run MAAB 3.0 compliance check -- used in CI/CD pipeline
model = "ProductionModel";
load_system(model);

% Run all MAAB checks
ma = ModelAdvisor.run(model, ...
    "Configuration", "maab", ...
    "Force",         true);

% Generate HTML report (attached to CI build artefact)
ModelAdvisor.report(ma, ...
    "Format",     "html", ...
    "FileName",   "MAAB_Compliance_Report.html", ...
    "OpenReport", false);

% Exit with error if any check fails (blocks CI pipeline)
results = ma.getCheckResults;
n_failed = sum(cellfun(@(r) r.Failed, results));
if n_failed > 0
    error("MAAB: %d checks failed. See MAAB_Compliance_Report.html", n_failed);
end
fprintf("MAAB compliance: PASSED (%d checks)\n", numel(results));

Summary

Running MAAB checks in CI/CD (on every model commit) rather than at delivery is the key process improvement that turns MAAB compliance from a painful delivery-time activity into a normal part of development. The most impactful MAAB rules for code quality are the data type rules: every signal without an explicit type is assigned double by Embedded Coder, generating 64-bit arithmetic on a 32-bit MCU. On an integer-only MCU this code will not compile; on an FPU-equipped MCU it silently uses 64-bit double instead of 32-bit single, consuming 2x memory bandwidth and producing slightly different numerical results than the simulation. Both failures are prevented by enforcing jc_0021 in every CI run.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.