Hi,
Team,
I am now working on support for state machine inheritance
in the state machine diagram. Along the way, I have updated a
few of the utilities that support presentation of decorations
in the diagram (and the explorer) to use the façade API to
simplify access to the details of potentially inherited
elements.
However, I have a test failure in the State Machine Diagram
Tests in the validation of the decorations for transitions: a
transition that is supposed to show the shield decoration for
a trigger guard and a gear decoration for a transition effect
is now not showing the guard decoration.
It turns out that the reason for this is that the trigger
guard constraint in the test model does not have the «RTGuard»
stereotype applied. It is my understanding from the UML-RT
Profile Specification that this stereotype is required to
designate a constraint as a trigger guard, so the façade API
will not report a guard for a trigger when this stereotype is
missing. The reason being that, otherwise, the constraint is
merely informative (I suppose).
My questions are: should the façade API and the tooling
not ignore constraints for triggers that omit this stereotype?
Should the tooling not apply this stereotype to the
constraint that it creates for a trigger guard?
