1
Bugs and Issues / Re: EA doesn't consider an action to be a behaviou
« on: June 20, 2011, 09:43:41 pm »
OK, I see that transition effect as an behavior is new to UML2.x, in UML1.x it was an action. Under these circumstances, I don't understand how am I supposed to express an effect consisting only of a call or send signal action, e.g.
someTrigger[someGuard]/send someSignal
using a behaviour. Is this textual notation considered to be equivalent to creation of an activity consising merely of the single action "send someSignal"?
This looks as if transition associations to behaviours were meant for machine generation only, not for human authors or readers. Besides, was it really meant that I can use e.g. a whole state-machine for a transition effect?
Martin.
someTrigger[someGuard]/send someSignal
using a behaviour. Is this textual notation considered to be equivalent to creation of an activity consising merely of the single action "send someSignal"?
This looks as if transition associations to behaviours were meant for machine generation only, not for human authors or readers. Besides, was it really meant that I can use e.g. a whole state-machine for a transition effect?
Martin.