ASPICE SYS.1 Requirements Elicitation
Get Started with This SkillOverview
Elaborate ASPICE SYS.1 work products: stakeholder needs specification and traceability from needs to sources for Automotive SPICE (VDA PAM 4.0).
Getting Started
Add your source materials to the project workspace, then activate the ASPICE SYS.1 Requirements Elicitation skill. The agent will guide you through the process step by step.
Example Conversation
You: We’re starting SYS.1 for our new ECU project. We have notes from the kick-off with the OEM and some regulatory constraints. Can you help us build the stakeholder needs specification?
Agent: I’ll help you elaborate SYS.1 work products. To structure the stakeholder needs specification I need: (1) Who are the stakeholders — OEM, Tier-1, internal functions, regulatory? (2) Do you have any existing list of needs or constraints from workshops or contracts? (3) Preferred format — table with IDs, or linked document?
You: Stakeholders are the OEM (our customer), our systems team, and we need to cover ISO 26262 and UNECE. We have a one-pager from the OEM and our internal safety checklist. Prefer a table with IDs we can trace later.
Agent: I’ve created
stakeholder-needs-specification.mdwith needs derived from the OEM one-pager and the safety checklist. Each need has a unique ID (SN-001 …), description, priority, source (OEM / ISO 26262 / UNECE / internal), and status. I’ve added a traceability table at the end linking each need to its source document or stakeholder. Shall I add a section for agreement evidence (e.g. review date and attendees) once you’ve had the alignment meeting?
Sample Output Excerpt
Below is a representative excerpt from a SYS.1 stakeholder needs specification.
Stakeholder needs specification (excerpt)
| ID | Description | Priority | Source | Status |
|---|---|---|---|---|
| SN-001 | ECU shall support OTA updates for calibration data only; no firmware OTA in Phase 1 | High | OEM SOW §3.2 | Agreed |
| SN-002 | All safety-related software shall comply with ISO 26262 ASIL-B | High | ISO 26262 | Agreed |
| SN-003 | Diagnostic data export shall comply with UNECE R156 (CSMS) | High | UNECE R156 | Draft |
| SN-004 | Max boot time from power-on to application ready: 2.5 s at −40 °C | Medium | OEM SOW §4.1 | Agreed |
Traceability (excerpt)
| Need ID | Source / stakeholder |
|---|---|
| SN-001 | OEM Statement of Work v1.2, §3.2 |
| SN-002 | ISO 26262:2018; internal safety checklist |
| SN-003 | UNECE R156; legal review 12 Jan 2025 |
| SN-004 | OEM SOW v1.2, §4.1 |
Validation
This skill does not include extension tools. Validation is performed by following the Validation checklist in the skill workflow: every need has a unique ID, description, and source; traceability is present; stakeholder agreement is documented; no placeholders left without owner or due date.