![[Image]SANEI HYTECHS](/en/shared/img/logo_w.png){kind=logo}
Towards Automotive SPICE 4.0 Support - Major differences from 3.1 to 4.0 -
2025.01.15
- Software Development
Automotive SPICE 4.0 was officially released in December 2023. Automotive SPICE is a process model that is widely used as a standardization framework for automotive software development processes.
Currently, many automotive software development companies are building and operating development processes based on Automotive SPICE 3.1, released in 2017. Each company is making continuous improvements while efficiency and improve quality of processes. As part of these improvement activities, companies are required to migrate from Automotive SPICE 3.1 to Automotive SPICE 4.0.
This article explains the main changes and process diff in Automotive SPICE 4.0.
Currently, many automotive software development companies are building and operating development processes based on Automotive SPICE 3.1, released in 2017. Each company is making continuous improvements while efficiency and improve quality of processes. As part of these improvement activities, companies are required to migrate from Automotive SPICE 3.1 to Automotive SPICE 4.0.
This article explains the main changes and process diff in Automotive SPICE 4.0.
INDEX
- What is Automotive SPICE?
- What is Automotive SPICE 4.0? Overview and benefits
- Major changes from Automotive SPICE 3.1 to Automotive SPICE 4.0
- Major diff between Automotive SPICE 3.1 and Automotive SPICE 4.0: "Process Reference Model"
- Major diff between Automotive SPICE 3.1 and Automotive SPICE 4.0: "Process Attributes"
- Changes from Automotive SPICE 3.1 to Automotive SPICE 4.0: Let's dig deeper look at SWE.2 software architecture design
What is Automotive SPICE?
Automotive SPICE (A-SPICE) is an international standard for evaluating software development processes in the automotive industry. SPICE stands for "Software Process Improvement and Capability dEtermination" and provides a framework for evaluating and improving the maturity of software development processes. It is used as a tool for quantitatively evaluating an organization's software development capabilities and setting improvement goals.
We have previously explained Automotive SPICE on our blog, so please take a look.
■ What is Automotive SPICE (A-SPICE)?
We have previously explained Automotive SPICE on our blog, so please take a look.
■ What is Automotive SPICE (A-SPICE)?
What is Automotive SPICE 4.0? Overview and benefits
Automotive SPICE 4.0 is a standard that adds new functions and requirements to the previous 3.1 standard in order to respond to the increasing sophistication of software in the automotive industry. Automotive SPICE 4.0 strengthens areas such as the development of complex algorithms using machine learning and close cooperation between software and hardware, which were not fully covered in the previous standard. This makes it possible to evaluate more complex software development processes.
Major changes from Automotive SPICE 3.1 to Automotive SPICE 4.0
Major changes from Automotive SPICE 3.1 to Automotive SPICE 4.0 are as follows:
For more detailed changes, please refer to the official Automotive SPICE document.
The official Automotive SPICE document can be downloaded from the VDA QMC site.
- Addition of Machine Learning Engineering Process Group (MLE: Machine Learning Engineering)
- Addition of Hardware Engineering Process Group (HWE: HardWare Engineering)
- Addition of Validation Process Group (VAL: VALidation)
For more detailed changes, please refer to the official Automotive SPICE document.
The official Automotive SPICE document can be downloaded from the VDA QMC site.
This time, let's look at the main changes made to the "Process Reference Model" and "Process Attributes" in the upgrade.
Main differences between Automotive SPICE 3.1 and Automotive SPICE 4.0: "Process Reference Model"
In the table below, the differences between the process groups/processes in Automotive SPICE 3.1 and Automotive SPICE 4.0 are shown in red.
Automotive SPICE 3.1 and Automotive SPICE 4.0 Process Groups/Process List
| Automotive SPICE 3.1 | Automotive SPICE 4.0 |
|---|---|
| Acquisition process group (ACQ) | Acquisition process group (ACQ) |
| ACQ.3 Contract Agreement | ー |
| ACQ.4 Supplier Monitoring | ACQ.4 Supplier Monitoring |
| ACQ.11 Technical Requirements | ー |
| ACQ.12 Legal and Administrative Requirements | ー |
| ACQ.13 Project Requirements | ー |
| ACQ.14 Request for Proposals | ー |
| ACQ.15 Supplier Qualification | ー |
| Supply process group (SPL) | Supply process group (SPL) |
| SPL.1 Supplier Tendering | ー |
| SPL.2 Product Release | SPL.2 Product Release |
| System engineering process group (SYS) | System engineering process group (SYS) |
| SYS.1 Requirements Elicitation | SYS.1 Requirements Elicitation |
| SYS.2 System Requirements Analysis | SYS.2 System Requirements Analysis |
| SYS.3 System Architectural Design | SYS.3 System Architectural Design |
| System Integration and Integration Test | System Integration and Integration Verification |
| SYS.5 System Qualification Test | SYS.5 System Verification |
| Software engineering process group (SWE) | Software engineering process group (SWE) |
| SWE.1 Software Requirements Analysis | SWE.1 Software Requirements Analysis |
| SWE.2 Software Architectural Design | SWE.2 Software Architectural Design |
| SWE.3 Software Detailed Design and Unit Construction | SWE.3 Software Detailed Design and Unit Construction |
| SWE.4 Software Unit Verification | SWE.4 Software Unit Verification |
| SWE.5 Software Integration and Integration Test | SWE.5 Software Component Verification and Integration Verification |
| SWE.6 Software Qualification Test | SWE.6 Software Verification |
| ー | Validation process group (VAL) |
| ー | VAL.1 Validation |
| ー | Machine Learning Engineering process group (MLE) |
| ー | MLE.1 Machine Learning Requirements Analysis |
| ー | MLE.2 Machine Learning Architecture |
| ー | MLE.3 Machine Learning Training |
| ー | MLE.4 Machine Learning Model Testing |
| ー | Hardware Engineering process group (HWE) |
| ー | HWE.1 Hardware Requirements Analysis |
| ー | HWE.2 Hardware Design |
| ー | HWE.3 Verification against Hardware Design |
| ー | HWE.4 Verification against Hardware Requirements |
| Supporting process group (SUP) | Supporting process group (SUP) |
| SUP.1 Quality Assurance | SUP.1 Quality Assurance |
| SUP.2 Verification | ー |
| SUP.4 Joint Review | ー |
| SUP.7 Documentation | ー |
| SUP.8 Configuration Management | SUP.8 Configuration Management |
| SUP.9 Problem Resolution Management | SUP.9 Problem Resolution Management |
| SUP.10 Change Request Management | SUP.10 Change Request Management |
| ー | SUP.11 Machine Learning Data Management |
| Management process group (MAN) | Management process group (MAN) |
| MAN.3 Project Management | MAN.3 Project Management |
| MAN.5 Risk Management | MAN.5 Risk Management |
| MAN.6 Measurement | MAN.6 Measurement |
| Process improvement process group (PIM) | Process improvement process group (PIM) |
| PIM.3 Process Improvement | PIM.3 Process Improvement |
| Reuse process group (REU) | Reuse process group (REU) |
| REU.2 Reuse Program Management | REU.2 Management of Products for Reuse |
Major changes of Process reference model
Addition of Hardware Engineering Process Group (HWE)
Automotive SPICE 3.1 was a development process framework centered on software, but Automotive SPICE 4.0 has added the new "Hardware Engineering Process Group (HWE)". This has enabled it to evolve into a framework that includes higher-layer development such as product development and system development. This can also be read in the "From Reuse Program Management to Product Reuse Management" and "Addition of Validation Process Group (VAL)" described below.
From "Reuse Program Management" to "Product Reuse Management"
The process defined as "REU.2 Reuse Program Management" in Automotive SPICE 3.1 has been renamed to "REU.2 Product Reuse Management" in Automotive SPICE 4.0.
Addition of Validation Process Group (VAL)
Automotive SPICE 4.0 has newly added the "Validation Process Group (VAL)".
The validation of the final product is positioned as an important part of the process, and quality of product has strengthed.
The validation of the final product is positioned as an important part of the process, and quality of product has strengthed.
Addition of Machine Learning Engineering Process Group (MLE)
Automotive SPICE 4.0 has newly added the "Machine Learning Engineering Process Group (MLE)" that supports machine learning.
In addition, "SUP.11 Machine Learning Data Management" has been added to the "Support Process Group (SUP)".
This makes it possible to support projects that utilize AI technology.
In addition, "SUP.11 Machine Learning Data Management" has been added to the "Support Process Group (SUP)".
This makes it possible to support projects that utilize AI technology.
Significant shrinkage of some process groups
In Automotive SPICE 4.0, the Acquisition Process Group (ACQ), Supply Process Group (SPL), and Support Process Group (SUP) have been significantly shrunk.
Changes in process names and content
Although the process IDs are the same as those in Automotive SPICE 3.1, there are many cases where the process names have been changed.
Even in processes that appear to have not changed, some changes in all process have been made to their specific content (deliverables, base practices, etc.).
Even in processes that appear to have not changed, some changes in all process have been made to their specific content (deliverables, base practices, etc.).
Main differences between Automotive SPICE 3.1 and Automotive SPICE 4.0: Process attributes
In the table below, the differences in process capability levels/process attributes between Automotive SPICE 3.1 and Automotive SPICE 4.0 are shown in red.
Automotive SPICE 3.1 and Automotive SPICE 4.0 Process Capability Levels/Process Attributes List
| Automotive SPICE 3.1 | Automotive SPICE 4.0 |
|---|---|
| Process capability Level 1: Performed process | Process capability Level 1: Performed process |
| PA 1.1 Process performance process attribute | PA 1.1 Process performance process attribute |
| Process capability Level 2: Managed process | Process capability Level 2: Managed process |
| PA 2.1 Performance management process attribute | PA 2.1 Process performance management process attribute |
| PA 2.2 Work product management process attribute | PA 2.2 Work product management process attribute |
| Process capability Level 3: Established process | Process capability Level 3: Established process |
| PA 3.1 Process definition process attribute | PA 3.1 Process definition process attribute |
| PA 3.2 Process deployment process attribute | PA 3.2 Process deployment process attribute |
| Process capability Level 4: Predictable process | Process capability Level 4: Predictable process |
| PA 4.1 Quantitative analysis process attribute | PA 4.1 Quantitative analysis process attribute |
| PA 4.2 Quantitative control process attribute | PA 4.2 Quantitative control process attribute |
| Process capability Level 5: Innovating process | Process capability Level 5: Innovating process |
| PA 5.1 Process innovation process attribute | PA 5.1 Process innovation process attribute |
| PA 5.2 Process innovation implementation process attribute | PA 5.2 Process innovation implementation process attribute |
* PA：Process Attribute
Major changes of Process attributes
Automotive SPICE 4.0 has only one change in the process attribute names.
Changes to the specific content of Process attributes
In addition, there have been changes overall to the content of process attributes, as same as to process reference models.
Change point from Automotive SPICE 3.1 to Automotive SPICE 4.0: A deep dive into SWE.2 software architecture design.
With the release of Automotive SPICE 4.0, major changes have been made to "SWE.2 Software Architecture Design".
While there are no changes to the process IDs or process names, there have been many revisions to the specific content.
However, the impact on practical work is not expected to be significant.
Here, we will use "SWE.2 Software Architecture Design" as an example to see what changes have occurred between Automotive SPICE 3.1 and Automotive SPICE 4.0.
While there are no changes to the process IDs or process names, there have been many revisions to the specific content.
However, the impact on practical work is not expected to be significant.
Here, we will use "SWE.2 Software Architecture Design" as an example to see what changes have occurred between Automotive SPICE 3.1 and Automotive SPICE 4.0.
In Automotive SPICE 3.1, it was defined as an "Output work products", but in Automotive SPICE 4.0, this has been changed to "Output information items". Automotive SPICE 4.0 Annex B also changed the wording from "Work product characteristics" to "Information item characteristics". Information item and their characteristics are defined as indicators of "what to look at" when investigating work products. For example, when evaluating a design specification which is a work product, as characteristics on one of information item "Software Architecture" have been prepared "how the architecture was arrived at", "rationale for the programming language", "definitions of classes and methods". These characteristics are used as objective evidence to prove the evaluation of the process. In Automotive SPICE 4.0, this information is considered to be important, and it is believed that the changes have been made to focus on this.
Changes to Base Practices
Significant changes have been made to the Base Practices (BPs) in many processes, including SWE.2. The serial numbers of the Base Practices are different from the process IDs and are not compatible between the old and new versions.
The titles of the Base Practices in the old and new versions can be found in the table below.
The titles of the Base Practices in the old and new versions can be found in the table below.
List of Base Practices in Automotive SPICE 3.1 and Automotive SPICE 4.0
| Automotive SPICE 3.1 | Automotive SPICE 4.0 |
|---|---|
| BP1: Develop software architectural design. | BP1: Specify static aspects of the software architecture. |
| BP2: Allocate software requirements. | BP2: Specify dynamic aspects of the software architecture. |
| BP3: Define interfaces of software elements. | BP3: Analyze software architecture. |
| BP4: Describe dynamic behavior. | BP4: Ensure consistency and establish bidirectional traceability. |
| BP5: Define resource consumption objectives. | BP5: Communicate agreed software architecture. |
| BP6: Evaluate alternative software architectures. | ー |
| BP7: Establish bidirectional traceability. | ー |
| BP8: Ensure consistency. | ー |
| BP9: Communicate agreed software architectural design. | ー |
Mergers and Abolitions of Basic Practices
In Automotive SPICE 4.0, the Mergers and Abolitions image is as follows.
Comparison table of Basic Practices between Automotive SPICE 3.1 and Automotive SPICE 4.0
Major changes
BP3 Supporting project estimates through software architecture analysis
Automotive SPICE 4.0 BP3 now requires "analysis of software architecture" to support project estimates in project management.
*We interpret this analysis as "analysis for monitoring the content of the estimate" rather than "analysis for estimating."
*We interpret this analysis as "analysis for monitoring the content of the estimate" rather than "analysis for estimating."
Bidirectional traceability and verification of non-functional requirements
Automotive SPICE 4.0 BP4 requires bidirectional traceability as before, and also includes verification of non-functional requirements that cannot be traced from the software architecture design.
Actual impact in SWE.2
Although there are no major changes in meaning, Automotive SPICE 4.0 formally clarifies some details that were not clear until now, while some items have been deleted.
To understand these differences, we recommend that you download the Automotive SPICE 4.0 document from the VDA QMC official website and check the details.
To understand these differences, we recommend that you download the Automotive SPICE 4.0 document from the VDA QMC official website and check the details.
For a smooth transition to Automotive SPICE 4.0
The introduction of Automotive SPICE 4.0 is not just a version upgrade, but a transition to a new stage in automotive software development.In this article, we have confirmed the main changes in Automotive SPICE 4.0 and detailed differences focusing on specific processes. We hope that this content will be helpful for those who are considering migrating to Automotive SPICE 4.0.
In addition, We have a long track record in AUTOSAR MCAL development, taking advantage of our extensive experience in automotive software development. Please consider our consistent automotive MCAL development services from design to verification.
In addition, We have a long track record in AUTOSAR MCAL development, taking advantage of our extensive experience in automotive software development. Please consider our consistent automotive MCAL development services from design to verification.
Business Activities Software Development Automotive Software Development AUTOSAR MCAL Development