Browse Skills

ASPICE SWE.5 Software Integration and Integration Test

    Get Started with This Skill

    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)

    IDObjectiveTraceability
    SW-IT-001OTA receives calibration package via RTE and triggers ApplySW-REQ-001
    SW-IT-002Boot reports application-ready within 2.5 s with all modules loadedSW-REQ-002
    SW-IT-003Diagnostic exports data set per UNECE R156 via RTESW-REQ-003

    Software integration test results (excerpt)

    Test IDDateEnvironmentResult
    SW-IT-0012025-02-16Target (ECU)Pass
    SW-IT-0022025-02-16Target, −40 °CPass (2.1 s)

    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.

    Ready to let your expertise drive the workflow?

    Stop wrestling with rigid templates and complex tooling. Write your process in markdown, let the agent handle the rest.

    Get Started