Book a Demo

Author Topic: Call/Signal Triggers with Arbitrary Specification  (Read 2752 times)

rainerf

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Call/Signal Triggers with Arbitrary Specification
« on: February 01, 2012, 01:41:11 am »
Hi all,

please bear with me here, I do realize that my use case might not be the standard one ;). I'm using EA 9.0, if that should matter.

When adding a Trigger to a StateMachine Diagram [1], I can freely define its Specification if it is set to Type "Change" or "Time". If it is set to "Call" or "Signal", however, EA provides me with an Input window where I can select a method or a signal, respectively, that has to be defined somewhere in the model. Since my use case has EA only as a part of a bigger tool landscape, however, neither the caller nor the State Machine's class is specified in the model -- which means that there is nothing in the model that I could choose in this step. Is there some way that I can avoid this and simply enter the specification by hand?

I'd like to avoid (ab)using "Change" or "Time" triggers, since their intuitive meaning is contrary to what the triggers mean in the model's context. Furthermore, I guess I could somehow import the model's external specification from the other data sources we use in our tool landscape, but this doesn't sound too easy, and would additionally impose the overhead of keeping the imported interface in sync with the external spec on the designer.

Thanks and best regards,
Rainer.


[1] More precisely, I'm adding a Stereotype extending a Trigger (without adding/changing anything in the Stereotype), since I was unable to find Triggers themselves in the Toolbox.

rainerf

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Re: Call/Signal Triggers with Arbitrary Specificat
« Reply #1 on: February 09, 2012, 11:39:38 pm »
Anyone?

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Call/Signal Triggers with Arbitrary Specificat
« Reply #2 on: February 10, 2012, 09:14:59 am »
I guess you can't do what you want. This is fixed behaviour of EA. You might ask for a feature to be implemented but if it's accepted it will take time to be implemented. For the time being you must bite the bullet and create specification classes prior to setting the trigger.

q.