| Papyrus Moka in Capella [message #1856374] |
Wed, 07 December 2022 18:32  |
 Matheus Cogo
Messages: 2
Registered: December 2022 |
Junior Member |
|
|
Hello everyone,
I am currently trying to bring some State Machine execution support for Eclipse Capella, a MBSE tool (https://www.eclipse.org/capella/). Instead of re-inventing the wheel, I thought of using Moka. What would be the challenges involved in porting Moka to the Capella ecosystem? Capella uses the Arcadia method, inspired by SysML, and Moka uses UML, so I was really just interested in getting the execution engines and writing the language interface myself. Any insights from some more experienced members would be appreciated!
Edit: after taking a look at the Moka architecture, it seems to me that the engine itself is abstracted from the language (Kernel APIs). In that case, would it be enough to simply rewrite UML implementations (like engine.uml, moka.fuml) to work with Capella Metamodels? Also, why is Mosquitto used here? Is there a detailed documentation available for Moka?
[Updated on: Wed, 07 December 2022 19:17] Report message to a moderator |
|
|
|
| Re: Papyrus Moka in Capella [message #1856473 is a reply to message #1856429] |
Mon, 12 December 2022 13:59  |
Matheus Cogo
Messages: 2
Registered: December 2022 |
Junior Member |
|
|
Hi, Pauline, thank you for the reply.
So the needed refactoring to make this work with Capella seems to be:
- Add the new language standard (as opposed to UML - by the way, yes, it is based on UML but closer to SysML. There are still some simplifications if I'm not mistaken) - ARCADIA.
- Refactor services to work with Capella ecosystem (animation, for example, would probably be done with Sirius).
Lastly, was there a reason to use MQTT locally? Wouldn't simple plugin handlers be enough to share information needed with services?
[Updated on: Mon, 12 December 2022 14:07] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.03081 seconds
] 
Search
Help
Register
Login
Home
