← Course overviewFree lesson 1 of 3 · lesson 1 of 37Next lesson →

Unlock all 37 lessons of Software Verification and Validation and System Testing for Model-Based DevelopmentFull course ₹40,000 · paid

Price & syllabus
Free lesson · 39 min · no payment

Model-Based Development for Automotive Embedded Software

A free lesson from Skill-Lync's Software Verification and Validation and System Testing for Model-Based Development course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Introduction to Model-Based Development”

What will you learn in this free Software Verification and Validation and System Testing for Model-Based Development lesson?

The instructor explains how automotive software grew from 50,000 lines in one ECU to 100 million lines across many ECUs. The lesson then covers the three pillars of model-based development, modeling, simulation and validation, and contrasts it with the linear traditional cycle using MATLAB Simulink.

  • Growth of automotive software and ECU count
  • Modeling, simulation and validation as three pillars
  • Traditional linear cycle versus model-based cycle
  • Benefits: variants, reuse and bidirectional traceability

What comes after lesson 1?

The next free lesson is lesson 2, “SDLC Methodologies and the V-Model in Automotive Software” (48 min). Later in Skill-Lync's Software Verification and Validation and System Testing for Model-Based Development course (paid): lesson 4, Software Verification and Validation and System Testing for Model-Based Development; lesson 5, Software Verification and Validation and System Testing for Model-Based Development; lesson 6, Software Verification and Validation and System Testing for Model-Based Development. The full course has 37 lessons (19 h 41 min of video); see the course overview or its price and syllabus.

Lesson transcript

Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.

Welcome to today's lecture on Software Verification and Validation and System Testing for Model-Based Development. The topic for today's discussion is Introduction to Model-Based Development. In this topic, we are going to see about the software development demands in automotive industry, model-based development, development, different stages of model-based development, and the advantages in model-based development. Now, let us see each topic one by one. The learning objectives out of this session would be a thorough knowledge on what model-based development is all about, why it is adopted in today's modern automotive embedded software development, development, the different stages of model-based development, and the advantages in adopting to the different stages of model-based development.

Okay. The first topic that we are going to see today is about the software development demands in automotive industry. So, this is an image of a modern automotive system. So, as you can see here, there are multiple features, and these features what we are talking about mostly is a embedded software feature which is present in the modern automotive system. Like if you can see, you have adaptive cruise control, automatic braking, electric power steering, electronic valve timing, idle start-stop, OBD, that is onboard diagnostics, and you also have the electronic stability control, parking system, the tire pressure monitoring, regenerative braking, and also from the battery side, you have the battery management system, the entertainment system, cabin environment controls, etc.

And also, you can see about the interior lighting, instrument cluster, driver alertness monitoring, head-up display, parental control, engine control, and so on. So, now, if you are looking at all these different features are there, right? So, each of these features can kind of be classified under a specific system. Okay. For example, when we are talking about the advanced driver assistance system or ADAS in short form, okay, features like the blind spot detection, lane departure warning, adaptive cruise control, anti-lock braking system, etc., they all fall under the ADAS system.

When we are talking about the powertrain and chassis, we talk about the engine control predominantly and also about the electronic throttle control, electronic valve timing, electronic power steering, cylinder deactivation control, and so on. When we are talking about the body and the comfort, we are dealing with the physical vehicle. Without talking about the chassis, the powertrain, and the engines, we are talking about the physical vehicle and the in-vehicle features. Okay. So, things like the voice or data communication, the car temperature control, and auto-dimming mirror, interior lighting, and instrument cluster, most of these come under the body comfort system.

When we are talking about the driver information and connectivity, usually the cluster and the internet of things and topics like these, they come under the modern automotive system. So, if you can see in the cars of today, there are multiple such features that is being associated with and they are broadly classified under so many categories. Okay. So, now if you can see, okay, over a period of time, I would have to say, okay, the number of features in the car has really grown. Okay. When we are talking about the first automotive ECU, which was a single function controller that was developed in the year 1978 by General Motors.

