Back to All Training Tracks
ISO/IEC 15288 & Automotive SPICE 4.0Systems Engineering 5 Weeks

Automotive Systems Engineering & ASPICE v4.0

Master the V-Model: SYS.1 through SYS.5, SWE.1 through SWE.6, bidirectional traceability, change management, and how to successfully lead an organization through an ASPICE Level 2/3 audit.

Launch Visual Simulator ↓ Open Trace Studio (DOORS Alt)
Production Vehicle Architectural Blueprint

ASPICE v4.0 Systems Engineering V-Model & Full Traceability Architecture

Decomposition from SYS.1 down to target silicon, and qualification up to SYS.5 with 100% MC/DC verification.

ASPICE v4.0 Level 3SYS.1 - SYS.5SWE.1 - SWE.6100% Traceability
ASPICE v4.0 Systems Engineering V-Model & Full Traceability Architecture
OFFICIAL AUTOSYS TECHNICAL CAD BLUEPRINT
Hands-On Engineering Practice

Interactive Domain Laboratory & Case Studies

Complete each stage interactively with visual architectural schematics, case studies, and voice dictation.

Automotive SPICE v4.0 Engineering Laboratory

Systems V-Model Engineering & Audit Mastery

From Stakeholder Requirements (SYS.1) to Vehicle System Qualification (SYS.5). Master bidirectional traceability, unit MC/DC code coverage, and lead successful Level 2/3 OEM assessments.

System Item:
ASPICE SYS.2 System Requirements Analysis

Specifying Testable & Measurable System Requirements

Deliverable: System Requirements Specification (SyRS)
Poor Customer Requirement (Rejected by Assessor):

“The Battery Management System should measure cell voltages quickly and disconnect if things get too hot.”

ASPICE SYS.2 Compliant Requirement:

“The BMS ECU shall sample all 96 lithium-ion cell voltages at ≥ 100 Hz with measurement resolution ≤ 1.5 mV and trigger main contactor isolation within 20 ms if any cell temperature exceeds 60.0°C.”

ASPICE v4.0 Systems Engineering V-Model and Traceability
ASPICE v4.0 V-MODEL & BIDIRECTIONAL TRACEABILITY ARCHITECTURELEVEL 3 AUDIT READY
Full Lifecycle Traceability: SYS.1–SYS.5 down to SWE.1–SWE.6 with 100% MC/DC verification linkage.ASPICE v4.0 Compliance
Trainee Lab Exercise: Defend Bidirectional TraceabilitySpeak or Type your response

Question: During an ASPICE Level 2 assessment, an OEM auditor asks you to demonstrate bidirectional traceability between System Requirement SYS-REQ-101 and its verification in SYS.5. What two traceability links must you prove?

Stage 1 of 7
Interactive ASPICE v4.0 V-Model

Automotive V-Model & Bilateral Traceability Explorer

Click any engineering process node to view required work products, base practices, and OEM audit questions.

Left Side: Design & SpecificationRight Side: Verification & Testing
SYS.2System Requirements Analysis
Trace Partner: SYS.5
Mandatory Base Practices (BP):
  • Specify system requirements
  • Structure and prioritize requirements
  • Analyze feasibility
Mandatory Work Products (Outputs):
📄 System Requirements Specification (SyRS)📄 Verification Criteria
Common OEM Assessor Audit Question:

“Can you demonstrate bidirectional traceability from SYS.2 requirements to SYS.5 test cases?”

ASPICE Level 2 requires formal bidirectional trace verification between SYS.2 and SYS.5.
Interactive Visual Masterclass🎙️ NotebookLM Multi-Speaker Engine● Daily Stacked Episode #1

ASPICE v4.0: Mastering the V-Model, SYS.1 to SYS.5 & Assessor Audits

Featuring Dr. Aris Thorne (Senior Safety Fellow) & Elena Vance (Principal Safety Assessor) · Added 2026-10-01 · 25 mins

