Automotive Architecture Tools Showdown: Rhapsody, EA, Matlab & Lightweight Alternatives

Opening the Tool Discussion

The conversation began when Leo asked in a WeChat group for automotive electronic architects: "At the concrete tool level, what tools are currently used for architecture in the automotive field?" This question sparked a lively exchange of experiences and insights.

Mainstream Multi‑Function Tools

IBM Rhapsody and Enterprise Architect (EA)

David mentioned IBM Rhapsody and EA , noting that both handle not only software architecture but also system hardware architecture, acting as versatile multi‑purpose tools across different design scenarios.

Jason countered: "EA‑type tools are only suitable for hand‑written code," suggesting he sees limitations in EA for automated code generation.

Matlab / Simulink

Opinions on Matlab were divided:

Lily asked: "Can Matlab now do architecture as well?"

Jason gave it high praise: "Matlab is invincible."

Alex disagreed: "Matlab's architecture capabilities are still very weak."

Tom clarified that Matlab is primarily used by digital model developers, implying it is not the mainstream choice for architecture design.

Lightweight Diagramming Tools

PlantUML

Tom shared PlantUML , describing it as "code‑as‑diagram, diagram‑as‑code." This approach tightly couples code and graphics, allowing architects to generate architecture diagrams directly from code and vice versa.

Drawio (diagrams.net)

Kevin recommended Drawio for those who prefer not to use code for diagrams. He highlighted its wide applicability: system diagrams, iOS prototypes, hand‑drawn sketches, business presentation diagrams, both static and dynamic. Key advantages:

Free and open source — a major plus for cost‑sensitive teams.

Integrated into platforms like Feishu (Lark) for convenient access.

Kevin demonstrated Drawio combined with AI‑generated graphics, showing its flexibility.

If an organization only needs basic diagramming, Drawio can satisfy that requirement.

Umlet

David also mentioned Umlet , stating it is very useful, though without detailed elaboration.

Tool Selection Criteria

The discussion revealed that different tools fit different scenarios and needs:

Need architecture modeling with code generation → MATLAB Simulink may be more suitable.

Electrical/electronic architecture requiring network matrices and signal matrices → EA could be the better choice.

Simple architecture diagramming for individuals or teams → Lightweight tools like PlantUML , Drawio , Umlet each have their merits; selection depends on personal preference and specific requirements.

In the complex engineering of automotive architecture design, choosing the right tool is like picking a well‑fitted weapon — it enables architects to work twice as efficiently.