And in 1981, General Motors were just using 50,000 lines of code, software code, across its entire domestic passenger car production. Okay. But back then, there was only single controller, one ECU for controlling the complete car. But when you are talking about today's automotive market, you have 100 million lines of code, which is running on 70 to 100 microprocessor based ECUs. And on an average, each car is today carrying close to, I would say, at least 15 to 20 ECUs. At least the cars, which is in the Indian market, would have anywhere between 5 to 10 ECUs.

And when you are talking about the high-end cars in the European and the North American market, they are easily carrying nearly 15 to 20 ECUs, where the complexity of the code is very high and it is no more the single core or single controller processors, rather you are having a multi-core ECU and multi-core processors that is there. So this kind of shows us over a period of time, how the features have increased in the car and also how complex the features have become. Okay. For example, if you are talking about the cars in 1980s and even until the 1990s, most of the cars did not have electronic power steering and the throttle control was not electronic based.

It was all mechanical based. So for features like that, there was no real software control that was required. But the cars in today's market, if you can see, it has all become electronic based. Basically, the throttle control and as well as the other such features are concerned, they have all become electronic control. So for this, when we are writing, we are in a position to write a separate software code to in order to control its functional behavior. So this is how the feature complexity has kept on being adding in the modern automotive application.

Okay. So this graph over here, it will give you an illustrative picture of how the software complexity has increased in today's cars. So if you can see this bar over here. So the car back in, I would say, the early 2000s and even in the 2010s, it was not a connected car. Okay. It had all standalone software features and most of the software features were kind of very basic. Okay. In the era between 2014 and 2017, the connected car, Internet of Things and autonomous car features slowly started coming into the car production market.

Even the cars which is running in the lower segment also started producing more such features. In the era between 2017 and 2020, we had a lot of autonomous driving and at least level one and level two autonomous driving vehicles started coming into the market. And upwards of 2020 until the projections are until 2025 or 2026, where many leading OEMs, like say people like Tesla, people like Mercedes-Benz, they are looking at completely autonomous cars, basically driverless cars. So when you are talking about such system, obviously the software complexity, both from the algorithm perspective and also the size of the software, the size of the software, I mean to say here, the complexity of the code is really going to go up in the market.

So this is the, in terms of the software, a feature complexity projection, this has been projected. So whatever has been the complexity, say like 15 years back, it has almost three times and four times the code complexity has become in today's market. One important thing one has to remember over here in terms of the code complexity is that even though the code complexity has gone up, okay, the algorithm complexity has also gone up overall. And also the ECU, okay, the target ECU, where the software has to be written or flashed, okay, even that ECU memory capability and the controller complexity has all gone up.

Okay. So the need for quickly writing the software comes into the picture. Okay. Now let us go back to the example. We were talking about 1980s, right, where 50,000 lines of code was used in the one single ECU, which governed the software operations of a complete car. Back then, all the 50,000 lines of code would have been written by a few set of engineers who were very good in C programming. Okay. But over a period of time, since the ECU complexity is going up, the more information is needed about the ECU architecture.

And also a lot of engineering based complexity is being brought into the system. So a deeper knowledge on mechanical engineering, on the thermodynamics, on the battery management and the advanced driver related features. So such specific domain knowledge and expertise started was needed. Okay. A software engineer, basically one who is a real expert in C programming cannot have all such knowledge, okay, to basically go and start writing to understand what is a powertrain related system and try to write it or bring it into his code. Likewise, someone who is really strong in the domain, right, he cannot go and start writing a way.

Very powerful and high complex C code, which is going to match the requirements. So this was a catch 22 like situation where at one end you had the growing demands for the software development where very high quality software is needed and also very, very stern domain knowledge and domain expertise was needed. So how to bridge this gap? Okay. So where is that gap going to be bridged? Okay. And also another key thing that they looked at is that there was a lot of competition that was coming up in the market. And also with newer, newer technologies and features coming into it, lot of safety certifications and multiple software systems, more players started emerging in the market. So people started looking, people I mean to say here is that the OEMs, okay, the OEMs started looking at taking their software quickly to the market.

