E-Learning Automotive SPICE® V3.1
E-Learning Automotive SPICE® – an Overview
- Reasons for the introduction of Automotive SPICE®
- Relation to other standards
- How does Automotive Spice® work?
- Example: MAN.3 project management
E-Learning Automotive SPICE® – System Engineering Processes – Development
- SYS.1: Requirements Elicitation
- SYS.2: System Requirements Analysis
- SYS.3: System Architectural Design
E-Learning Automotive SPICE® – System Engineering Processes – Integration and Test
- SYS.4: System Integration and Integration Test
- SYS.5: System Qualification Test
E-Learning Automotive SPICE® – Software Engineering Processes – Development
- SWE.1: Software Requirements Analysis
- SWE.2: Software Architectural Design
- SWE.3: Software Detailed Design and Unit Construction
E-Learning Automotive SPICE® – Software Engineering Processes – Integration and Test
- SWE.4: Software Unit Verification
- SWE.5: Software Integration and Integration Test
- SWE.6: Software Qualification Test
E-Learning Automotive SPICE® – Project Management
- MAN.3: Project Management
What Is ASPICE?
The name Automotive SPICE®, or short ASPICE, stands for “Automotive Software Process Improvement and Capability Determination”. It is a standard in the automotive industry. ASPICE is based on the current version of the ISO/IEC 330xx series and has defined its own Process Reference Model (PRM) and Process Assessment Model (PAM). The model includes processes for analyzing, evaluating, and improving system developments.
ASPICE makes a distinction between two levels: the process dimension and the maturity dimension. The maturity dimension defines – according to the ISO/IEC 330xx series – six process capability levels. These so-called capability levels cover levels from 0 to 5. In the process dimension with the current version 3.1, a total of 32 processes from all relevant areas are described. They cover the complete development process. In the VDA Scope, the German Association of the Automotive Industry (VDA) also determines highly important processes.
Why Is ASPICE Needed?
ASPICE allows structured and therefore effective work. It creates traceability in the development process and has become established as a standard. This standard is required by customers when assigning projects and is also specifically controlled during the ongoing process. This means that certification according to ASPICE is currently more or less mandatory in the automotive industry. To achieve this, companies must provide evidence of work products and have their processes authorized by auditors.
In this context, security is a highly relevant topic. In the automotive sector, IT security plays an increasingly important role. Also the product liability for security-related topics has gained in significance. ASPICE is very practical here and guarantees quality assurance. Those who develop according to ASPICE automatically fulfill numerous requirements for the IATF 16949 standard, ISO 9001, and ISO 26262.
How Is ASPICE Related to Embedded Systems?
ASPICE describes the development process of embedded systems in the automotive environment.
What Can You Learn About ASPICE in the Embedded Academy E-Learning?
The course on ASPICE is divided into several e-learning units. Each of them explains three processes. The first e-learning provides an overview on the contents of the process model. Further e-learnings describe individual specific topics, such as system engineering, requirements and design, or software development and testing.
After this e-learning, engineers understand what ASPICE is. For this, not all learning units of the course have to be completed. It is intentionally designed in such a way that users can specifically select the aspects they are interested in. Whenever different topics belong together, the e-learnings will highlight this connection. This is particularly helpful for practical application work when processes and relationships need to be understood.