Enterprise Architect
| Tested version | EA 15.2 (Trial edition used for verification). CelinQ integrates through EA's own COM Automation API rather than a version-specific format parser, so the integration is not architecturally tied to 15.2 — but 15.2 is the only version actually exercised in CelinQ's own test suite to date. |
|---|---|
.eap / .eapx | Supported and verified. All of CelinQ's EA test fixtures and scripted acceptance runs use .eap. |
.qea / .qeax | Not yet verified. CelinQ opens repositories through EA's own format-agnostic Repository.OpenFile method, which should accept EA's newer SQLite-based format in principle — but no .qea/.qeax fixture exists in CelinQ's test suite, and EA's own documentation notes .qea requires EA 16 or later. Treat this as untested, not unsupported. |
| Elements, relationships, diagrams, tagged values, packages | Full support — these are what CelinQ's canonical model and Fusion merge engine were built around from the start. |
Archi
| Tested version | Archi 5.7.0. |
|---|---|
.archimate | Supported and verified — the only format Archi itself uses, read and written through Archi's own EMF model API. |
Cross-tool mapping: Enterprise Architect ↔ Archi
When an EA repository and an Archi model share a CelinQ workspace, this is exactly what maps, and what doesn't, between them.
| Elements | Full. Element type, name and identity map directly. |
|---|---|
| Relationships | Full. Including source and target endpoints. |
| Properties / tagged values | Full in the common case. Archi's uniform property list maps directly to EA's tagged values. Enterprise Architect's richer, split property model (core fields separate from tagged values, plus a relationship Direction field Archi has no equivalent for) does not fully round-trip back from Archi — an EA-specific field with no Archi counterpart stays on the EA side. |
| Diagrams / views | Full, including diagram node and connection positions (x, y, width, height), preserved through the sync. |
| Folders / packages | Full. |
| Stereotypes / specializations | No equivalent yet. Not currently mapped in either direction — a named, open gap. |
| An EA element with no Archi-side type equivalent | Skipped, not silently substituted. The sync engine logs the specific entity it could not translate and continues with everything else — it does not invent a fallback type or drop the failure silently. The element does not appear on the Archi side until this gap is closed; reconciliation does not currently self-heal it. |
Why this page exists. A capability matrix is only useful if it is honest about the boundary between "supported," "partial" and "not yet." Every row above reflects what the current code actually does, checked against the real mapping implementation — not what the architecture would eventually allow if someone finished the remaining work.
Read next
Security
Security
Deployment topology, authentication, encryption, secrets and backup — the real facts.