And giving newer, right? And giving newer added features to the customer at a very, very reduced cost. Okay. That is the cost at which they are trying to provide these features to the customer has to be very reduced. So when you're taking and looking at all these things, the demand to develop the software very quickly, very efficiently at a very faster rate. Okay. All this started multiplying. Okay. And they started analyzing some of the risk that was there or challenges that was there in today's market. Okay. They were talking about the damage, reputation, recall and the time waste. Okay. So in the previous eras, it was all about hand coding with newer features coming into picture and more complex algorithms coming into picture.

Okay. Okay. The skill for writing very efficient software code also was very high. Okay. Now say for example, we are having a mechanical engineer who has a very, very strong power train domain knowledge. Now when we are asking this particular engineer to come and write say a boost pressure control algorithm from an algorithm perspective, he would be really strong. Okay. But when he would not have such high skills in terms of C programming. Okay. So when he starts to naturally learn, understand and code, there could be a lot of issues. Okay. The time that he takes to learn and write such code will be very high. And also on the other hand, when you are asking a C programming developer to understand the boost pressure algorithm and come and write it, then naturally he will also take a lot of time to write.

Okay. Okay. So there are a lot of chances for the software quality going for a toss. Okay. So these are usually seen as risk. Okay. So this you have to handle the software quality. You have to ensure that the software is 100% foolproof and it takes very, very lesser time to go to the market. Okay. And there should not be any recall of the vehicle in terms of the software related things. So these were some of the risks that were foreseen and the time to go to the market. And the time to go through a lot of safety certifications and software systems, which was also considered to be a major challenge for today's market. The more time the software took to go to the market, it started to add on to a lot of production costs. Okay. So what can be done here? Okay. So at one side, you had a lot of challenges in terms of quality and the cost.

You had millions of lines of code coming in, you needed an efficient calibration mechanism and you had multiple variants. Okay. So the multiple variants that we are talking about here is that certain software features are standard. Okay. And certain features will only be available in a particular car only in high end versions. So you need to ensure that one software package will have all the features, whereas the other software package will not have all the features. So in that case, what you can do is that you need not cut and you paste the code and you need to ensure that the unwanted lines of code are stubbed accordingly from one variant to another variant.

So these were some of the challenges that were posed. And moving the code from one variant, right? That also was very, very time consuming in your normal manual coding related operations. So these were some of the challenges that the automotive embedded software development industry was facing. So what are the possible solutions that was foreseen? Okay. So some of the common solutions that most of the OEMs and tire one suppliers were looking at was the standard design and architecture, model based development, parallel software development, and multi core ECU. Okay. Among that, one of the most common, most influential, and one that has been widely adopted by all the industries, that is most of the major OEMs and the tire one suppliers across multiple features is the model based development. So now we will see what this model based development is actually about. Okay. Model based development, you can briefly put it across in three different phases, three different phases. I mean, it is not like three stages of operation. Okay. I would say that these three points that you are seeing here, that is modeling, simulation, and validation. These are considered to be three major pillars of it. Okay. Okay. So MBD is called model based development and three major pillars of it is modeling, simulation, and validation. So what is modeling? Virtual representation of the real world problem. Okay. Codes are generated based on the model. Okay. The next one is simulation. That stands for testing the behavior of your model in conditions, which is different difficult to reproduce. It is difficult to reproduce the physical models. The third one is the validation at every iteration between the modeling and simulation. So this improves the quality of final software product. So what is modeling? Development of a model. Okay. So basically, you have a requirement or a problem statement. That requirement or a problem statement, when it is related or when it is realized in a simulation, it is related or something like it is related or something like that, you have an overview of the modeling that you have been tested, right?

