ASPICE refuses to give you a blueprint. So we wrote one. Every VDA-scope process area — outcomes, work products, and the concrete tool artifacts they map to — grounded in one configuration-management data model.
The Blueprint is our free, open template QMS for ASPICE: one page per VDA-scope process area (SYS.1–5, SWE.1–6, SUP.1/8/9/10, MAN.3, ACQ.4), each mapping the standard's process outcomes and work products to concrete artifacts and issue types in the tools you already run — Jira, Polarion, Codebeamer, DOORS Next, Enterprise Architect, Confluence — all grounded in one configuration-management data model. Take it and implement it yourself, or have us implement it with our agentic solutions on a partner headless ALM.
ASPICE's original sin: there is no official blueprint anywhere — it grades you against a checklist and refuses to tell you how to build the thing. The Blueprint is our answer. Each page below takes one process area, states its purpose and process outcomes from the standard, lists its work products, and — the part nobody else publishes — maps every work product to the concrete issue type, work-item type or model element it becomes in your actual tools. All of it grounded in the configuration-management data model, the enabling layer that caps every process's maturity. Free to use. We also implement it with agents.
Gather, agree and track evolving stakeholder requirements — the top of the V.
Stakeholder requirements → analysed, verifiable system requirements.
System architecture, requirement allocation, interfaces — traced to SYS.2.
Integrate system items; test interfaces & interactions vs the system architecture.
System requirements → software requirements, with verification criteria and traceability.
Software architecture, requirement allocation, interfaces — traced to SWE.1.
Detailed design + the software units (code), traced to architecture.
Verify units against the detailed design — static analysis + unit test, traced.
Integrate units into the software; test interfaces & interactions vs architecture.
Confirm the integrated software meets the software requirements (SWE.1).
The enabling layer — the CM data model every other process is capped by.
Independent assurance that work products and processes comply — non-conformances tracked.
Identify, analyse, track and close problems — with cause, impact and trends.
Record, impact-assess, approve and track changes — traced to affected work products.
Control the release: content, build from CIs, release notes, approval, delivery.
The VDA scope is the set of process areas German OEMs typically assess in a plug-in/VDA assessment: SYS.1–SYS.5 (system engineering), SWE.1–SWE.6 (software engineering), and the supporting/management processes SUP.1, SUP.8, SUP.9, SUP.10, MAN.3, and ACQ.4.
Yes. The Blueprint is a free, open template QMS: every VDA-scope process area mapped to its work products and the concrete tool artifacts they become, grounded in the configuration-management data model. You can implement it yourself; we also offer to implement it with our agentic solutions on a partner headless ALM.
The typical ASPICE toolchain: Jira (issues/tests via R4J, Xray/Zephyr), Polarion, Codebeamer, IBM DOORS Next, Enterprise Architect (architecture/design models), and Confluence (plans, reviews, records). Types are configurable, so the mappings are the common ASPICE setup, not the only one.
Start with the configuration-management data model (SUP.8) — it is the enabling layer that caps the maturity of every other process. Then work the V: system requirements (SYS.1/2), architecture (SYS.3/SWE.2), software requirements (SWE.1), detailed design and code (SWE.3), and verification up the right arm (SWE.4–6, SYS.5).
Grounded in the standard, honest about the theater: What is ASPICE · Automating ASPICE with AI agents · Agile ASPICE · Best ASPICE tools