ASPICE v4.0: Mastering the V-Model, SYS.1 to SYS.5 & Assessor Audits
VEHICLE CAD ARCHITECTURE
AT
Dr. Aris Thorne
Senior Safety Fellow
·
EV
Elena Vance
Principal Assessor
Dr. Aris Thorne(Senior Safety Fellow)

Elena, when an OEM audits a Tier-1 supplier for ASPICE Level 2 or Level 3, what is the single most common failure that leads to a non-conformance finding?

Elena Vance(Principal Safety Assessor)

Without question: Bidirectional Traceability. An engineer has a great system requirement in SYS.2, but when I ask to see the test case in SYS.5 that verifies it, there is no direct link. Or worse, there is a test case in SYS.5, but no one knows which system requirement it traces back to—it's an orphan test case. In ASPICE v4.0, if you have broken traceability links, your process capability drops to Level 1 immediately.

Dr. Aris Thorne(Senior Safety Fellow)

How should an engineer maintain clean traceability across Jira, DOORS, and Git repositories?

Elena Vance(Principal Safety Assessor)

You use formal unique identifiers—like SYS_REQ_012 linked to SWE_REQ_045 linked to TC_SYS5_012. You maintain a Traceability Matrix, and every release baseline must include a Traceability Completeness report showing 100% coverage with zero unlinked requirements.

Line 1 of 425% Complete
ASPICE v4.0: Mastering the V-Model, SYS.1 to SYS.5 & Assessor Audits

Understand how Automotive SPICE v4.0 evaluates engineering capability. Learn how to establish bulletproof bidirectional traceability from SYS.1 down to SWE.3 and back up through SYS.5 verification.

Stacked Masterclass Series (3)Daily Cadence
Hardware & Software Interfaces
SYS.2 System Requirements
Atomic specifications allocating functional behavior to domain controllers.
SWE.3 MISRA C Construction
Implementation complying with coding standards with zero unreviewed deviations.
SWE.4 Unit Verification
Structural testing achieving 100% statement, branch, and MC/DC coverage.
SYS.5 System Qualification
Testing complete vehicle functionality against original customer specifications.
Independent Engineering Takeaways
  • The engineering process group: SYS.1, SYS.2, SYS.3, SWE.1, SWE.2, SWE.3, SWE.4, SWE.5, SWE.6, SYS.4, SYS.5
  • Why 'Bidirectional Traceability' is the number one cause of non-conformance findings during OEM audits
  • Preparing work product baselines and engineering change management for Level 2/3 assessments
Detailed Knowledge Repository

Engineering Curriculum & Standards Guidance

1. The Automotive V-Model & Process Areas

From Stakeholder Requirements (SYS.1) to Vehicle System Integration (SYS.5)

ASPICE defines the standard process assessment model utilized by all major automotive OEMs (BMW, VW, Mercedes, GM, Ford).

Left side of the V: SYS.1 Requirements Elicitation, SYS.2 System Requirements Analysis, SYS.3 System Architecture Design, SWE.1 Software Requirements, SWE.2 Software Architectural Design, SWE.3 Detailed Design.

Right side of the V: SWE.4 Unit Verification, SWE.5 Software Integration, SWE.6 Software Qualification, SYS.4 System Integration, SYS.5 System Qualification.

Core Architectural Takeaways

  • Bidirectional traceability between left-hand specifications and right-hand test cases is mandatory for ASPICE Level 2.
  • Every requirement must be verifiable and testable.

OEM & Tier-1 Technical Interview Guidance

Interview Question: What is the difference between Verification and Validation in ASPICE?

Winning Answer: Verification confirms that a work product meets its specified requirements ('Did we build the system right?'). Validation confirms that the system fulfills its intended operational use in the vehicle ('Did we build the right system?').

AutoSys Professional Certification

Earn Your Accredited Automotive Credential

Register for a free learner account to save your lab progress, unlock downloadable templates (HARA Excel sheets, FMEDA calculators, GSN safety case templates), and earn your verified completion certificate.

Register as Learner →Hands-on Tool Practice