To ensure that whatever input that you are passing seamlessly, it is going to give you an output. And also once the standards and guidelines, whether the model related settings or whether the block related settings or the software industry standards, whatever that is there, whether it has taken care of. So once you ensure both these things and once you develop the model, this model can be simulated. This model can also generate code out of it. And whatever code that this model is generating is an industry standard code. And the next one is validation, where at every stage you can do the validation. Once from the requirement, once you develop the model, based on what is the requirement information, you can pass some set of inputs and you can see the expected output that is coming out of the model and compare those results against the actual output.

By comparing the results against the actual output, whatever the expected output versus actual output is coming. Any change that is needed at the model level, you can go and correct it at the model level. Likewise, it will also give an indication whether I have developed my problem as per the requirement. So another major advantage of modeling is that these are all graphical blocks that you have. So the need for syntax is not there. When you are talking about C programming, one needs to remember a lot of syntax and based on that syntax only your code has to be generated. So it was really difficult for non-computer science and non-IT people to write engineering software codes given the growing complexity. But now as far as modeling is concerned, since you are developing a graphical representable control algorithm in the form of a model that can be converted into a code after going through a lot of sanity checks and model guidance reports, looking at the model guidance reports and so on. Okay. And also at every stage, the validation is possible as we have already discussed, which will improve the software final quality product. So this is what we call as model based development. Okay. So how model based development is different from the traditional software development cycle. Okay. The traditional software development cycle is a very, very linear process. One has to say, okay, not just the traditional software development cycle, even in model based development cycle. Okay. There are certain stages of development one needs to know. Okay. One is the requirement specification, design, implementation, test and verification. Everything is there both in traditional software development cycle and the model based software development cycle here. But how it is different from the traditional to the modern is that, see, we know what is the requirement. Okay.

The requirement will be in the form of Word document or in an Excel document. Either it can be in the form of a text. It can be in the form of a flow chart. It can be in the form of a table or can be in the form of a text, see, or what is the exception. Yeah. Do that kind of thing. Whatever it is. Okay. Whatever the requirement that is there, that requirement has to be first understood and then it has to be converted into a handwritten code.

Again, we already discussed about what are the challenges that handwritten codes face. Okay. Once if the complexity keeps increasing, it becomes too difficult to develop 100% foolproof and very, very clear handwritten codes. And also the need for technical experts. Okay. Either a proper C programming person needs to have very good engineering knowledge or a person with very good engineering knowledge needs to have very, very sound MATLAB hand coding skills. Okay. So this is a very, very catch 22 situation that we already discussed. So, okay. So that was another challenge.

So understanding such skills and understanding the requirement and writing a very, very foolproof software code. Okay. It was considered to be extremely time consuming process. Okay. And then directly you had to test on hardware. So once your C code is ready, you put that C code into a compiler or you can flash it into the ECU and then you will only be testing it at the vehicle level directly. Okay. Okay. And any issue, if you find that with respect to bug and all, you have to again, go back to the drawing board. Okay. So the flow will always be from the left to right of your screen, starting from requirements, design, implementation, test and verification.

And finally, when there is any issues that is occurring, you have to go back to the first stage and then you have to see whether the issues with respect to the requirement issues with respect to the implementation or what. So all this analysis has to be done and then only you have to do the fix. So it is considered to be a very, very linear and completely time consuming process. Okay. So another major disadvantage with this is that whatever design that you are doing, you cannot find any fault or issues at the design stage or at the implementation stage.

Only at the final level, you can monitor like if there are any design or requirement related issues that is found and then you have to go back, analyze it, fix it and then you have to repeat the whole process. So every time you only during the last stage, you will find out what is the actual issue and then you would have to come back. So this is considered to be a major problem in the traditional software development cycle. Now let's come to the model based development cycle.

In model based development cycle, what exactly happens is that it is kind of a cyclic process. Like the traditional cycle, you have the requirements specification, design, implementation, test and verification, everything is there. But okay, since it is a model based and a tool based development technique, right at the requirement stage, at the design and implementation stage, at the verification and validation or the code generation stage, at every stage, at every stage, the tool will have a bidirectional traceability. Bidirectional traceability means what I mean to tell is that, say, for example, the software simulation tool that we are discussing is MATLAB Simuling.

