Good Engineering with Automotive SPICE 4.0

Dominik outlines his journey from automotive consultant to project manager at a German OEM, embracing Scrum. He covers founding his own company, continuous improvement, corporate quality, supplier support, and certifications.

Explore the escalating complexity of automotive software, from 6.5 million lines in a 787 to 100–500 million lines in modern and autonomous vehicles, connected by 100–200 ECUs and backend systems.

Explore how rising software complexity transforms automotive development, demanding agile, multi‑company collaboration, cyber and software update requirements, and shorter software life cycles, all under Automotive SPICE 4.0 process quality.

Explore the motivation to learn the purpose and basics of automotive SPICE, understand the process assessment model, the process reference model, and recognize assessor questions, practical examples, and typical pitfalls.

Explore the ASPICE 4.0 process overview, showing software engineering (SWE1–SWE6), system engineering (SYS1–SYS5), project management, and supplier monitoring in ECU development within the recommended VDA scope.

Explore the automotive SPICE process definition, detailing process id, name, purpose, outcomes, and the process reference model, with base practices, output information items, work products, and performance indicators.

Examine how Automotive SPICE 4.0 rates processes with objective evidence and interviews, using the NPLF scale, and determine level 2 prerequisites for PA 1.1, 2.1, and 2.2.

Explore automotive SPICE 4.0 project management, defining scope and lifecycle, assessing feasibility, planning work packages and resources, and monitoring progress with PDCA, earned value, and burn-up analysis.

Specify, structure, and analyze software requirements; ensure bidirectional traceability with system requirements and architecture; assess impact on the operating environment and communicate outcomes to stakeholders.

Verify integrated software against software requirements with defined verification measures, regression considerations, traceability, and communication of results under automotive SPICE 4.0.

Specify verification measures for system verification to prove conformance with system requirements. Verify the integrated system, establish traceability between results and requirements, and communicate outcomes to stakeholders.

Manage change requests end-to-end by recording, analyzing, approving, and implementing changes, while establishing bidirectional traceability to affected work products and tracking progress to closure.

Learn how to monitor and manage external contract-based suppliers with Automotive SPICE 4.0 ACQ4 by defining joint activities, exchanging information, reviewing work products, tracking progress, and correcting deviations.

Explore chapter 4 and the manage process defined as capability level 2 in Automotive SPICE 4.0. Understand why most OEMs require suppliers to cover all the generic practices.

Capability level 2 covers performance management and work product management with generic practices, focusing on planning, monitoring, resource management, and controlled work products through quality assurance and configuration management.

Apply a holistic, agile-driven framework with Automotive SPICE to secure top management commitment, define processes, tailor methods to context, train staff, and continuously improve toward quality and project success.