# ASPICE SWE.5 Software Integration and Integration Test

> Elaborate ASPICE SWE.5 work products: software integration strategy, integration test specification, and test results for Automotive SPICE (VDA PAM 4.0).



Tags: Automotive, ASPICE, Software Engineering, Testing


## Example Prompts

- Define the software integration strategy and test cases for SWE.5
- Record software integration test results with traceability to requirements
- Document integration order and test environment for our software

URL: https://rakenne.app/skills/aspice-swe-integration-test/index.md

Try this skill: https://rakenne.app/a/?skill=aspice-swe-integration-test



## Overview

Elaborate ASPICE SWE.5 work products: software integration strategy, integration test specification, and test results for Automotive SPICE (VDA PAM 4.0).

## Getting Started

Add your source materials to the project workspace, then activate the *ASPICE SWE.5 Software Integration and Integration Test* skill. The agent will guide you through the process step by step.

## Example Conversation

> **You:** We're ready to plan software integration and integration tests for SWE.5. We have the software architecture and software requirements. Integration order?
>
> **Agent:** I'll help you define the software integration strategy and integration test specification. I need: (1) Integration order — e.g. BSW then RTE then ASW modules (OTA, Boot, Diagnostic); (2) Test environment — host, target, or both; (3) Which software requirements are in scope for integration test.
>
> **You:** BSW → RTE → OTA, Boot, Diagnostic. We test on target (ECU). All interface requirements are in scope.
>
> **Agent:** I've created `software-integration-strategy.md` (order and environment) and `software-integration-test-specification.md` with test cases derived from interface requirements. Each case has ID, objective, preconditions, steps, expected result, and traceability to SW-REQ. I've added a results template. When you run the tests, we can fill pass/fail, date, environment; failures can link to SUP.9. Should I add a section for test environment configuration (e.g. RTE stub vs. real BSW)?

## Sample Output Excerpt

Below is a representative excerpt from a SWE.5 software integration test specification and results.

---

### Software integration test cases (excerpt)

| ID | Objective | Traceability |
|----|------------|--------------|
| SW-IT-001 | OTA receives calibration package via RTE and triggers Apply | SW-REQ-001 |
| SW-IT-002 | Boot reports application-ready within 2.5 s with all modules loaded | SW-REQ-002 |
| SW-IT-003 | Diagnostic exports data set per UNECE R156 via RTE | SW-REQ-003 |

### Software integration test results (excerpt)

| Test ID | Date | Environment | Result |
|---------|------|--------------|--------|
| SW-IT-001 | 2025-02-16 | Target (ECU) | Pass |
| SW-IT-002 | 2025-02-16 | Target, −40 °C | Pass (2.1 s) |

<!-- /excerpt -->

## Validation

This skill does not include extension tools. Validation is performed by following the **Validation** checklist in the skill workflow: integration strategy covers all software components; every integration test case traces to at least one software requirement or interface; test 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)