Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: dserodio on April 01, 2005, 02:55:31 pm
-
How can I make EA show the diagram stereotype?
-
Diagram stereotype??
If you need to reference one diagram from another diagram just drag and drop it in as a diagram reference.
-
Yes, on the Diagram Properties dialog I can set the diagram's stereotype, say, "Physical Data Model". But I can't figure out how to make this stereotype show up in the diagram.
-
I never used the stereotype for diagrams since there is another property to distinguish between class, use case and state diagrams. BUT: the stereotype should appear in the project browser if it's not blank. So I suppose you send a bug report.
-
I also use the diagram stereotype, for example, to mark 'business' from 'system' activity diagrams.
I started a topic in the automation forum a while about showing the stereotype in the documentation, but no one has ever answered it (#stereotype# is not a diagram tag for the HTML doc).
The fact that the stereotype also doesn't show in the browser makes me think that it probably isn't taken into account by EA.
The hyperlink idea is good but it only helps to refer to a diagram from another, i would like the diagram itself to show what stereotype it belongs to without including it in the diagram name (since it is part of its description).
I would also like to know what can i do to show the stereotype, since my projects rely heavily on it.
Any words of wisdom from the admins would be very welcome.
-
I have tracked this issue for a long time and i would like to hear one of the admin's opinnion.
What is the purposse of the diagram's stereotype and why isn't it reflected anywhere except in the diagram's property page?
-
I have tracked this issue for a long time and i would like to hear one of the admin's opinnion.
What is the purposse of the diagram's stereotype and why isn't it reflected anywhere except in the diagram's property page?
Diagram isn't a UML metaclass (which is a pity), so UML diagrams aren't extendable (it would be useful if they were), so they don't need to have a stereotype. We've given them one anyway; if you find it useful, feel free!
-
Understood
But could you please pretty please add a stereotype HTML doc tag so at least we can see it reflected in the documentation?