Book a Demo

Author Topic: State Transitions  (Read 3472 times)

sbaldrick

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
State Transitions
« on: September 16, 2011, 08:53:15 am »
In the Transition Properties dialogue window, one may specify the effect as behavior and select that behavior from a list of class operations.

In the dialogue window there is room for selection of several behaviors, yet each time I select another behavior it replaces the existing behavior instead of adding to it.

It is normal for a state transition to trigger several operations. It should be possible to select several behaviors describing those operations.
« Last Edit: September 16, 2011, 08:53:56 am by MundayL »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: State Transitions
« Reply #1 on: September 16, 2011, 05:43:51 pm »
Leslie,

I believe it is indeed a UML restriction that a transition can have at most one behavior as effect.
So I guess EA is just (trying) to be UML compliant. (an Operation is not a Behavior, so they are still wrong here)

Geert

sbaldrick

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Re: State Transitions
« Reply #2 on: September 17, 2011, 02:30:29 am »
Behavior/Operation - I may have mixed up the terms a bit.

As an example, a state transition may cause many triggers to be fired in addition to performing 1 (or more) operations within the current object.

The easy workaround is to create an operation that performs the complete behavior of the transition, but this seems a little awkward, and doesn't help clarify the requirements.