Can't draw a simple UML Activity Diagram without 'Strict Connector Syntax' OFF

[Ian Mitchell]

In v16.1, I've just tried to draw a simple UML Activity diagram. Which  I have't done for years, and was surprised when EA would not let me.
Not even the simplest 'Control  Flow' connectors worked between any kinds of element.
So I switched-off 'Strict Connector Syntax' in Start / Preferences / Links, and all was well.

This seems like a strange default. The UML-compliant connector type between, for example, Activity and another Activity IS  a Control flow last time I checked. Or is it? And if not, what is?
So this must be a bug?
Is Strict Connector Syntaxt ON or OFF for an out-of-the-box EA setup? If it's ON, then this isn't a great UX.

[philchudley]

Hi Ian

I believe, and Geert will concert me if I am wrong, but UML (latest version) dictates that control / object flows can only be drawn between actions. EA now enforces these rules, therefore, you have to:

• Define you activities as stand alone elements on an Activity diagram, add any parameters, and make them composite to link to an activity diagram that models the internal flow in that activity
• Re-use the activity on its own composite diagram as a link
• Use actions etc to model the flow, to call an activity within an activity re-use an activity as an invocation

To model the top level orchestration between activities:

• Model the top level as a single activity and make this a composite element
• Re-use all other activities as invocations
• Model the flow between them

A major flaff for simple flows, then as you have discovered, Strict Connector Syntax off, if the way to go.

Oh just for fun the same applies to SysML as well.

All the best for Christmas, New Year and your expedition to New Zealand

Phil

[Modesto Vega]

Hi Ian,

Phil's interpretation of the standard aligns to the discussion we had in the following thread https://sparxsystems.com/forums/smf/index.php/topic,46866.0.html. Control and object flows can only drawn between actions, this was the case in v15.

The only unclosed loose end from these discussions is what are the permitted, as per the standard, relationships between activities.

[Geert Bellekens]

Hi Ian,

I'm afraid you've been making Activity diagrams wrong for all these years.
UML never allowed this, but EA did untill recently.

Geert

[Eve]

I'm afraid you've been making Activity diagrams wrong for all these years.
UML never allowed this, but EA did untill recently.

Just wanted to reinforce this.

[Ian Mitchell]

Well, I did say it was a long time since I created an AD.
I think I now remember why I started to use BPMN as soon as that was available. The out-of-the box experience - as defined by UML and implemented by EA - which Phil so expertly described, really is a bit clunky.
Thanks everyone.