Lesson finished
Unlock all 37 lessons of Software Verification and Validation and System Testing for Model-Based DevelopmentFull course ₹40,000 · paid
ASPICE Process Model, Maturity Levels and SWE Stages
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: “Software Verification and Validation and System Testing for Model Based Development”
What will you learn in this free Software Verification and Validation and System Testing for Model-Based Development lesson?
The instructor introduces ASPICE, the automotive process model created by a group of European OEMs, and its primary, organizational and support process groups. The lesson explains maturity levels one to five and maps the SWE stages onto the V-model.
- What ASPICE is and who created it
- Primary, organizational and support process groups
- Capability levels from performed to optimizing
- Mapping SWE stages to the V-model
What comes after lesson 3?
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. In this session, we will be learning about the ASPICE process overview. So in the previous sessions, we learned about the software development lifecycle, different SDLC methodologies, in specific about the V-cycle or V-model in software development lifecycle and about the roles and responsibilities of different stakeholders in the V-model of software development lifecycle we extensively covered. So in this lecture, we will be covering about the ASPICE, what is ASPICE model, the complete structure of the ASPICE model we will be seeing, then the ASPICE maturity level we would be seeing, and then the different stakeholders in software engineering process group.
So software engineering process group, you call that as SWE in ASPICE. So exclusively about that and different stakeholders involved, we will see. Okay, so just going in-depth into the ASPICE, I will just try to correlate between the V-model of development to the ASPICE. So the V-cycle development or the V-model of automotive embedded software development, that is more team-specific and project-specific or application software-specific. So any team that you are working in powertrain control or ADAS features or body-controlled module or cluster in infotainment, if you have to develop an application software, you can follow the V-model of development.
So that is team-specific. Okay, so who is going to do what, which tool you are using, how long you are going to do the work, if you find a bottleneck, whom to contact, where you can go and fix it. So all that role-specific, domain-specific, tool-specific for a specific application software. It can be any application software in embedded software development. For that, we went for the V-cycle of development. Now coming back to ASPICE, ASPICE is something from a larger perspective. Okay, ASPICE stands for Automotive Software Performance Improvement and Capability Determination.
Okay, so this is a domain-specific version of ISO or IEC-15504. Okay, ASPICE basically evaluates the efficiency of embedded software development processes by the embedded software suppliers in the automotive industry. So this is the major focus of the ASPICE. And once again, ASPICE, it's not just merely restricted to the software development part. Okay, along with software development, there are multiple other stages as well. Okay, so you are not looking from the software development perspective. Rather, you are looking from a product development perspective. The product development can also be, apart from software product, there can also be other hardware products, other design products that you are associated in your vehicular manufacturing.
So all that from a complete system perspective, we are going to have a look about the ASPICE. Okay, so this is with respect to the complete ASPICE process. And then before going to look at the different process categories of ASPICE, I will also give a specific background on where and how the ASPICE was created and who initiated this ASPICE process. So where this whole ASPICE process basically started. Some of the key European OEMs, they came together to create this industry-specific process model. Okay, called as the ASPICE.
And this industry-specific process model, as I already told you, it is not just restricted to the software development, software verification and validation. In fact, it covers a completely larger picture of product development or the complete automotive product development. So it covers a complete larger picture. Okay, ASPICE model, whatever that we are calling, right? So this basically comes under the ASPICE software development initiative. Okay, so this ASPICE software development initiative was created by the Automotive Special Interest Group or SIG. So the list of European OEMs who came together, that list of European OEMs, whoever came together, they formed an Automotive Special Interest Group.
And those people in Automotive Special Interest Group basically created the framework for ASPICE model. Okay, so some of the members who are part of this Automotive SIG or Special Interest Group, they are Audi AG, BMW Motors, Daimler AG, Fiat Auto, Porsche AG, Volkswagen AG and the Volvo Corporation. Okay, and also Ford Worker GmbH or in local, you can also say that it is Ford Europe and Jaguar Land Rover. So all these people are European OEMs, European car manufacturers who came together to form the conglomeration called as Automotive Special Interest Group.
And they are considered to be kind of the fathers or more than fathers, they are considered to be the people who governed and devised this ASPICE model. Okay, so now this again is further subclassified into three major categories. Okay, so you call that as primary, organizational and supportive here. Okay, so you go to the primary, primary will have further subgroups. Okay, so who does what? Okay, so this is another very important thing. We already told that ASPICE is going to be talking things from a product development perspective.
It's not merely embedded software development. So product development means it covers a larger scale. Who is going to supply the ECU to me? Who is going to supply the wiring harness to me? If I am going to purchase any physical switch or a physical product, who is going to supply that to me? Okay, so there can be one particular part in manufacturing a simple thing, which will involve more than two suppliers. Okay, so product from supplier A and product from supplier B has to be assembled together.
Okay, the same thing can also be said about the software. Say, for example, you have a feature, okay, the powertrain development would be done by Robert Bosch. Okay, the body control module would be done by Continental. Okay, someone else like Electrobit would be working on the ADAS features. So all of these people, I mean, all the different software products, you have to take them and you have to put them and you have to make your car function. Okay, so for that, all of that certain standards and guidelines need to be followed.
Okay, so the complete product development, one such complete product development standard, which was devised by the automotive special interest group, is what you call ASPICE once again. Okay, now this you have to see. Okay, so here another major thing is that since the OEMs and Tire 1 suppliers are basically involved in this, okay, there are different benefits that it provides for both the OEMs and Tire 1 suppliers. Okay, as far as the OEMs is concerned, they will have a major control or major say in the quality of electronic and hardware products, especially when the supply chain could become very, very complex.
Okay, so this is the major advantage for the OEMs basically. Now looking at the suppliers. So what is the major benefit for the suppliers here? Okay, so they get an opportunity to be associated in really challenging market. Okay, adhering to different ASPICE standards will have them, will have it in them to have a control on the production cost repair and so on. So these are the basic advantages between the OEMs and the Tire 1 suppliers, the advantages between both. Now coming to the primary group, organizational group and the support group.
Okay, the primary group here that consists of the acquisition process group, supply process group and engineering process group. Organizational talks about the management process group, process improvement process group and reuse process group. And finally, support talks about the supporting process groups. So in this, as far as this course and ASPICE is concerned, we will just be aware of these different process groups. And in the ASPICE architecture, who does what? We will be seeing that. Okay, now we will go to the ASPICE model. So this is the complete ASPICE model that you have.
And if you can see, there are three major pillars, which it is classified as. So vertically, we will try to split this. So this, until this part, we have the primary life cycle processes or the primary process group. The next one is the organizational process group. This one and the third one is the support process group. Okay. So again, under primary process group, we told like it is further subdivided as acquisition process, supply process and engineering process. So it is again subdivided as acquisition process, supply process and then engineering process.
Engineering process is again further subdivided as system engineering and software engineering. Okay. So engineering means it's not just software, right? So even other parts of design engineering and other things are there. So all that comes under the system engineering, the process groups. Okay. So next we go for the organizational life cycle processes. So that talks about the organizational, we discussed about the management process group, process improvement. And then reuse process group. So again, you have management process group, reuse process group and process improvement process group. Finally, the supporting life cycle processes or support process group is archived here at the bottom. Now, if you can see each of these subgroups that we have, whether it be the acquisition process group or supply process group or software engineering process group or management process group, you have all of that.
Each of them have a specific name associated with it and each of them have certain IDs associated with them. Okay. For example, if you're looking at the acquisition process group, one of the IDs that they have is ACQ.3. Okay. That is contract agreement. ACQ.4 is supplier monitoring. ACQ.11 is technical requirement. ACQ.12 is legal and administrative requirements and so on. When you go to the supply process group, SPL.1 is supplier tendering. SPL.2 is product release. Okay. When we are going to the MAN process group, MAN.3 is product management. MAN.5 is risk management. MAN.6 is measurement basically. Okay.
So likewise, in each of the subgroups, we will have sub functions and sub layers. Okay. So this ASPICE model in our V cycle model or V model, whatever we discussed, that was team specific. It was very specific to that particular project team. So my ASPICE model is sitting as an umbrella over my V model. ASPICE model is complete organization specific. Okay. For example, if you're talking about an OEM means, okay, OEM, whoever is manufacturing a car, he will have multiple supplier groups associated to it, be it with respect to the software engineering or system engineering or raw material acquisition and so on.
So in order to build his car, it involves both software and hardware products, right? So right from the material procurement to the giving tenders to different people to allocation of the budget to setting up the different resources on who does what, it involves a lot of things. So people who are involved in the acquisition part. Okay. So they will all form under the acquisition process group. Next, the supply process group. So supply tendering and product release, all that comes under that. So likewise, from an OEM perspective, you will clearly associate yourself at different levels. Okay.
If you are a tier one supplier or if you are a tier two supplier, where your only role is to do some application software development, then you will restrict yourself only to that. Okay. Then you won't be covering the complete ASPICE model. You will only be restricted to the software engineering process group. Okay. So likewise, clear cut roles for the complete car manufacturing, for the complete process or product development, what are the different roles? Who are the different stakeholders? Who are the different stakeholders? And what is their roles and responsibilities? So if you are a manufacturer, for example, if you are involved in purchasing of the raw materials and other things, or if you are involved in budgeting, staffing and so on, then you will classify your work according to the ASPICE model. And then it will fall under either acquisition process group or supply process group or management process group and so on. So likewise, you will split your work and then you will do. Okay.
Okay. So this is with respect to the ASPICE model where you will fall in one among the many categories. Then you go for the ASPICE maturity levels depending on who does what. Okay. So here we saw, okay. If you are an OEM whose job is to manufacture a car, then you have to either do the complete thing. But if you are just a tire one or a tire two supplier, who is supporting the OEM in his software product development, where you are only going to involve yourself in application software development, or you are providing tools to support the application process development, then you will be only restricted to this particular software engineering process group.
Then depending on that only your maturity level would be there. Okay. So if you are an ASPICE level five, then you are at the top of the ladder. You are a master. You have taken care and ensured that at different stages of ASPICE product development, every stage you have complied to it. Okay. That's what you mean to say with ASPICE level five. Okay. So you have different names for different levels. The lower ASPICE level is called incompetence. Level one is performed. Level two is managed. Level three is established. Level four is predictable and level five is optimizing. Okay.
So ASPICE level one means you are at very, very low level of your product development and processes are kind of very meekly followed, not completely followed in this. In level two means your processes are somewhat manageable and different roles and responsibilities are identified with respect to that. Okay. When you are going for level three or established here, the process is continuously followed. And there are people who check whether these processes are being followed, not only at one level, at multiple levels of product development, you follow it, not just the software development or anything at multiple levels, you follow it and you take care of it. Okay.
Then at level four is called predictable where the metrics, whether you are correctly following it compared to the previous quarter to this quarter, how is your progress and improvement? What are your process improvement plans? So all this will fall under the predictable stage and completely foolproof process and methodology comes under the optimizing stage where you are at the top of the pile. So whatever product development, whatever product development, whatever product development, whatever product development or quality assurance or QA and whatever things that you are following here, everything is as per the complete ASPICE standards and over the period of time, you are kind of improving on whatever existing things that you have.
Okay. So all this comes under the different ASPICE maturity levels. So usually when you are a tier two supplier, you would be provided level two or level three certification by the ASPICE SIG board and other consortiums here. And when you are a top level OEM, where your company product development is going to follow the ASPICE model means that usually you would be higher up the level four and level five. Okay. So different stages of things, you have to ensure that you are following these standards and from organization to organization, you can customize your ASPICE model.
That is the advantage with ASPICE model and ASPICE product development feature. Okay. Now, since we are talking about the exclusively for embedded software development, there is a separate software engineering process group. We will see what this separate software engineering process group is that and who are the different stakeholders in software engineering process group. And we will also see how the different stakeholders in our software engineering process group, how they are kind of aligned with respect to our V model. We will also see that in this lecture. Okay. So the different stakeholders.
So in this, if you can see, there are six different stages in software engineering process group, which is SWE1, SWE2, SWE3, SWE4, SWE5 and SWE6. Okay. SWE1 is software requirement analysis. SWE2 is software architectural design. SWE3 is software detailed design and unit construction. SWE4 is software unit verification. SWE4 is software unit verification. SWE5 is software integration and integration test. And SWE6 is software qualification test. So now we will see about each and every stage of SWE1 to SWE6. We will try to correlate this with our V cycle of development.
Another interesting thing that I would like to tell here is that if you can see the structure of the ASPICE model here. So this ASPICE model is something you can just Google on the ASPICE model and you will get this image basically. Okay. So this is the ASPICE model that is globally followed. Again, I told you when you're going from organization to organization, they will adopt this model and they will try to customize it to their own needs. Okay. So, but still the stages like SWE1, SWE2, SWE3 will be taken.
But inside SWE1, inside SWE2, inside SWE3, they will basically customize from organization to organization. If you can see, okay, try to compare it with your V cycle model. Okay. This is also looking very similar to your V, right? SWE1, 2, 3, then SWE4, 5, 6. So the flow here is reminding you of your V cycle basically. So now we will see you have six different stages in it. We will try to correlate this one with the V cycle model and we will also learn about the different stakeholders who are here.
Okay. So SWE1 first, we will see. So that is software requirement analysis. So this is very similar to our requirement analysis and requirement elicitation. Okay. There we had an on-site team and an offshore team. Okay. Now here, if you can see, you will have the software requirement. We will specify what is the software requirement. We will structure and analyze the software requirement. Then after specifying, structuring, and analyzing the software requirement, we will see the kind of impact it is going to have in the operating environment, which is basically then the developed verification criteria we will develop.
And then which is followed by bidirectional traceability, ensure consistency, and communicate the agreed software requirements. So to put it in an even simpler terms, until, This stage from specify software requirements to the analyze it has on the operating environment. All this has to be done by the on-site team basically because they are the product owners and they are the algorithm owners. So they have to specify all these things. Then they will tell to the supplier or your customer that boss, this is what you have to do.
So you take the specific tools and you start the development. That's what they tell. And also in the meantime, they will define their own processes. This is how I want my model to be developed. It has to follow the ASPICE process. So in MATLAB modeling, you have to run your model advisor check for ASPICE processes. If in case your product is going to have ASPICE compliance. OK, so you have to do so for ASPICE, again, your model configuration settings and other things are different for your normal MAM or JMAM.
Comparing it with ASPICE, it will be totally different. So you have to ensure that. Then under requirement elicitation, you have to link your requirement to the model. OK, so that is there even in the V cycle. This is also expected in the ASPICE development. Then ensure consistency. So every part of requirement has to be linked at the model level. Then communicate the agreed changes. So you do a requirement elicitation, you do a requirement analysis, then you go to do requirement elicitation, you do the model to requirement mapping.
And finally, if all the requirement part is handled at the model level, then you pass this information to your corresponding on-site team that we have done this. This is what you do in software requirement analysis. Then you go to the architectural design. So here again, the work, it will start from your offshore senior architect to the development team. So it will start with developing a software architectural design. Then you will slowly add so and so features. First, the skeleton would be ready from the skeleton. You have to ensure that all the configuration parameters and model simulation settings are taken care.
Then you have to check for the ASPICE standard settings. And after that, if additionally any MAP or JMAP that is required, you even follow that. OK, once all that is done, if any issues are there, kindly correct it. And then you have to take these reports. So the bidirectional traceability part and ensure consistency part here we are talking about taking the model advisor reports. That's what you are talking about here. Then we communicate the agreed software architecture design. OK, finally, the software detailed design. So once all these things are done and taken care at the model level, then we run the design verifier.
So usually the design verifier part comes under this SWE3. OK, where you run the design verification, any design related issues that is integer overflow or dead logics or division by zero. So if any such malicious design related issues are there, that would be found out. OK, and then that should be corrected. OK, so like how you do the looping at every individual stage, even in this stage, you can go back, you can correct and then you can come back to the current stage and then you can continue.
Again, ensure bidirectional traceability, consistency and you develop software units. So the final thing over here that they are showing is develop software units. So the control algorithms in the form of a model, whatever you have designed and whether it is following all the standards or not, whatever you are doing, right, including the design verification, model in loop validation that comes at the final stage of develop software units. OK, then the software verification part, OK, then after developing the model and MIL validation and all that, once you're doing, then we go for.
So in MIL validation, we usually do the function testing. OK, then after that, you go for the code generation. After doing the code generation, we go for the static verification of the code. And then finally, we go for the software in loop validation. So that comes under the software unit verification stage where bidirectional traceability and consistency, everything has to be done. And finally, the software integration part you have to do. OK, so this stage, ideally, what you do is that it is considered to be something like a back to back testing that you do.
Both MIL and SIL, you have to compare and see whether the test results are kind of same. So that is what you do in SWE5. You start with develop software integration strategy. This includes regression testing. Then you go on to integrate software units and different software items. You select the test cases. You perform software integration test where at the final level, you ensure bidirectional traceability, ensure consistency and summarize the communication results. So this is what you do. And the final stage is the software qualification test, which usually comes after the MIL and SIL stage, something like Hill or you release it to the customer where the customer does his own validation.
So that comes under the software qualification stage. So here it again follows the you have to develop software qualification test strategy. You perform, you develop specifications for software qualification test where you select the test cases, perform integrated software testing. And at end of it, you have to ensure bidirectional traceability, consistency, and then you have to summarize and close the results. So this is the workflow as far as software qualification test is concerned. So if you can see, when you try to correlate, we already told which stage corresponds to what.
So this SWE1 corresponds to requirement elicitation and requirement analysis in my corresponding to the V model. SWE2 corresponds to the software low level design of my V model. SWE3 talks about the software high level design and model in loop validation of my V model, where in this you develop the functional test criteria, perform the functional validation, and compare the MIL results against the calculated results. If any changes are there at the model level, either at the requirement level or at the implementation level, if any changes are there, you go back and you correct it and perform the whole operation again.
Then finally, we talk about the software unit verification, where the model is converted into a code and then a static code analysis for this is done, where an other model level design verifications are also done. Okay, so once all this is done, finally, you take the software product and put it inside a loop, very similar to your model in loop, you will do a software in loop validation at the tool level, okay, using the same test cases that was used for model in loop validation. So this comes under SWE.5 stage.
And then finally, we go for the qualification test while releasing to the customer. This can either be done at the top level of your end or you release it to the customer and customer does it at his end. And once this software qualification test is completed, then he will take the software product and he will do the acceptance test and then he will further take it for his analysis, put it into the ECU and test it at the vehicle level. So this is what he will basically do.
So this is the different stages of the software qualification test. Okay. So in this lecture, in detail, we learned about what is ASPICE model and the ASPICE maturity level. Okay. So ASPICE is not restricted to just the software product development. It is covering a complete bigger picture. It talks about the complete product development over here. Okay. And who are the different stakeholders? So we saw about the ASPICE model, it about the different levels of ASPICE model. So different process groups and all we saw, how the subgroups are created, how the subgroups are classified.
Out of that, we have one such subgroup is software engineering process group and the different stakeholders in software engineering process group we saw, different stages we saw, how it is structured we saw. And then we tried to correlate between each stage of this subgroup. Each stage of software engineering process group, we tried to correlate that with our V cycle or V model of automotive embedded software development. Okay. So with this, we have come to the end of today's lecture. Thank you.