Hi team,
I was investigating the usage of the facade for the tests, currently extending the tests around canonical mode and state machines (not working well currently for transitions).
While working with the tests, I (re)discovered the fact that the facade is a very efficient way to build semantic test environments. However, I found some limitation on the creation of transitions, and I wanted to discuss about potential improvements.
Currently, the method
createTransitionTo on UMLRTVertex creates the transition, without taking care of the target and source, e.g. by passing the rules setup for the creation of transition on Bug 494284: [Tooling] Create a UML-RT Transition using the tool palette in a state machine diagram. There is also no kind implied there
Would there be any added value (except for the tests) to update that method to follow the rules, and for example create by default entry/exit points? If yes, what should be the APIs there?
1. createTransition(targetVertex, TransitionKind)?
2. createExternalTransition(targetVertex), createInternalTransition() & createLocalTransition(targetVertex).
The other way of formulating this: are there any other interested parties involved in the definition of the creation methods? And what would be there constraints / wishes?
Cheers,
Rémi
--
Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France
Commercial Register 824 977 516 R.C.S. EVRY
