Process assessments for the automotive industry.
Automotive SPICE® (ASPICE) is often used by major OEMs and Tier 1 suppliers to determine the software capabilities of their own suppliers. The risk of losing future contracts or suppliers and being forced into less profitable arrangements is a typical consequence of not achieving the required level of ASPICE.
iProcess works with Automotive SPICE® gap assessments, improvements and value driven approaches for system and software development processes.
The model can be downloaded for free at automotivespice.com.
Automotive SPICE® is registered trademark of the German Association of the Automotive Industry - Verband der Automobilindustrie e. V. (VDA).
The 6 capability levels:
Levels are building on top of each other, for example, Level 2 cannot be achieved without Level 1 being fully achieved.
The scope of
The system engineering group (SYS)
consists of processes addressing the elicitation and management of customer and internal requirements, the definition of system architecture, and the integration and testing at the system level.
The software engineering group (SWE)
contains processes addressing software requirements derived from the system requirements, the development of the corresponding software architecture and design as well as the implementation, integration, and testing of the software.
The acquisition group (ACQ)
consists of processes that are done by the customers or by the suppliers when acting as a customer for its own suppliers, when acquiring products or services.
Supporting processes (SUP)
cover processes that may be utilized by any of the other processes at various points in the lifecycle. Configuration Management, Change Management, Problem Resolution are examples of supporting processes.
The management process group (MAN)
consists of processes designed for managing the project or program, most common being Project Management and Risk Management. A subset of highly significant processes assessed within the automotive industry is known as VDA Scope.
Do we have to follow
V-cycle to be compliant?
No. The model provides guidance and best practices on „what“ needs to be achieved. The „how“ part is up to the organization, independent of the chosen development model: Agile, V model or Hybrid.