eclipse-uml2-bot
commented
6 hours ago By Ed Willink on Sep 13, 2020 03:06
Bug 566911 considers the need for better OCL support for StateMachine instance execution.
Bug 566912 considers the provision of Animation in Papyrus.
| --- | --- | | Bugzilla Link | 566910 | | Status | NEW | | Importance | P3 normal | | Reported | Sep 13, 2020 02:56 EDT | | Modified | Sep 13, 2020 03:06 EDT | | See also | 566912, 566911 | | Reporter | Ed Willink |
Description
The risk that the USE tool that supports UML and OCL might fade away prompts me to reflect on what it does well that Eclipse UML/OCL/Papyrus do not.
I am not aware of anyone attempting to do state machine animation/analysis in Eclipse. Narrowly this is because Eclipse UML targets Ecore instances and there is no EStateMachine/EState/ETransition class in Ecore. But UML has a bloated InstanceValue / InstanceSpecification capability that should allow the modeling to proceed.
Therefore the main problem is that Eclipse UML has encouraged a culture of Ecore only instances inhibiting UML usage.
If the UML Model Editor emulated the Ecore Model Editor by providing a Create Dynamic Instance... context menu entry for a Classifier it could unblock the impediments to this use case. No doubt some other menu entries amy need revisting once the Instance.uml is opened to ensure that the user gets to work with instances and slots rather than classes and properties.
NB. The failure to support UML instances is sufficiently serious that this must be a bug rather than an enhancement.