So I will be talking from MATLAB Simuling perspective itself. So let's take MATLAB Simuling. So the first stage is requirement analysis. So MATLAB has requirement analysis and requirements manager toolbox. So using that toolbox, we can map the customer requirement directly into our skeleton model. So that will ensure that whether all parts of the requirement you have implemented. This particular thing is not possible in manual coding based approach. The next one is model simulation. So all the once the basic skeleton is done at the model level, then any individual signal related or individual requirement related modeling designs and guidelines or not, it has to be implemented.

So once you implement all that, then you can simulate the model and see whether it is causing any issue. And also there are a lot of design verifier tools are there. And apart from the design verifier tools, there are certain industry standard checks that can be done, whether your model is developed as per the automotive industry standard. So checks for that is also that that will be done. And then finally, you will have test verification and validation. OK, so once if there is no issues in the requirement, you only then you can go to the next stage.

OK, if there is any issues that is found at the requirement stage itself where you have missed any requirement, means then you have to go and you have to add the requirement during simulation. When you find any issues, you have to go and fix it at the model level. If your model is having certain properties, which is not as per the industry standards, then you have to go back and then you have to fix those industry relevant settings. And then you have to do the simulation.

You have to retake those reports. So at each stage, there are checkpoints where you can stop and you can verify and you can kind of validate your approach, whether at the requirement stage, whether we are doing correct, whether at simulation stage, we are doing correct, whether at test and verification stage, we are doing correct, whether at autocode generation, we are correct. And everything we are doing and the final code that is generated from the MATLAB Simulink model, right? It is 100% as per the industry standards.

So you need not worry about the syntax, whether it will compile properly in the compiler. You need not worry about such things. And so and you can solely focus on the algorithm part. That is from an engineering perspective, whether we are implementing our algorithm correctly. You only need to focus on that. But in the traditional approach, you both had to focus on the algorithm that is from an engineering perspective about implementing the algorithm. And also you were to focus a lot on the whether I am writing the correct piece of code, whether this code will be compiled correctly or not, whether is it going to have any kind of syntax error.

You need not worry about that. So this is the major difference between traditional software development and model based development here. In very simpler words to say, traditional software development is a linear based approach, which is not at all user friendly, but model based development is a continuous and iterative approach where at each stage you will have stoppers to kind of check, verify and validate your approach. So that is with respect to the model based development. And what are the major benefits of model based development? We have discussed already about some of the benefits while explaining about the traditional software development and model based development.

So models here are considered to be the core of development. OK, and these models can be stored and then it can be retrieved. OK, and also we were talking earlier about the variance, right? So when we are talking about variance, certain features have to be stubbed. So stubbing the features in a C code is a very, very difficult task. So, but stubbing the features in at the MATLAB model level, right? So that is very, very easier. OK, so such kind of model leverage capabilities are there in model based approach.

OK, and also these variance can be evaluated very, very fast compared to the traditional approach. OK, and there is a test and validation at each stage, which we have already told about and reduced development cost. The reduced development cost here means the time that it takes to go to the market is very, very quick here. So with newer cars coming in the market, newer features in the market and having so much of a competition between multiple OEMs, the quicker time your software goes to the market, you can actually quicken the car production, software production, and you can kind of sell more cars with more increased user friendly features.

So all of this is considered to be the benefits of model based development. OK, and also about the reusability of models and model templates. OK, the model templates once developed, they can be reused. OK, and in the future, if there is any feature upgradation or anything, or if you have to remove any kind of feature, going back to the C code and changing it is a very difficult task. So these kind of model integration is much more easier compared to the code integration based approach. OK, now we will see about the different stages of model based development.

OK, so the first stage is requirement elicitation and requirement analysis. OK, so requirement analysis and requirement elicitation. OK, this is a stage where your customer will give you a requirement or a problem statement. That requirement or problem statement from the customer has to be converted into a Simulink control algorithm, which should be compatible enough to be converted into a C code. OK, so this is the basis for requirement analysis and requirement elicitation. So this is the final objective. So whatever requirement your customer is giving, you have to ensure that every part of that requirement is analyzed and that is incorporated into the Simulink model.

