ASPICE SWE.1 Software Requirements Analysis

SWE.1 is the top-left of the software V. Get the software requirements — and their traceability and verification criteria — right here, and everything downstream has something solid to trace to.

Purpose (per the ASPICE PAM): transform the software-related parts of the system requirements into a set of software requirements.

The process is achieved when these outcomes hold:

The output work products SWE.1 asks for (named per the standard):

This is where the standard meets reality. Each work product and outcome has a concrete home — an issue type, work-item type, or model element — in the tools you already run. Types are configurable, so treat this as the typical ASPICE setup:

The trap isn't the tools — it's that the links between them are maintained by hand and decay the moment a requirement changes. (See best ASPICE tools.)

Here is the part almost everyone misses. SWE.1 can never reach a mature capability level (CL2+) on its own — it can only be as mature as the configuration-management data model underneath it. SUP.8 Configuration Management is the secret enabling layer: the shared data model of items, versions, baselines and links that is the basis on which every other process group becomes provable. Scatter that data model across a Jira project, a Polarion space, a DOORS module, an EA model and a Confluence tree, and the model is fragmented by construction — the traceability that SWE.1 depends on decays the moment anything changes, and no amount of process ceremony fixes it.

What actually unlocks maturity is a headless ALM — an API-first, tool-agnostic configuration-management data model that is the single source of truth for every work product and every link, readable and writable by both humans and agents — plus an agent/human workflow definition, coordination and traceability platform on top of it, so every change is planned, assigned (to a human or an agent), executed and traced against that one model. That is the layer that lets SWE.1 be mature instead of theatrical.

ASPICE deliberately gives you no blueprint. So we wrote one. This SWE.1 guide is part of The Blueprint — our free, open template QMS for ASPICE: every VDA-scope process area, its outcomes and work products, mapped to concrete artifacts in your tools and grounded in one configuration-management data model. Take it, use it, no cost.

Agents read the system requirements and the code, derive the software requirements with verification criteria, and generate the SYS.2 ↔ SWE.1 traceability — each link with a confidence score, low-confidence ones flagged for a human. And we offer to implement The Blueprint for you: our agentic solutions (Vera generates SWE.1's work products and traceability as a byproduct of the build, each with a confidence score and audit trail) running on a partner headless ALM — the API-first configuration-management data model that makes the whole thing provable.