ASPICE SWE.2 Software Architectural Design

Overview

Elaborate ASPICE SWE.2 work products: software 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 SWE.2 Software Architectural Design skill. The agent will guide you through the process step by step.

Example Conversation

You: We need to document the software architecture and allocate software requirements to components for SWE.2. We have the software requirements spec and an existing module list.

Agent: I’ll set up the software architecture and allocation. Please confirm: (1) Location of the software requirements specification; (2) Software components/layers you want (e.g. BSW, ASW, application); (3) Any existing API or interface list?

You: Requirements are in software-requirements-specification.md. We use AUTOSAR — BSW, RTE, and three ASW modules: OTA, Boot, Diagnostic.

Agent: I’ve created software-architecture-specification.md with the components and their responsibilities, and software-requirement-allocation.md mapping each SW-REQ to the allocating component(s). All requirements are allocated. I’ve added the software interface specification (APIs between OTA, Boot, Diagnostic and RTE). Should I add the RTE interface to BSW (e.g. Com, NvM) as a separate section?

Sample Output Excerpt

Below is a representative excerpt from a SWE.2 software architecture and allocation.

Requirement allocation (excerpt)

Software interface (excerpt) — OTA ↔ RTE

Validation

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