Architecture as Code for AUTOSAR Classic
Declare components and compositions as plain YAML in Git. SWCraft checks the whole hierarchy and generates AUTOSAR ARXML, local UML/SysML views and requirements from the same model.
01 / One source of truth
Components, their hierarchy, the diagrams and the ARXML stop being documents that agree by discipline. They are derived from one model, with validation controlling the ARXML handoff.
01name: VehicleControl
02title: Vehicle control
03root: true
04members:
05 - name: BrakeController
06 type: BrakeController
07 - name: Diagnostics
08 composition: Diagnostics
09ports:
10 - name: pVehicleState
11 direction: provide
12 interface: IVehicleStateAUTOSAR
UML / SysML
Sphinx-Needs
Architecture
One explicit root contains named component and composition instances, with boundary ports delegated through the hierarchy.
References, interface compatibility, task mappings, resource budgets and AUTOSAR identifiers are validated across layers.
The existing downstream toolchain remains on the ARXML path. SWCraft moves the reviewable source of truth upstream.
02 / Deterministic gate
Model findings stop generation before it begins. The final ARXML check gives a separate verdict: if schema validation fails, the rejected file remains on disk and must not be handed downstream.
$ swcraft check-model --project swcraft.yaml
checking architecture model...
FINDING SWC 'BrakeController' port 'rBrakeRequest'
references interface 'IBrakeRequest' which is not declared
REFUSED model unchanged · nothing generatedRoot composition, member placement, delegation compatibility and hierarchy cycles.
Task mappings, runnable access points, sequences and requirement coverage.
CPU thresholds, memory budgets and core-to-memory accessibility.
Generated identifier legality and optional validation against a licensed XSD.
03 / Constrained assistance
The assistant cannot edit files or run a terminal. It reaches the architecture through SWCraft, stages one complete change on a private copy, and asks you about the exact resulting delta.
Describe the outcome, not the files.
Every related element arrives together.
The real model stays untouched.
Review what will land, not a summary.
Approve all of it or apply nothing.
04 / Incremental adoption
Introduce Architecture as Code around a bounded slice. Keep the existing engineering flow in place and evaluate the model, checks and generated handoff on their own merits.
Choose a contained subsystem or component group instead of committing to a broad migration.
Build the reviewable source alongside the current process, with no production repository change required.
Only a validated ARXML artefact crosses the boundary into the downstream toolchain.
Review the model, findings, architectural diff, impact and generated views before choosing what comes next.
No big-bang replacement. SWCraft is introduced upstream of the existing toolchain. Its value can be reviewed on a controlled scope before any wider adoption decision.
05 / The architecture workbench
Completion, hover and immediate diagnostics for every model file in VS Code.
EDITORCompare two releases as the exact elements and properties that changed.
CLI · JSON · PANELSee the blast radius of a component or interface before making the change.
READ ONLYNest named instances, expose boundary ports and carry the same composition structure into ARXML and internal block, overview and nesting views.
YAML · ARXML · SVGThe CPU and RAM numbers behind a refusal, visible before the design lands.
CPU · MEMORYVersion-matched documentation and generated reference, served locally.
OFFLINE06 / Project status
The complete architecture loop is implemented. SWCraft covers authoring, deterministic validation, generated handoff and controlled AI-assisted change. It is ready to evaluate on a bounded architecture slice alongside the existing AUTOSAR toolchain.
A Git-native YAML model holds components, interfaces, connections, compositions, requirements and constraints.
Model integrity, architectural rules, resources, safety, AUTOSAR identifiers and optional XSD conformance are checked before handoff.
ARXML, local SVG and HTML diagrams, Sphinx-Needs requirements, semantic diffs and impact reports come from the same model.
One offline workstation archive carries the CLI, VS Code extension, MCP integration, assistant, guide and required runtimes.
07 / Product demonstration
Core workflow demo · 5 minutes 51 seconds · captions · no audio
This recording shows an earlier interface. Current releases generate SVG drawings and self-contained HTML pages that open directly from a file.
ModelYAML authoring and diagnostics
GateValidation and AUTOSAR XSD
ChangeAI proposal and exact review
ViewsDiagrams, resources and impact
A bounded first step
Start from existing architecture or an empty project. Keep the model in its own Git repository; the ARXML it emits is the only thing the downstream toolchain needs to see.
Talk to KonstantinImport or modelUse a representative, bounded slice.
Validate and deriveBuild ARXML, hierarchy-aware diagrams and reports.
Review the evidenceDecide what fits your engineering process.
SWCraft is developed with a tool-qualification path in mind; it is not a qualified tool. Licensed AUTOSAR XSD schemas are not distributed with it.