Skip to main content
Concept guide · ISO 26262-6 · 12 chapters

Model-Based Development

Learn where ISO 26262 obligations land when models become the source: toolchain, modeling guidelines, implementation models, code generation, the xIL ladder, back-to-back testing, coverage, analysis and tool confidence.

Chapters
12
Chapters
xIL rungs
4
xIL rungs
Worked example
1
Worked example
The short version

Quick answers

What is model-based development in ISO 26262?
Model-based development (MBD) is the practice of specifying software behavior as executable models (typically Simulink or TargetLink block diagrams and state machines) and generating production code from them instead of hand-writing it. ISO 26262-6 explicitly accommodates this: models can serve as the design representation, simulation becomes a verification method, and code generation replaces manual implementation. The safety obligations do not disappear, they relocate: into modeling guidelines, model-level verification, back-to-back testing between model and code, and a tool confidence argument for the generator per ISO 26262-8 Clause 11.
Does automatically generated code still need MISRA checking and review?
It depends on the confidence you can claim in the generator. If the code generator is qualified with an appropriate tool confidence level per ISO 26262-8 Clause 11, verification effort can shift to the model level, and per-line manual review of the generated C is not required. In practice, projects still run MISRA and static analysis on generated code with a project-blessed configuration, both as a safety net and because integration code around the generated unit is hand-written anyway. What the tool confidence argument buys you is relief from duplicating model-level verification at code level, not a blanket waiver.
Why this course · ISO 26262, Part 6

Why it pays for itself

Walk the full MBD chain

Follow the chain from Simulink or TargetLink block diagrams through modeling guidelines and implementation models to generated production C, and see where ISO 26262 attaches obligations along the way.

Climb the xIL verification ladder

Understand what MIL, SIL, PIL, and HIL each prove, how back-to-back testing demonstrates model-to-code equivalence, and which coverage evidence is needed on the model versus on the generated code.

Defend generated code to an assessor

Build the tool confidence argument for your code generator (classification, qualification, and the residual verification you still owe) so autocoded ASIL software gets accepted rather than re-reviewed by hand.

After the course

What you’ll be able to do

Place obligations in an MBD flow

Know where ISO 26262 verification obligations sit when the model is the source.

Apply modeling guidelines

Use and enforce guideline catalogs that keep models analyzable.

Verify across the xIL ladder

Choose the rungs and back-to-back comparisons that show model and code agree.

Measure coverage on both sides

Combine model and code coverage without assuming one implies the other.

Argue tool confidence

Classify and, where needed, qualify the code generator under Part 8, Clause 11.

The curriculum · 12 chapters

Chapter by chapter

  1. 01

    From Hand-Written Code to Models

    See how the model becomes the source, why automotive software moved to models, and how the risks move rather than disappear.

    • The model as source
    • Why models
    • Risks move
  2. 02

    The Toolchain: Models, Generators and Artifacts

    Meet the roles, tool families, data dictionary and artifacts of an MBD project, and where generated code lands in AUTOSAR.

    • Controller and plant models
    • Data dictionary
    • Artifact inventory
  3. 03

    What ISO 26262 Says About Model-Based Development

    Find where Part 6 addresses MBD, where models earn credit in the method tables, and what the standard does not say.

    • Home in Part 6
    • Credit in the method tables
    • What it does not say
  4. 04

    Modeling Guidelines

    Apply public modeling guideline catalogs, translate coding topics into model language, and enforce rules with checkers and CI.

    • Public catalogs
    • Rules in detail
    • Enforcement in CI
  5. 05

    From Function Model to Implementation Model

    Turn a function model into an implementation model through scaling and implementation decisions, and keep the two from drifting apart.

    • Two model roles
    • Fixed-point scaling
    • Preventing drift
  6. 06

    Production Code Generation

    Watch a model become code, treat generator configuration as source, adjust MISRA expectations and keep traceability to the line.

    • Generator configuration
    • MISRA and generated code
    • Traceability
  7. 07

    The xIL Verification Ladder

    Climb from MIL to HIL, see what each rung answers, and decide which rungs a project actually needs.

    • Four questions
    • Climbing the ladder
    • One vector set
  8. 08

    Back-to-Back Testing

    Compare model and code with back-to-back tests, set tolerances, judge vector quality, and triage disagreements.

    • Procedure
    • Tolerances
    • Triage
  9. 09

    Coverage on Model and Code

    Measure structural coverage on both sides, earn MC/DC by hand once, and see why model coverage does not imply code coverage.

    • Coverage metrics
    • MC/DC lab
    • Two-sided workflow
  10. 10

    Static Analysis and Formal Methods

    Go beyond testing with static checks on models, property proving and sound analysis of the generated code.

    • Model static checks
    • Property proving
    • Sound code analysis
  11. 11

    Tool Confidence for Code Generators

    Classify the code generator under Clause 11, combine confidence strategies, and know what a qualification package can support.

    • TCL classification
    • Confidence strategies
    • Qualification package
  12. 12

    Worked Example, Pitfalls and Assessor Questions

    Take a torque limiter from start to finish, review the pitfall catalog, and prepare for assessment questions.

    • Torque limiter example
    • Pitfall catalog
    • Assessment questions

