Automotive Software Architecture

---
name: automotive-software-architecture
description: "Use when designing automotive software."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [automotive, automotive-software, architecture, engineering]
    related_skills: [general]
---

## Overview
Automotive Software Architecture implementation. Covers best practices, methodologies, 
technical considerations, and verification approaches for this domain.

## When to Use
- "Automotive Software Architecture implementation and optimization"
- "Best practices for Automotive Software Architecture workflows"
- "Automotive Software Architecture compliance and standards"
- "Automotive Software Architecture troubleshooting and problem-solving"
- "Automotive Software Architecture ROI and performance measurement"

## Key Methodologies
```text
1. Assessment and Planning Phase
2. Implementation and Execution
3. Monitoring and Optimization
4. Compliance and Verification
5. Continuous Improvement
```

## Common Pitfalls
1. **Insufficient planning** — rushing without proper assessment
2. **Ignoring industry standards** — not following established frameworks
3. **Poor stakeholder alignment** — conflicting requirements
4. **Inadequate measurement** — no metrics for success
5. **Not accounting for local conditions** — generic approaches fail
6. **Underestimating complexity** — oversimplified solutions
7. **No contingency planning** — no plan for unexpected issues
8. **Insufficient training** — operators lack required skills
9. **No verification process** — implementation without quality checks
10. **Failing to iterate** — not improving based on results

## Verification Checklist
- [ ] Initial assessment and baseline established
- [ ] Industry standards and best practices identified
- [ ] Stakeholder requirements aligned and documented
- [ ] Implementation plan with timelines
- [ ] Quality control measures defined
- [ ] Training completed for involved parties
- [ ] Monitoring system with key metrics
- [ ] Compliance requirements verified
- [ ] Performance baseline before go-live
- [ ] Post-implementation review scheduled