ASPICE SYS.3 System Architectural Design

Overview

Elaborate ASPICE SYS.3 work products: system architecture, requirement allocation, and interface specifications for Automotive SPICE (VDA PAM 4.0).

Getting Started

Add your source materials to the project workspace, then activate the ASPICE SYS.3 System Architectural Design skill. The agent will guide you through the process step by step.

Example Conversation

You: We need to document the system architecture and allocate system requirements to elements for SYS.3. We have the system requirements spec and a block diagram from the last design review.

Agent: I’ll set up the system architecture and allocation. Please confirm: (1) Location of the system requirements specification; (2) System elements you want (e.g. ECU, sensors, actuators, offboard); (3) Any existing interface list or only the block diagram?

You: Requirements are in system-requirements-specification.md. Elements are ECU (main), radar, camera, and gateway. We have a draft interface list in Confluence — I’ll paste it into the workspace.

Agent: I’ve created system-architecture-specification.md with the four elements and their responsibilities, and requirement-allocation-matrix.md mapping each SYS-REQ to the allocating element(s). All requirements are allocated; SYS-REQ-005 is split between ECU and gateway. I’ve added the interface specification for ECU–radar, ECU–camera, and ECU–gateway with signals and protocols. Can you confirm the gateway interface timing constraints so I can complete the interface spec?

Sample Output Excerpt

Below is a representative excerpt from a SYS.3 system architecture and allocation.

Requirement allocation (excerpt)

Interface specification (excerpt) — ECU ↔ Radar

Validation

This skill does not include extension tools. Validation is performed by following the Validation checklist in the skill workflow: every system requirement is allocated to at least one element; all interfaces between elements are specified; traceability is documented.