Read all 12 chapters with Expert.

Start with a free account: the complete Functional Safety Concept guide and 5 practice exams a month, then upgrade when you need this guide.

Expert plan pricing
Worked Example

Torque Limiter, Start to Finish

The final chapter follows one torque limiter function through the model-based flow of the guide.

  • The function and its safety requirement
  • Model, implementation model and generated code
  • Verification across the xIL rungs and back-to-back tests
  • Coverage and tool confidence evidence
Torque limiter MBD flow
Function: a fictional torque limiter developed as a model

Unlock in course

Built for

Who this guide is for

  • Controls engineers whose Simulink models become production ASIL code
  • Software leads defining the verification strategy for autocoded components
  • Tool responsibles classifying and qualifying a code generator toolchain
  • Assessor-facing engineers who must argue why generated code was not hand-reviewed

Frequently Asked Questions

Common questions about Model-Based Development

The ladder runs the same test cases against progressively more realistic execution platforms. MIL (model-in-the-loop) executes the model in the simulation environment, proving the design logic. SIL (software-in-the-loop) runs the generated code compiled for the host PC, exposing code generation and numeric effects. PIL (processor-in-the-loop) runs the code on the real target processor, catching compiler and word-length issues. HIL (hardware-in-the-loop) tests the integrated ECU against a real-time plant simulation. Each rung answers a distinct question, and skipping one leaves a class of errors unexamined.
Back-to-back testing runs identical stimuli through two representations of the same component (typically the model and the generated code, at MIL versus SIL or SIL versus PIL) and compares the outputs, expecting equivalence within defined tolerances or an exact match for states and flags. ISO 26262-6 lists it as a verification method for exactly this situation: the verified design artifact is the model, the shipped artifact is the code, and back-to-back results are the evidence that the two behave the same. The course covers the procedure, tolerances, vector quality and the triage when model and code disagree.
The guide covers the full chain in 12 chapters: from hand-written code to models, the toolchain, what ISO 26262 says about MBD, modeling guidelines, function and implementation models, production code generation, the xIL ladder, back-to-back testing, coverage on model and code, static analysis and formal methods, and tool confidence for code generators. It closes with a worked torque limiter example, a pitfall catalog and assessment-preparation questions. A free account starts you off, and the Pro and Expert plans unlock more of the library.

Start the course today

A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov and RBD simulators, and 5 practice exams per month. The Pro and Expert plans unlock more of the 93-guide library. No credit card required.

Continue with

Where this topic leads next.

Browse all 93 guides
  • SoftwareFunctional Safety with AUTOSARAUTOSAR gives the car industry a standard software platform, but a specification cannot be ASIL anything, and a qualified stack does not make your software safe. Learn how the Classic and Adaptive platforms turn ISO 26262-6 requirements into concrete mechanisms: memory partitioning, timing protection, the Watchdog Manager and end-to-end communication protection.Expert plan pricing12 chapters
  • SoftwareLinux and Open-Source SafetyBuilding an ISO 26262 safety case for software nobody developed for you: pin down the exact kernel as an element, choose between qualification, proven-in-use and ISO PAS 8926, and guard Linux with external safety mechanisms.Expert plan pricing13 chapters
  • Safety analysesSafety AnalysesLearn how HARA, FMEA, FTA, STPA, DFA, and HAZOP complement each other across the ISO 26262 lifecycle. Covers method selection criteria, analysis sequencing, and a guide to choosing the right technique for each risk.Expert plan pricing12 chapters