| Use Case | Description | Diagram Type |
|---|---|---|
| System requirements | Capture and link system requirements to architecture | SysML Requirements Diagram; Use Case |
| Functional architecture | Hierarchical function decomposition | SysML Block Definition Diagram (BDD) |
| Component interfaces | SWC ports and interfaces | SysML Internal Block Diagram (IBD) |
| State machines | ECU operational mode state machines | SysML State Machine Diagram |
| Safety concept | Safety goal allocation; fault tree | Custom safety templates; FTA diagram |
| Sequence diagrams | Signal flow between ECUs for a use case | SysML Sequence Diagram |
Enterprise Architect in Automotive
EA Architecture Script (Python/Jython)
Pythonea_automation.py
"""Enterprise Architect automation via Python COM interface.
Note: EA scripting runs inside EA via JScript/VBScript or
externally via Python + win32com on Windows.
"""
import win32com.client as com
def get_ea_elements(project_file: str, package_name: str):
"""List all elements in an EA package."""
ea = com.Dispatch("EA.App")
repo = ea.Repository
repo.OpenFile(project_file)
# Find package
models = repo.Models
for i in range(models.Count):
model = models.GetAt(i)
pkg = find_package(model, package_name)
if pkg:
elements = []
for j in range(pkg.Elements.Count):
el = pkg.Elements.GetAt(j)
elements.append({
"name": el.Name,
"type": el.Type,
"notes": el.Notes,
"tagged": {tv.Name: tv.Value
for tv in el.TaggedValues}
})
return elements
return []
# Export function tree with ASIL tags
functions = get_ea_elements("VehicleEEA.eapx",
"FunctionalArchitecture")
for f in functions:
asil = f["tagged"].get("ASIL", "QM")
print(f" {f['name']:<40} ASIL: {asil}")Summary
Enterprise Architect is the preferred tool for systems engineering activities that require rich modelling (SysML block diagrams, state machines, sequence diagrams) and requirements management, while PREEvision is preferred for E/E-specific activities (network topology, harness design, ARXML generation). In most OEM projects, both tools are used: EA for the functional and logical architecture (what the system does and how components are structured) and PREEvision for the physical network and wiring architecture (where ECUs are located and how they are connected). The integration between the two tools (EA exports function allocation; PREEvision reads it for routing table generation) is the most architecturally important interface to manage in the toolchain.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.