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 decode SAE J2012 standard CAN diagnostic trouble codes (P, B, C, and U codes) with manufacturer-specific extensions, analyze multi-frame fault sequences and temporal patterns across multiple modules, and generate structured diagnostic hypotheses that differentiate between electrical, communication, and algorithmic failures. This skill transforms raw DTC data into actionable investigation vectors, reducing diagnostic analysis cycles from hours to minutes while improving root cause accuracy.
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 systematically investigate NVH complaints, conduct root cause analysis using transfer path analysis methodologies, plan and interpret diagnostic testing data, and develop evidence-based solutions across the full vehicle lifecycle. This framework guides you through multidisciplinary analysis—covering acoustics, mechanical dynamics, materials, and manufacturing variability—enabling faster problem resolution and more effective cross-functional communication with design, manufacturing, and supplier teams.
You can create multi-phase OTA rollout campaigns tailored to automotive safety constraints, hardware heterogeneity, and regulatory requirements. This skill helps you design canary deployments (2%, 5%, 20%, 100% increments), establish automated rollback thresholds, coordinate dependencies across ECUs, and communicate deployment risks to cross-functional stakeholders—transforming reactive firefighting into proactive, data-driven fleet management.
You'll establish validated simulation architectures that execute cleanly and produce physically meaningful results. This skill guides you through model topology decisions, solver parameter selection, constraint formulation, and pre-run validation checkpoints. You'll identify and eliminate configuration errors—improper contact stiffness, inconsistent degrees of freedom, poorly scaled inertia properties—before wasting CPU hours on failed simulations.
This skill systematically validates your OTA update architecture across five critical dimensions: partition and storage allocation for A/B slots and recovery images, safety and rollback mechanisms including atomic commit strategies, delta compression efficiency for cellular bandwidth optimization, regulatory compliance mapping against ISO 26262 and UN R156, and deployment risk identification including version conflicts and single points of failure. You identify architectural gaps before they cause field failures or fleet immobilization.
You can rapidly correlate vehicle test data (lane change, slalom, ramp steer) with simulation targets, troubleshoot steering feel complaints like heaviness, dead band, and kickback, and analyze how suspension geometry, EPS control strategies, and column stiffness modifications affect handling behavior. This skill organizes complex multi-domain steering data into actionable insights that connect theoretical kinematics to driver feedback.
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.