1
General Board / Re: MCP (Model Context Protocol) server for Enterprise Architect has been released
« on: January 20, 2026, 11:44:10 am »
- Tool-Specific Features: In tools such as Sparx Enterprise Architect, a “Composite Diagram” is a child diagram nested beneath a parent element. For example, if you double-click a Class and it opens a sub-diagram, that sub-diagram is called a “composite diagram,” regardless of whether it is a state machine, activity, or structure diagram.
Even the fact that Gemini is using the phrase "Sparx Enterprise Architect" is enough to say that it's pulling from sources that shouldn't be trusted. It's equivalent to "International Business Rhapsody". It may not be hallucinating, but drawing from unreliable sources is just as bad.
Unless this is a hallucination, then a UML Composite Structure Diagram is an EA Composite Diagram; but not vice-versa!I disagree with both the Gemini interpretation of what a Composite diagram is as well as your assertion that it is actually a Nested Diagram.
Another problem is that EA sometimes conflates Composition with Nesting (I’ve spoken about the difference many times in the past). You’ll see Gemini did not make that conflation. What EA calls a Composite diagram is, in fact, a Nested diagram.
The UML Composite Structure Diagram is a particular type of diagram that shows the internal structure of a particular namespace. EA generalizes that to include Composite behavior and allows new types of Composite diagrams to be defined in a profile. Neither requires actually being nested within in the Namespace it is documenting. EA defaults to that behavior but allows the diagram to be in another namespace, while UML doesn't have anything to say on it.
And yes, Gemini did conflate the two terms and you used that conflation to argue your point.