So you need to ensure that. OK, and one of the key techniques over here is that the customer would be having a very big requirement. Basically, you cannot take a completely big requirement and then implement it just like that or try to understand it. It will be very complex to understand and analyze. So you can try to break this requirement into smaller sub features and then it can be implemented as smaller sub features. And then it can be connected together into a single model and you can save it and then you can try to generate a code out of it.

OK, so in this way, you can understand how to break your given requirement. And when you are implementing it in terms of smaller chunks in the model. Basically, as a subsystem or as any specific block, you can take a small requirement and then you can implement it. You can ensure bidirectional traceability. Bidirectional traceability means the requirement to model connect and the model to requirement connect is the link between both of them established. Okay, I have this very big requirement which is broken down into the smaller parts. Okay, whether it is correct, whether it is understandable.

So, like that you can see and that you can take it forward. So, this is with respect to the requirement analysis and requirement elicitation. So, this is the illustration that we are talking. So, the image on the left side of the screen is a chassis. Okay. So, the image on the middle where I am currently pointing my mouse at. Okay. So, this is a control algorithm problem. So, this control algorithm problem. Okay. That would be converted or given by the customer. Okay. As in the form of a flowchart or in the form of a requirement. And this requirement has to be implemented.

Instead of going and directly starting to develop a model and generate a code out of it, in order to ensure that every part of the requirement is developed, you have to make use of the Simulink requirement toolbox and you have to tag the model against the requirement. Okay. So, if the requirement is in the form of a document, any specific requirement number has to be created for it. And that particular requirement will be tagged or linked to a given subsystem or a given block in the model.

And this will be done using the Simulink requirement toolbox. So, how to do it, we will be seeing in our future lectures. Okay. So, this is a tool-based approach. Sometimes even without using the Simulink requirement toolbox, we can do a requirement tagging and traceability of a given control algorithm into a Simulink model. So, how to do it, a non-tool-based methodology, that also we will be covering in the future lectures in this program. Okay. So, this is with respect to the requirement analysis and requirement elicitation. The next one is model development. Okay. So, you have a problem. Now, the skeleton of the model is developed based on the customer-given requirement.

Okay. So, once you have developed this model, the skeleton of the model based on the customer requirement, then you will go on to fine-tune the model as per the industry standards. So, this starts with ensuring the model settings are all industry-specific or problem-specific. Okay. You have to take care of the model settings. In MATLAB Simulink, you call that as configuration parameter settings. Then whether the correct coder tool is selected, whether the MATLAB simulation properties and all are correct and it is taken care of, whether the solver settings are taken care of. So, all these things you have to ensure.

Then you have to create different signals and calibration parameters for your given model from the requirement document. Okay. So, how to create it? Assigning the correct data type for it. Everything you have to ensure. Okay. So, all of this, these Simulink signals and Simulink parameters will be created in the data dictionary. So, you have to then link your data dictionary to your model. Okay. So, once you do the complete model development as per the model-based development modeling guidelines. Okay. So, the model-based development modeling guidelines and all, few people would be following MATLAB standard automotive guidelines and also you call as MAAB.

Okay. So, using MAAB guidelines only, you do the model development that is called as MAB. Okay. And also, there is something called as JMAB. That is Japan MathWorks Automotive Advisory Board. Okay. So, in this course, we will see about the JMAB guidelines. So, using the JMAB principles only, we will be doing the complete model development. Okay. So, they are basically some modeling guidelines and modeling rules which you are going to follow here. So, after model development, at the later stage, we are going to have verification and validation followed by the code generation.

