# ASPICE SWE.4 Software Unit Verification

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



Tags: Automotive, ASPICE, Software Engineering, Testing


## Example Prompts

- Plan and specify unit tests for our software units for SWE.4
- Record unit verification results with traceability to requirements
- Define unit test coverage for the software requirements

URL: https://rakenne.app/skills/aspice-swe-unit-verification/index.md

Try this skill: https://rakenne.app/a/?skill=aspice-swe-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)

| ID | Objective | Traceability |
|----|------------|--------------|
| SW-UT-001 | ValidatePackage: valid package returns OK | SW-REQ-001, ValidatePackage() |
| SW-UT-002 | ValidatePackage: invalid checksum returns ERROR | SW-REQ-001 |
| SW-UT-003 | Boot time measurement on target at −40 °C | SW-REQ-002 |

### Unit verification results (excerpt)

| Test ID | Date | Environment | Result |
|---------|------|--------------|--------|
| SW-UT-001 | 2025-02-14 | Host | Pass |
| SW-UT-002 | 2025-02-14 | Host | Pass |
| SW-UT-003 | 2025-02-14 | Target, −40 °C | Pass (2.2 s) |

<!-- /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.


---

Back to [Skill Library](https://rakenne.app/skills/index.md)