AUTOSAR Architecture Designer
Design AUTOSAR 4.x architectures with automated component mapping and compliance validation
What You Can Do
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.
Features
intelligently maps software components across application, RTE, and BSW layers based on functional requirements
defines service interfaces, creates port contracts, and visualizes data flow between components
identifies architectural flaws and interface mismatches before RTE code generation
checks designs against AUTOSAR 4.x standards and generates remediation recommendations
generates comprehensive communication mapping showing all component-to-component interactions
produces standardized schema guidance for architecture export and tool integration
creates clear architectural diagrams showing component relationships and layer separation
generates structured materials for team reviews and stakeholder sign-off
Example Output
Example 1: Component Layer Allocation
- Application Layer: FuelInjectionController, EngineSpeedSensor
- RTE Layer: FuelInjection_Service, SensorData_Interface
- BSW Layer: CAN_Driver, PWM_Module
- Validation: ✓ No circular dependencies, ✓ All interfaces mapped, ⚠ 2 unresolved service calls
Example 2: Port Interaction Matrix
| Source Component | Target Component | Port Type | Data Flow | Status |
|---|---|---|---|---|
| EngineController | FuelPump | Require-Provide | CyclicData | ✓ Valid |
| SensorInterface | EngineController | Require-Provide | EventData | ✓ Valid |
| DiagnosticServer | EngineController | Client-Server | DiagRequest | ✓ Compliant |
Example 3: Compliance Report
- Total Components: 12
- Layer Distribution: APP (6), RTE (3), BSW (3)
- AUTOSAR 4.3 Compliance: 98%
- Critical Issues: 0
- Warnings: 2 (service timeout not specified, port multiplicity mismatch)
What's Included
- AUTOSAR-Architecture-Designer SKILL.md: Core instruction file for architecture design workflows
- Layer Allocation Template: Structured worksheet for mapping components to AUTOSAR layers (APP/RTE/BSW)
- Port Interaction Framework: Template for defining interfaces, contracts, and data flow relationships
- Compliance Checklist: AUTOSAR 4.x standards validation checklist with remediation guidance
- Architecture Documentation Template: Structured outline for generating architecture review materials and dependency graphs
Who It's For
- Automotive Embedded Software Engineers — designing ECU architectures and system components
- Systems Architects — planning AUTOSAR layer distribution and component interaction patterns
- Technical Leads — validating architecture coherence before development and RTE code generation
- Integration Engineers — documenting port contracts and interface requirements for distributed teams
- Architecture Reviewers — preparing standardized materials for design reviews and compliance audits
Best For
- Designing architecture for new ECU features or complete systems
- Refactoring legacy embedded code into AUTOSAR-compliant structures
- Validating component interactions and port connections before RTE generation
- Planning service distribution across application, RTE, and BSW layers
- Documenting architectural decisions and creating design review materials
- Analyzing communication patterns to optimize signal routing and interfaces
You might also like
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 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 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.
You can model transient and steady-state thermal behavior in EV power electronics, calculate junction temperature rise during driving cycles, and design cooling strategies that meet automotive thermal specifications. This skill helps you size heat sinks, evaluate thermal interface materials, compare active versus passive cooling approaches, and validate designs against AEC-Q200 and ISO 16750-3 standards.
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 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.