ASPICE SYS.2 System Requirements Analysis
Get Started with This SkillOverview
Elaborate ASPICE SYS.2 work products: system requirements specification and traceability to stakeholder needs for Automotive SPICE (VDA PAM 4.0).
Getting Started
Add your source materials to the project workspace, then activate the ASPICE SYS.2 System Requirements Analysis skill. The agent will guide you through the process step by step.
Example Conversation
You: We have our SYS.1 stakeholder needs baselined. Can you help us derive the system requirements specification for SYS.2 with traceability?
Agent: I’ll derive system requirements from your stakeholder needs. I need the baselined stakeholder needs document and any interface or constraint docs. Should I use your existing ID scheme (e.g. SYS-REQ-xxx) or create one?
You: Use SYS-REQ-001 and up. We have the needs in stakeholder-needs-specification.md.
Agent: I’ve created
system-requirements-specification.md. Each system requirement has an ID, description, type (functional / non-functional / interface), priority, and verifiable acceptance criteria. The traceability matrix links each SYS-REQ to the source stakeholder need(s). I’ve flagged SYS-REQ-007 and SYS-REQ-008 as needing clearer acceptance criteria so they’re testable. Should I refine those two?
Sample Output Excerpt
Below is a representative excerpt from a SYS.2 system requirements specification.
System requirements (excerpt)
| ID | Description | Type | Priority | Acceptance criteria |
|---|---|---|---|---|
| SYS-REQ-001 | The system shall support calibration data update via OTA; firmware OTA out of scope for Phase 1 | Functional | High | Test: Trigger OTA for calibration package; verify ECU accepts and applies; no firmware change. |
| SYS-REQ-002 | Safety-related software elements shall be developed to ISO 26262 ASIL-B | Non-functional | High | Evidence: Safety case and ASIL-B development process attestation. |
| SYS-REQ-003 | Boot time from power-on to application ready shall be ≤ 2.5 s at −40 °C | Non-functional | Medium | Test: Measure at −40 °C in climate chamber; pass if ≤ 2.5 s. |
Traceability (excerpt)
| System requirement | Stakeholder need(s) |
|---|---|
| SYS-REQ-001 | SN-001 |
| SYS-REQ-002 | SN-002 |
| SYS-REQ-003 | SN-004 |
Validation
This skill does not include extension tools. Validation is performed by following the Validation checklist in the skill workflow: every system requirement has unique ID, description, and acceptance criteria; traceability is complete; no conflicting requirements without resolution; all requirements are verifiable.