# ASPICE SYS.4 System Integration and Integration Test

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



Tags: Automotive, ASPICE, Systems Engineering, Testing


## Example Prompts

- Define the system integration strategy and test cases for SYS.4
- Record integration test results with traceability to requirements
- Document integration order and test environment for our system

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

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



## Overview

Elaborate ASPICE SYS.4 work products: 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 SYS.4 System Integration and Integration Test* skill. The agent will guide you through the process step by step.

## Example Conversation

> **You:** We're ready to plan system integration and integration tests for SYS.4. We have the system architecture and system requirements. Where do we start?
>
> **Agent:** I'll help you define the integration strategy and integration test specification. I need: (1) Preferred integration order — e.g. bottom-up (sensors/actuators first, then ECU), or top-down; (2) Test environment — HIL, vehicle, or both; (3) Which system requirements are in scope for integration test.
>
> **You:** Bottom-up. We have a HIL bench and will do a final run in vehicle. All SYS-REQ that touch interfaces are in scope.
>
> **Agent:** I've created `integration-strategy.md` (order: radar + camera + gateway integration with ECU on HIL, then full system in vehicle) and `integration-test-specification.md` with test cases derived from the interface requirements. Each test case has an ID, objective, preconditions, steps, expected result, and traceability to SYS-REQ. I've added a results template — when you run the tests, we can fill pass/fail, date, and environment. Should I add a section for defect IDs linking to SUP.9?

## Sample Output Excerpt

Below is a representative excerpt from a SYS.4 integration test specification and results.

---

### Integration test cases (excerpt)

| ID | Objective | Preconditions | Traceability |
|----|------------|---------------|--------------|
| SYS-IT-001 | Verify ECU receives object list from radar on CAN | HIL: radar + ECU connected; radar sim active | SYS-REQ-006 |
| SYS-IT-002 | Verify boot time with all elements connected | Full system on HIL at −40 °C | SYS-REQ-003 |
| SYS-IT-003 | Verify OTA calibration update path ECU–gateway | HIL: gateway + ECU; OTA server sim | SYS-REQ-001 |

### Integration test results (excerpt)

| Test ID | Date | Environment | Result | Note |
|---------|------|--------------|--------|------|
| SYS-IT-001 | 2025-02-10 | HIL | Pass | — |
| SYS-IT-002 | 2025-02-12 | HIL | Fail | 2.8 s measured; defect PR-044 |

<!-- /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 elements and defines order and environment; every integration test case traces to at least one system 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)