Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: meierch on February 25, 2010, 06:31:01 am
-
All elements have a status field ... diagrams don't. I would also like to have a status field for diagrams as well to support our quality/review process.
-
I'd second this
-
Thirded!
-
And tagged values please.
b.
-
And tagged values please.
b.
Why not? I'm all for Consistency...
Paolo
-
I also agree :)
-
I agree with the status field request.
For the tagged values, well just be careful with that. Stereotypes and tagged values on diagrams are not UML.
Geert
-
For the tagged values, well just be careful with that. Stereotypes and tagged values on diagrams are not UML.
Well, they should be. Diagrams are objects too! :)
Diagram status is essentially the same thing as drawing status in the hardware engineering world and is fundamental configuration management stuff. Definitely gets my vote, along with stereotypes and tagged values, standard or no. After all, EA was ahead of the standards curve with Requirements, for example, long before SysML was a gleam in OMG's eye.
Fred W
-
For the tagged values, well just be careful with that. Stereotypes and tagged values on diagrams are not UML.
Well, they should be. Diagrams are objects too! :)
Diagram status is essentially the same thing as drawing status in the hardware engineering world and is fundamental configuration management stuff. Definitely gets my vote, along with stereotypes and tagged values, standard or no. After all, EA was ahead of the standards curve with Requirements, for example, long before SysML was a gleam in OMG's eye.
Fred W
'Onya Fred!
I agree...
We need to be able to create models and render them so that they communicate to the users (and, increasingly, to non-technical users).
Anything that allows us to specify aspects of diagrams is welcome...
Paolo
-
These requests have my vote!