Close this search box.

Model Based Design of Automotive Software

ISO 26262 and AUTOSAR compliant

Complexity of modern automotive software demands development methodologies that save time and ensure reliability. We at Embitel, achieve this by using Model Based Design(MBD) powered by tools like MATLAB, Simulink and Simscape, and more.

Automation of Model Based Design processes like code generation, testing and documentation lead to faster time to market something that automotive companies always aspire. Model Based Development (MBD) can result in average costs savings of 25%-30% and time savings of 35%-40% (according to a global study by Altran Technologies, the chair of software and systems engineering and the chair of Information Management of the University of Technology in Munich)

Over the past decade, our team of MATLAB programming experts has been delivering cost and time savings with Model Based Design approach for product development.

Use Cases for Model Based Development of Automotive Embedded Software

Embitel has successfully delivered automotive software developed using Model based design methodology. Our expertise in MBD powered automotive product development spans across the following areas:

Body Control Module

MBD Software Code Generation: Compliant with Automotive Industry Standards

Learn about the process of MBD and our capabilities in
model based development of automotive solutions

A Handbook on Model Based Design

A Handbook on Model Based Development

Learn about the process of MBD and our capabilities in model based development of automotive solutions


Model Based Design Services for Automotive Product Development

  • Model Based Design of System level architecture and solution services
  • Identification of maximum possible issues/queries during H/W & S/W requirement analysis
  • Requirement freezing after resolution of these issues
Migration from Non-MBD to MBD paradigm
  • Architecture Development mapped with Model Based Design paradigm
  • Modules/ Component Development in MATLAB, Simulink, Stateflow as per MAAB guidelines
  • Memory Optimization for RAM/ROM according to MAAB guidelines
  • ISO 26262 Compliant Models Rapid Prototyping- Virtual Prototyping, External Bypass etc.
Verification & Validation Services
  • Model in Loop Testing (MIL)
  • Software in Loop Testing (SIL)
  • Hardware in Loop Testing (HIL)
  • Processor in loop testing (PIL)
  • Simulink Design Verifier
  • Verification and Validation (V&V) of MATLAB Simulink Models
ISO 26262 Compliant MBD approach
  • Software development in compliance with ISO 26262 (part 6)
  • Support for development focused on ISO 26262 requirements specific to Model Based Design
  • All additional V&V requirements are fulfilled based on ISO 26262 standard
  • Models are created based on the requirements as per the ISO 26262 Model Based Design guidelines
Auto Code Generation
  • Code Generation using Target Link (MATLAB model conversion to Target Link Model)
  • Code Generation with Matlab E-coder
  • MISRA, AUTOSAR compliant code
  • Custom Code Generation with Custom Target Language Compiler and E-coder
Integration Services
  • Application & LLD Interface Development
  • Integration Testing in real time environment to ensure error free module interactions
  • Testing on real-time hardware (bench testing) (HIL)
  • Testing on a target processor if real-time hardware is not present (PIL)
fixed point concept
Floating to Fixed Point Conversion
  • Support for Conversion of Floating point models to Fixed point models as per customer requirements using Mathwork Fixed Point Converter Tool Box.
  • Support for Conversion of floating point Matlab code to fixed point code.
  • Code generation & testing of floating and fixed point models for the comparison of results, in order to ensure expected accuracy.

Video Explaining How Model Based Development Works?

Customer Success Stories of Model Based Design and Development

Our Expertise inModel Based Design Tools and Technologies

Expertise in MBD Tools and Technologies

Embitel’s Model Based Development Methodology

Model Based Development Methodology

FAQ’s Regarding Model Based Design

What software development model do you comply with for delivery of Model Based Development Projects?

Ans. Our Model Based Software Development team follow the industry accepted V-cycle SDLC Model. Over the last 12+ years, we have achieved ensured complete compliance and alignment of this V-model with enterprise level QA modules such as CMMI Level-3 and ASPICE.

The quality of the artifacts and documents generated throughout the development process are in compliant with CMMI Level-3 and/or ASPICE.

We have also worked on projects where we delivered the artifacts compliant to both CMMI Level 3 and ASPICE, as per the requirements of the customer.

Have you executed and delivered any MBD process automation/improvements for the customers? What benefits did customer experience due to this automation?

Ans. For one of our Model Based Development projects, we developed an automation tool that could convert libraries of floating point to fixed point model. This conversion was the step prior to generating the code and integrating it with the low-level drivers.

Completion of this conversion manually would have taken more than a week for a developer. Also, it would be error prone, as a lot of data type changes and I/O port name changes would have been required.

However, with the help our Automation Tool, we could convert 16 such libraries to fixed point in 1-2 days.

The benefits for the customer were

  • More accurate conversion, better quality of the code and very less turn-around time.
Does Embitel provide post-integration support for Model Based Software Development?

Ans. Yes, post-integration support is part of the Service Level Agreement (SLA). Any kind of bug fixes and change requests, during or post the integration in production environment are part of our model based design support and maintenance services.

If required, our Model Based Design experts can also travel to the customers’ location for an Onsite Support.

Can Embitel provide consulting service for MBD process setup, tool chain selection and more for a new initiative?

Ans. Yes, Embitel has all the necessary skill-sets to help you setup Model Based Software Development process.
Our MBD experts will help you with the following processes:

  • Support for Documentation related to each and every phase of V based SDLC model.
  • ISO 26262 compliance
  • AUTOSAR based model development
  • Test plan, test cases creation
  • I/O documentation for every phase of V-cycle as an evidence for CMMI or other QA audits
Does Embitel have experience in AUTOSAR based MBD project?

Ans. We have expertise in designing both Non-AUTOSAR as well as AUTOSAR based MBD models.

Our MBD experts have worked on projects where standard AUTOSAR guidelines have been followed for model creation, data type nomenclature, I/O names, vehicle diagnostics and more.

What is the team structure for the execution of Model Based Development Projects, can you share the details?

Ans. When you partner with Embitel for Model Based projects, you can expect to collaborate with an expert core team of Model Based Development Consultants, Project Managers and Automotive Engineers.

Here is the team hierarchy that is most commonly followed in the Model based software development project.

  • Veteran Model Based Development Managers, who ensure end to end V cycle based MBD project execution. Compliance to the organizational process execution model is also ensured by them to the highest level possible.
  • Senior MBD Consultants with 14+years of experience, to partner with you for critical automotive projects for product (ECU)/application development and consulting support.
  • Senior MATLAB programming experts proficient in developing automotive ECUs/applications as per the latest industry standards including MAAB, AUTOSAR, and ISO 26262.
We have a non-MBD product line that is under development/ready for production. How can we migrate to model based development for the product line?

Ans. We can help you with a phased adoption of Model Based Development paradigm after in-depth review of the architecture of your existing product line.

Here is a brief overview of how a MBD adoption/migration approach may turn out be:

  • Getting ready for the migration: Includes assessment of current state of the development process and learning the core MBD tools.
  • Feature selection as per project scope: Understanding and fin-tuning of scope and requirements at every phase of development, selection of features, modeling and simulation and code generation.
  • Component selection and physical modelling: Activities include Expand modelling, simulation at component level and introduction of plant modelling.
  • Standardization: Performing Simulation at system level and full model based verification and validation. Best practices like introduction of tool automation and creation of reusable libraries also come into picture.
  • Optimization: The final phase is to align the MBD approach with enterprise vision and goals. Objective is to make the processes fully automated and optimized.
What are the applications of model based design in automotive software landscape?

Ans:Model-Based Design (MBD) in the automotive software landscape facilitates the design, simulation, and testing of automotive software before physical prototypes are built.

It streamlines development, enhances accuracy, and reduces costs.

For example, MBD is used in designing advanced driver-assistance systems (ADAS), where simulations predict system responses to various scenarios, enabling early detection and correction of issues, ultimately speeding up the ADAS development cycle and improving safety features.

If we compare it with a non-MBD approach, developing a new adaptive cruise control feature would involve manually writing and integrating code based on the system’s specifications, with physical tests conducted on prototypes to validate functionality. This could lead to significant delays if errors are found late in the development process.

Conversely, with an MBD approach, the same adaptive cruise control system is designed using models that precisely define its behavior. Simulations based on these models can quickly test various scenarios (e.g., different traffic conditions), identifying issues early. Automatic code generation from validated models further speeds up development and reduces errors, making the overall process more efficient.

Knowledge bytes

  • Reduced system complexity
  • Test suite reusability
  • Design reusability to multiple hardware target deployment
  • Automatic code generation
  • Continuous error identification and correction
  • Enhanced efficiency of up to 50%
  • Reduced time-to-market and overall cost of development
  1. 1. Model Based Design (MBD) is a software development methodology based on V-cycle.
  2. The model based approach enables a developer to simulate the models for the complex control processes.
    • These software models can be tested to assess the performance in real-time. Once finalized, the code can be auto-generated from the models, using code generation tools.
    • This way, the product can be tested at every stage of its development before the code is generated.

Here is a snapshot of Model Based development process:

  • Requirement Maturation: Hardware and Software requirement analysis is performed as the first step to weed out maximum number of design issues.
  • Model Simulation: The desired functionalities are expressed in the form of mathematical formula which eventually become models using simulation tools like MathWorks Simulink.
  • Testing and Validation: Software-in-loop, model-in-loop and hardware-in-loop testing are performed on the model. As it is an iterative cycle, any issue found at any stage is rectified by tracing it back to its previous stage.
  • Code Generation: Code is auto generated from the tested and verified models.
  • The advantages are many that have made model-driven approach, a method of choice for automotive software development. Model Based Design approach renders a great value-add for development of powertrain and chassis control applications, in particular.

A few of MBD’s advantages:

  • Continuous testing of the software at every stage ensures that it is free from bugs/ errors and is of the highest quality.
  • Time-to-market is reduced considerably as code doesn’t have to be written manually.
  • MBD makes it easier to design Complex functions, as it requires less iterations.
  • Cost of development is reduced.
  • Test suites can be reused for different production programs.
Scroll to Top