AUTOSAR Architecture Validation & Compliance Assistant
Validate AUTOSAR architecture designs for standard compliance and structural integrity
What You Can Do
You can validate AUTOSAR software architectures across multiple compliance dimensions—layer separation, component interfaces, port definitions, service interfaces, and communication semantics. The skill identifies structural violations, missing documentation artifacts, and compliance gaps early in the design phase, helping you catch issues before formal gates and functional safety audits. It generates architecture compliance reports and documentation needed for ISO 26262 functional safety reviews.
Features
verifies proper isolation between Application Layer, RTE, and BSW modules
checks port definitions, service interfaces, and communication semantics for correctness
validates cross-ECU communication configuration and RTE interactions
ensures artifact naming follows AUTOSAR standards and traceability rules
identifies gaps in interface specifications, design artifacts, and compliance evidence
audits state machines and mode-dependent behavior for AUTOSAR compliance
reviews Basic Software configuration against AUTOSAR layering requirements
produces structured documentation for ISO 26262 functional safety audits
Example Output
Example 1: Layer Violation Detection
✓ Application Layer: 10 SWCs validated ✓ RTE Configuration: 4 scheduling groups, 25 runnable mappings ⚠ Violation Found: SWC_Engine directly accesses CAN driver (BSW) — should use RTE service port ⚠ Missing: Port timing annotations on 3 periodic SWCs
Example 2: Compliance Report
AUTOSAR 4.2 Compliance Summary
- Reviewed 15 Software Components
- Interface Definitions: 12/15 complete (80%)
- Mode Management: 2/4 state machines properly annotated
- Communication Bindings: CAN configuration validated ✓
- Missing Artifacts: 3 interface specifications, 2 mode declarations
- Recommendation: Add interface timing contracts before RTE generation
Example 3: BSW Organization Assessment
✓ Com module: Properly layered, 24 signal mappings validated ✓ EcuM: State chart follows AUTOSAR 4.x standard ⚠ Memory layout: 2 BSW modules sharing RAM section (non-compliant) → Action: Refactor memory organization per AUTOSAR Memory Abstraction Layer rules
What's Included
- AUTOSAR_Validation_Assistant.md: core validation skill and compliance checking methodology
- Architecture_Review_Checklist: comprehensive AUTOSAR 3.x and 4.x compliance checklist (layer separation, interfaces, naming)
- Compliance_Report_Template: structured markdown template for ISO 26262 functional safety gate documentation
- SWC_Interface_Verification_Framework: step-by-step process for validating port definitions and service interactions
- BSW_Module_Organization_Guide: reference guide for proper Basic Software layering and configuration patterns
Who It's For
- AUTOSAR Architects — validating software architecture designs before specification sign-off
- Embedded Software Engineers — reviewing component layering and interface compliance
- Functional Safety Managers — gathering compliance evidence for ISO 26262 audits and safety gates
- ECU Integration Engineers — assessing multi-ECU communication topology and RTE configuration
- Legacy Code Refactoring Teams — identifying compliance gaps when migrating to AUTOSAR standards
Best For
- Pre-implementation architecture reviews of SWC designs
- Multi-ECU communication topology validation
- Compliance documentation generation for functional safety audits
- BSW module organization and layering assessment
- Interface specification completeness and correctness checking
You might also like
You can pinpoint the exact source of sensor fusion failures—whether they stem from misaligned camera/LiDAR/radar extrinsic calibration, timestamp desynchronization, data validation gaps, or algorithmic issues. This skill decomposes multi-modal perception errors into sensor-specific contributions and generates quantifiable diagnostic reports that directly guide calibration and testing teams toward fixes rather than blind troubleshooting.
You can design complete AUTOSAR 4.x system architectures by automating component allocation across abstraction layers, modeling port interactions and service interfaces, and validating compliance with AUTOSAR standards. Claude helps you create standardized architecture documentation, detect circular dependencies and interface mismatches, and generate port interaction matrices—accelerating ECU architecture development while ensuring standards adherence.
You can analyze FEA thermal simulation data to identify motor hotspots, calculate heat generation from motor losses across operating points, evaluate competing cooling solutions quantitatively, and troubleshoot excessive temperature rise during dyno testing. The skill helps you validate thermal management design margins, assess motor lifetime degradation risk, and optimize cooling loop efficiency—enabling data-driven thermal design decisions before building prototypes.
You can efficiently diagnose complex NVH concerns by working through a structured framework that correlates customer symptoms with potential powertrain failures. This skill helps you narrow diagnostic possibilities, recommend targeted testing sequences, distinguish between component failures and tuning issues, and substantiate warranty claims with technical evidence.
You can evaluate simulation scenarios against functional safety and SOTIF requirements, identify untested edge cases and high-risk operational design domains, map failure modes to root causes, and generate traceability matrices linking requirements to validation results. This skill transforms raw simulation data into defensible technical documentation that demonstrates test completeness and readiness for real-world deployment.
You can quantify sensor fusion performance across object detection, classification, tracking, and localization using standardized metrics. The framework helps you identify systematic failure modes in diverse environmental conditions, document safety-critical gaps, and generate structured evidence packages for ISO 26262 and SOTIF compliance. This enables you to benchmark sensor configurations, define perception KPIs, and support regulatory submissions with rigorous performance documentation.
You can upload ECU firmware logs, CAN bus traces, and diagnostic data to identify root causes of vehicle malfunctions in hours instead of days. Claude parses hexadecimal memory dumps, cross-references DTC databases with symptom descriptions, correlates sensor data with actuator commands, and generates hypothesis trees for intermittent failures—enabling faster debug cycles and validated firmware patches.
You can analyze multi-dimensional steering system performance including torque characteristics, self-alignment torque, steering angle feedback, road feel transmission, and torque vectoring effects. Extract actionable insights from simulation and test data to identify root causes of steering feel issues, then develop tuning recommendations for steering gear ratios, EPS algorithms, suspension geometry effects, and torque vectoring control strategies.