Sequence diagram: wrong execution specification

[nasahl]

Hi,

the following sequence diagrams show very different execution specifications:



and



There is no logical reason for a different modelling of the execution specifications. It should be the users choice to decide the correct modelling of the execution specification.
Does anyone know if there is a way to model the execution specification? Or is this just an EA bug ?  

Christof

[Eve]

I'm not sure what you are saying is a bug.

You've modelled both possibilities.  What is the problem?

[nasahl]

The point is, that I have no choice to decide the range of an execution specification.
What I would like to model is the execution specification ranges of the first diagram but with d1() being asynchronous. But this is not possible:
When d1() is synchronous, then the execution specifications are according to the first diagram.
When d1() is asynchronous, then the execution specifications are according to the second diagram.
But this predefinition is not logical.

I think it should be the decision of the user how the execution specification should look like, no matter if d1() is synchronous or asynchronous.
In some cases EA gives you the choice to influence the ranges. Then you see a right arrow attached to a message. I would have expected such a mechanism here also.

Christof

[Martin Terreni]

Ritgh click on b2 arrow-head, I think it is possible  to tell it to contiue the process.

[nasahl]

I tried this, but it is not possible that b2() ends in a parallel execution specification when d1() is asynchronous.