AUTOSAR Architecture Design Assistant
Design AUTOSAR ECU architectures with SWC hierarchy, BSW config & compliance validation
What You Can Do
You can design complete AUTOSAR system architectures by decomposing functional requirements into Software Components (SWCs) with properly mapped interfaces, configuring Basic Software (BSW) modules, and validating against AUTOSAR standards in real time. The skill helps you evaluate ECU communication patterns, optimize component partitioning for multi-core execution, and identify integration risks before firmware development begins—reducing costly rework cycles and supplier coordination delays.
Features
Decompose requirements into Software Components with clear port definitions and data flow validation
Map functional needs to Basic Software layers with memory and performance constraint checking
Verify architecture against AUTOSAR 4.x standards, naming conventions, and OEM guidelines in real time
Design Runtime Environment port connections and inter-component data exchange patterns
Identify circular dependencies, port type mismatches, and architectural bottlenecks before implementation
Generate standardized AUTOSAR XML element hierarchies ready for tool export
Optimize SWC allocation across processor cores with execution flow analysis
Produce standardized diagrams, dependency matrices, and interface specifications
Example Output
Example 1: SWC Decomposition
Input: "Design AUTOSAR architecture for adaptive cruise control ECU with sensor fusion and vehicle control"
Output:
- SensorFusion_SWC (interfaces: CameraInput, RadarInput, VehicleSpeed; provides FusedObjectList)
- PathPlanning_SWC (requires FusedObjectList; provides DesiredAcceleration)
- VehicleControl_SWC (requires DesiredAcceleration; provides ThrottleCommand, BrakeCommand)
- DiagnosticsManager_SWC (provides SystemStatus, requires all component health signals)
Port Validation: ✓ All data types consistent, ✓ No unconnected ports, ⚠ RadarInput latency risk flagged
Example 2: BSW Configuration Check
Input: "Validate BSW selection for 512KB RAM, 100ms cycle time, 5 CAN messages/sec"
Output:
Recommended BSW Modules:
✓ ComM (Communication Manager) — 8KB RAM, lightweight for CAN bus
✓ PduR (PDU Router) — 4KB overhead, supports message routing
✗ SafetyManager — 80KB footprint exceeds 20% BSW budget; recommend SimpleDiag alternative
RTE Buffer Sizing: 120 bytes for cyclic communication → ✓ Fits within 100ms deadline
Example 3: Integration Risk Report
Architectural Issues Found:
⚠ Circular dependency: SensorFusion → PathPlanning → VehicleControl → SensorFusion
⚠ Port mismatch: CameraInput expects int32 pixel_count; CameraDriver_SWC provides uint16
⚠ Memory risk: Combined SWC code footprint 280KB; ECU ROM budget 256KB
What's Included
- SKILL.md: Complete AUTOSAR architecture design instruction file with validation rules
- SWC Decomposition Template: Functional requirement to Software Component mapping worksheet
- BSW Module Selection Checklist: Memory, performance, and dependency validation guide
- AUTOSAR Port Definition Framework: Port interface standardization and type checking matrix
- Integration Risk Assessment Checklist: Circular dependency, timing, and data flow validation
- ARXML Structure Planning Guide: XML element hierarchy template for tool configuration
- Multi-core Partitioning Worksheet: Core allocation strategy and load balancing analysis
- Architecture Documentation Template: Standardized component diagram, dependency matrix, and interface specification formats
Who It's For
- AUTOSAR Architects — Designing ECU software stacks and component hierarchies from specifications
- Embedded Systems Engineers — Migrating legacy firmware to AUTOSAR 4.x standards with compliance requirements
- ECU Firmware Teams — Planning multi-supplier component integration and interface contracts
- Systems Engineers — Validating functional decomposition before assigning to development teams
- OEM Technical Leads — Reviewing supplier AUTOSAR submissions against company architectural guidelines
Best For
- Designing new AUTOSAR system architectures from functional specifications
- Decomposing complex ECU functionality into Software Components with clear interfaces
- Evaluating Basic Software module selections against memory and timing constraints
- Validating port definitions for type consistency and data flow correctness
- Identifying integration risks and architectural bottlenecks before firmware development
- Planning multi-core SWC partitioning and execution strategies
- Migrating legacy non-AUTOSAR software to AUTOSAR 4.x compliance
- Generating ARXML structure planning for tool configuration and export
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 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.
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.
This skill helps you architect platform strategy by generating decision frameworks, prioritization matrices, and roadmap plans that account for developer ecosystem impact. You'll analyze tradeoffs between breaking changes, feature velocity, and technical debt to make confident platform decisions. It synthesizes developer feedback, competitive positioning, and business goals into actionable strategic outputs that your team can execute.
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 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.