Thanks you for your answers and feedback.
"reduce the size","simplify understanding"-> yes.
In fact, I have some transitions which aren't the mains cases (and not allow
for all users).
And as there is many states, I would like to show only the "standard"
transition in the first diagram.
I don't know if it's the good exemple :
An Invoic become a "Duplicata" when it have been edited once time.
For special case, we can have a transition for "Duplicata" -> "Invoic"
=> In order to reedit original.
=> It could be usefull for a test/preprod server, but forbidden in
production.
An other use :
I want some text to explain the state.
I would like:
A complete diagram
A diagram without the comment
This second diagram can be used with a module, such as Argoprint, to produce a
document.
In this document, after the diagram, all state are explained (with text) [It's
what I hope, I will try later].
So in the document, without comment, the diagram will be easier to read.
Note : I used a "comment" and not "Documentation" in property panel, because it
loose data when I select an other state.
I don't know how to use this panel, and if it's UML standard (Same for source,
but not enabled).
Is it a Issue ?
Otherwise, I agree with the fact that there 1 Diagram/statemachine is enough.
And, for UML 2, it's seem the same with Activity (A diagram describe an
activity).
It's why I prefer a Discussion instead of issue.
What is UML position ? If I find something, I will add URL.
An other solution for me:
Add stereotype (and tagvalue for text).
Have a module (Argoprint with features) where I can produce document with only
some "stereotype" transition (or without only, or all).
Best regards,
Laurent.
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2797970
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
