ASPICE SWE.3 Software Detailed Design and Unit Construction
Get Started with This SkillOverview
Elaborate ASPICE SWE.3 work products: detailed design and software units (code) with traceability for Automotive SPICE (VDA PAM 4.0).
Getting Started
Add your source materials to the project workspace, then activate the ASPICE SWE.3 Software Detailed Design and Unit Construction skill. The agent will guide you through the process step by step.
Example Conversation
You: We’re implementing the OTA and Boot modules. Can you help us document the detailed design and keep traceability to the software architecture for SWE.3?
Agent: I’ll help you elaborate detailed design and link it to software units. I need: (1) The software architecture and allocated requirements for the modules you’re implementing; (2) Coding standard (e.g. MISRA, AUTOSAR C++14); (3) Format for detailed design — inline in code, separate design doc, or both?
You: We use MISRA C:2012 for C and our internal C++ guidelines. Prefer a separate design doc per module with traceability to source files.
Agent: I’ve created
detailed-design-ota.mdanddetailed-design-boot.mdwith unit-level design (main functions, data structures, state machines) and traceability to source files (e.g. ota_handler.c, boot_manager.c). The traceability matrix links SW-REQ → component → design element → file/function. I’ve added a short checklist for MISRA compliance (no deviations yet). Should I add the same structure for the Diagnostic module when you’re ready?
Sample Output Excerpt
Below is a representative excerpt from a SWE.3 detailed design and traceability.
Detailed design — OTA module (excerpt)
| Design element | Description | Source unit |
|---|---|---|
| OTA_StateMachine | States: Idle, Validating, Applying, Done, Error; transitions on events from RTE | ota_handler.c : OTA_Run() |
| ValidatePackage() | Checks signature and size; returns valid/invalid | ota_handler.c |
| ApplyCalibration() | Writes to NvM; triggers reset if required | ota_handler.c |
Traceability (excerpt)
| SW-REQ | Component | Design element | Unit |
|---|---|---|---|
| SW-REQ-001 | OTA | OTA_StateMachine, ValidatePackage, ApplyCalibration | ota_handler.c |
Validation
This skill does not include extension tools. Validation is performed by following the Validation checklist in the skill workflow: every component has corresponding detailed design and implemented units; code adheres to referenced coding standards; traceability is maintained; units are buildable and identifiable for unit test.