ASPICE SUP.8 Configuration Management
Get Started with This SkillOverview
Elaborate ASPICE SUP.8 work products: configuration management plan, baselines, and status records for Automotive SPICE (VDA PAM 4.0).
Getting Started
Add your source materials to the project workspace, then activate the ASPICE SUP.8 Configuration Management skill. The agent will guide you through the process step by step.
Example Conversation
You: We need to document our configuration management plan and baselines for SUP.8. We use Git for code and a doc repo for requirements and design; we don’t have a formal change control process yet.
Agent: I’ll help you elaborate SUP.8 work products. I need: (1) Which work products are configuration items (e.g. requirements, design, code, plans); (2) How you define baselines (e.g. requirement baseline, design baseline, release); (3) How changes are requested and approved (e.g. change request form, CCB, or lightweight approval). I can draft a CM plan and a change request template.
You: Configuration items are all SYS/SWE work products and the project plan. Baselines at requirements, design, and release. We use a change request form and the project manager approves.
Agent: I’ve created
configuration-management-plan.mdwith configuration items, baselines (requirements, design, release), and the change control procedure (request → impact → approval by PM → implement → verify). I’ve addedbaseline-contents.mdas a template to record what is in each baseline when you create it, andconfiguration-status.mdfor change history. I’ve also added a simple change request template (CR-ID, description, impact, decision, implementation). Want me to prefill the current baseline contents from your workspace?
Sample Output Excerpt
Below is a representative excerpt from SUP.8 configuration management work products.
Configuration management plan (excerpt)
| Section | Content |
|---|---|
| Configuration items | Stakeholder needs, system/software requirements, architecture, design, source code, project plan, test specs and results |
| Baselines | Requirements baseline (Mar); Design baseline (Jun); Release baseline (Nov) |
| Change control | Change request (CR-xxx) → impact analysis → PM approval → implement → verify; CCB for scope/schedule changes |
Baseline contents (excerpt) — Requirements baseline (Mar 2025)
| Item | Version / ID |
|---|---|
| Stakeholder needs specification | v1.0 |
| System requirements specification | v1.0 |
| Traceability (needs ↔ sys req) | v1.0 |
Change request (excerpt)
| CR-ID | Description | Decision | Date |
|---|---|---|---|
| CR-012 | Add SYS-REQ-009 (new OEM constraint) | Approved | 2025-02-08 |
Validation
This skill does not include extension tools. Validation is performed by following the Validation checklist in the skill workflow: configuration management plan defines configuration items, baselines, and change control; baselines have recorded contents; change requests are recorded with decision and implementation status; configuration status is maintained.