So, you have the customer-given requirement as shown on the left side of the screen. This is converted into a Simulink model and this Simulink model is basically developed as per the MAB or JMAB rules. So, in this lecture, we are going to learn about the JMAB modeling guidelines and the basic MBD modeling rules. Okay. So, and then once the model is developed, you have to simulate the model and see, you have to take the JMAB modeling guidelines related reports. Then, you have to do design verification whether the model is as per the industry-defined standards.

Okay. Certain design verification you have to take to ensure that there is no data loss coming out of it. And after that, you have to do verification and validation. And finally, you go for auto code generation. Okay. So, in verification and validation, what you will basically do is, you will write test cases. Okay. Test cases will be in the form of test harness. That test harness is going to give you some set of input values. Okay. This is again based on the functional requirement. Functional requirement is the control algorithm or the problem given by the customer.

Okay. So, based on that, only you are developing the model. And based on the same functional requirement document, you are creating the test harness. Okay. That is the set of inputs that you have to pass. You will be giving that input to both the model in loop and software in loop. So, what is model in loop and what is software in loop? We will see the complete process overview behind verification and validation also we will see. And the final result, what we are going to get is the model coverage and the code coverage part.

So, this is how you will be doing the verification and validation with respect to the model-based design. So, the major areas over here is the requirement analysis and requirement elicitation. Then it is followed by model-based development. Then it is followed by verification and validation. And finally, the auto code generation is also there. Okay. We will further break down each stage in detail in the upcoming lectures. Okay. So, this is just a teaser kind of a thing to give you a brief overview about the different stages of MBD.

Okay. What are the major advantages of model-based development? Okay. Again, most of the advantageous points we have already discussed in the same lecture earlier. We are just going to recollect these points again. Okay. They are efficient handling of the increasing system complexity, tool leverage at all the stages of model-based development, including requirement elicitation, to model development, to verification and validation. Okay. We can simulate the system under test, ensuring that the system output, okay, the model output or the code output, it matches the calculated value. Okay.

Then you can, it has a very, very close collaboration among OEMs, Tire 1 suppliers and tool vendors. OEMs are usually the car manufacturers. Tire 1 suppliers are ECU suppliers. For example, organizations, Robert Bosch, Continental and all, they are Tire 1 suppliers. OEMs are organizations like Ford or Renault-Nissan or Daimler or Mercedes-Benz. They are OEMs. And tool vendors are people like MATLAB Simulink. And apart from MATLAB Simulink, for verification, validation, requirement analysis and all, there are other third-party tools which can also be synced with MATLAB Simulink like BTC Embedded Tester, ETAS, DSPACE and so on.

Okay. And then adherence to the industry acceptable standards. So, the industry standards on the product development and software development like ASPICE and also the functional safety standards as prescribed by the ISO 26262. Okay. Model-based development basically adheres to both the ASPICE standards as well as the ISO 26262 standards. So, these are two widely adopted industry standards used across all the OEMs and Tire 1 suppliers. And even MBD is kind of considered to be a crux or core for adherence to ASPICE and ISO 26262. Okay. So, now we have come to the end of this lecture.

So, in this lecture, we saw about what model-based development is, why it is required, the different stages of model-based development and also the advantages of model-based development. And with this, we have come to the end of this lecture. Thank you.

Want the rest of Software Verification and Validation and System Testing for Model-Based Development?

Get the full course syllabus and fees.

The full course is paid (₹40,000). We'll send the syllabus and call you back within one working day.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.

Full course · paid

Unlock the full Software Verification and Validation and System Testing for Model-Based Development course

The remaining 34 lessons, mentor-reviewed projects and a certificate come with the paid course (₹40,000). Leave your details: we'll send the syllabus and fees and call you back.

Get the syllabus and fees

A counsellor calls you back within one working day.

By submitting you agree to our Terms and Privacy Policy.

Grow by Skill-Lync · free lesson

Start watching

Free, no payment. Leave your details once and every free lesson on Grow plays straight away. A Skill-Lync counsellor may call you about the full Software Verification and Validation and System Testing for Model-Based Development course.

By submitting you agree to our Terms and Privacy Policy.

Talk to a career counsellor

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.