Activitydiagram Decision Name

[Nicklas Wiegandt]

Hello,

i work with the Staruml Version 2.4.0 on a activitydiagram and i wanted to show the name of a decision but i can't find how i could do this. I think this was possible in one of the older Versions. 

Can anyone help me please, how i can show the name of a decision in a activitydiagram?

Thank you.

Kind regards,

Nicklas

[StarUML]

Hello Nicklas,

Showing names of control nodes (including decision, merge, ...) diagram is not supported. It was never supported in previous versions, even in V1. Typically just show the guards of the control flows connected to the decision node, instead of showing the name of decision node. At this time, we recommend to use "Text" or "Note" annotation.

Could you explain or convince why showing name of decision nodes is necessary? If it is reasonable, we will consider to support this feature.

Thanks,

StarUML Team

2015년 7월 14일 화요일 오후 9시 29분 10초 UTC+9, Nicklas Wiegandt 님의 말:

[Nicklas Wiegandt]

Hey,

i find it necessary to show the name of the decision node becuase, i can write ther something like: "User logged in?" so everybod who looks at the diagram knows what dicision will be made. Back in my vocational college Time (not so long ago ;) ), we had some Teacher who wanted of us to write it like this. I don't think this is default UML but i think there are some users like me who want to.

Have a nice Day,

Nicklas

[StarUML]

OK. I understand what you expect. However, we strongly recommend to use "guard" property of "Control Flow" instead of using "name" of "Decision Node". Please refers to: http://www.uml-diagrams.org/activity-diagrams-controls.html#decision-node

2015년 7월 15일 수요일 오후 4시 48분 37초 UTC+9, Nicklas Wiegandt 님의 말:

[Nicklas Wiegandt]

Thank you for your Help! :)

[Jakub V.]

I just add my five cents to demonstrate that this need has multiple users :)

 I would love name, or label, for decision too, I believe it's easier/faster to read/understand, if you separate question and answer (eg name of decision and guard on/of flow), than having to put everything into guards .. there's also some redundancy in writing, since you're forced to repeat the "verb" on each outgoing flow..

especially when using activity diagram to document some low level implementation, for example getting some values from database and deciding upon the number of records returned .. eg something like 'found  more than 1 item', 'found one item', 'found none' .. on the low level implmementation you usually need to have all details (parameters for query, for example), meaning you want to have the rest of diagram as simple as possible, and having the name on decision helps that :)

thanks,

 J.

ps: I know I can simulate that with arbitrary text to the element, but you have to attach it with note-link, otherwise you will loose it upon the first reorganization/repositioning of the diagram elements .. therefore it's cumbersome and flawed :)

Dne středa 15. července 2015 v 10:23:11 UTC+2 uživatel nicklas....@googlemail.com napsal: