Model Based Software Design and Development

Model-Based Software Development (MBD)is an embedded software initiative where a two-sided model is used toverify control requirements and that the code runs on target electronic hardware.

One side is the Control Model, representing the embedded software of the system. The architecture of the embedded software is modeled with blocks containing algorithms, functions and logic components.

Compiled software is auto-generated from this model.

The other side is the Plant Model, representing the physical aspects of the system. Each block contains mathematics that allows it to emulate the behaviour of that physical item.


Stages of Model based Development

Model-in-the-Loop (MIL):

In this stage, the software is run as the diagram-based model against the plant model in a simulated electronichardware environment. Once the performance is satisfactory, this provides a nominal baseline against the rest of the testing stages arecompared.

Software-in-the-Loop (SIL):

Here, compiled software is auto-generated from the control model and run against the plant model in a simulated electronic hardware environment. This testing reveals any errors in the compiled software architecture.

Processor-in-the-Loop (PIL):

With this stage, compiled software, still auto-generated from the control model, is run against the plantmodel on the target electronic processor, which is a programmed FPGA or custom ASIC. This reveals any issues with compiled softwareand target electronic processor interaction.

Hardware-in-the-Loop (HIL):

Finally, in this stage, the compiled software, against auto-generated, is run against the plant model on thefull target electronic hardware, often the final Electronic Control Unit (ECU)


The benefits of MBD are:

  • Shorter Lead Time Development,
  • Detecting the Error at early stage,
  • Development Cost Savings,
  • Increased Traceability,
  • Modelling and Coding Standards,
  • Validation and Testing.

ALTEN Global experience in MBD is depicted below:

MBD Projects
  • Body Control software (Full Life cycle)
  • Battery management system(Full Life cycle)
  • LCA C-Laws (Simulation Model Dev & MIL testing)
  • HVAC System (Full Life cycle)
  • Merging and Spacing algorithm (Simulation Model Development)
MBD Activities
  • Control Model Development
  • Model in loop testing
  • Software in loop testing
  • Auto code generation
  • Model traceability
  • Model coverage analysis
  • Models review
MBD Tools
  • MATLAB
  • Simulink
  • MATLAB State flow
  • MATLAB Coder
  • SIMULINK Coder
  • MATLAB Embedded Coder
  • MATLAB Coverage
  • Simscape
MBD Standards
  • DO-178C
  • DO-331
  • ISO 26262
  • MathWorks Automotive Advisory Board(MAAB) guidelines