ASPICE SWE.1 Software Requirements Analysis
Get Started with This SkillOverview
Elaborate ASPICE SWE.1 work products: software requirements specification and traceability to system requirements for Automotive SPICE (VDA PAM 4.0).
Getting Started
Add your source materials to the project workspace, then activate the ASPICE SWE.1 Software Requirements Analysis skill. The agent will guide you through the process step by step.
Example Conversation
You: We have system requirements and system architecture baselined. Can you help us derive the software requirements for SWE.1 with traceability to system requirements?
Agent: I’ll derive software requirements from your system requirements and architecture. I need the system requirements spec and the system architecture (or at least the software-relevant elements). Should I use a prefix like SW-REQ-xxx for software requirement IDs?
You: Yes, SW-REQ-001 and up. The ECU is the only software element in our architecture.
Agent: I’ve created
software-requirements-specification.md. Each requirement has ID, description, type, priority, and verifiable acceptance criteria. The traceability matrix links each SW-REQ to the allocating system requirement(s). I’ve flagged SW-REQ-012 and SW-REQ-013 for clearer acceptance criteria so they’re testable at unit or integration level. Want me to refine those?
Sample Output Excerpt
Below is a representative excerpt from a SWE.1 software requirements specification.
Software requirements (excerpt)
| ID | Description | Type | Priority | Acceptance criteria |
|---|---|---|---|---|
| SW-REQ-001 | The software shall accept OTA calibration packages via the gateway interface and apply them after integrity check | Functional | High | Test: Provide valid/invalid package; verify apply/reject and logging. |
| SW-REQ-002 | Boot software shall reach application-ready state within 2.5 s at −40 °C (host-measured) | Non-functional | High | Test: Measure on target at −40 °C; pass if ≤ 2.5 s. |
| SW-REQ-003 | Software shall provide UDS-based diagnostic data export per UNECE R156 data set | Interface | High | Test: Request export; verify format and content per spec. |
Traceability (excerpt)
| Software requirement | System requirement(s) |
|---|---|
| SW-REQ-001 | SYS-REQ-001 |
| SW-REQ-002 | SYS-REQ-003 |
| SW-REQ-003 | SYS-REQ-004 |
Validation
This skill does not include extension tools. Validation is performed by following the Validation checklist in the skill workflow: every software requirement has unique ID, description, and acceptance criteria; traceability is complete; no conflicting requirements; all requirements are verifiable.