ASPICE SWE.4 Software Unit Verification

Overview

Elaborate ASPICE SWE.4 work products: unit verification strategy, test specification, and verification results for Automotive SPICE (VDA PAM 4.0).

Getting Started

Add your source materials to the project workspace, then activate the ASPICE SWE.4 Software Unit Verification skill. The agent will guide you through the process step by step.

Example Conversation

You: We need to plan and document unit verification for our OTA and Boot modules (SWE.4). We have the software requirements and detailed design.

Agent: I’ll set up the unit verification strategy and test specification. Confirm: (1) Environment — host only, target, or both? (2) Coverage goals — requirement coverage, statement/branch, or both? (3) Any static analysis tool (e.g. Polyspace, Coverity) to include in verification results?

You: Host and target. We want requirement coverage and statement coverage. We run Polyspace for critical files.

Agent: I’ve created unit-verification-strategy.md (scope: OTA and Boot; host + target; requirement and statement coverage) and unit-test-specification.md with test cases derived from SW-REQ and detailed design. Each case has ID, objective, preconditions, inputs, expected result, and traceability. I’ve added a results template for test execution and a section for Polyspace results. Failed tests can link to SUP.9 problem reports. Should I add the same for the Diagnostic module when it’s ready?

Sample Output Excerpt

Below is a representative excerpt from a SWE.4 unit verification specification and results.

Unit test cases (excerpt)

Unit verification results (excerpt)

Validation

This skill does not include extension tools. Validation is performed by following the Validation checklist in the skill workflow: unit verification strategy defines scope and environment; every in-scope requirement or design element is covered; verification results are recorded with pass/fail and traceability; failed tests have defect or problem resolution references.