|Multiple domain modeling using Sirius [message #1819290]
||Sun, 12 January 2020 07:03
| Avi Shaked
Registered: October 2019
One of the things I like best about Sirius is its minimalist, build-up approach to models. Unlike in other modeling tools, the end-user is not overloaded with options, does not need to select appropriate pallet and model integrity is maintained through the packaging structure based on the meta-model (the ECORE model).
However, these features also have a significant drawback when one tries to combine multiple domain-specific modeling into the same model. For comparison, in commercial modeling environments, one can use "stereotypes" for adding a domain-specific representation to existing elements.
The issue is especially pressing when one tries to extend existing Sirius implementation. Some examples of potential use cases:
- Model a process using BPMN Designer (a DSM over Sirius) and extend it with a specific BPMN extension (such as PE-BPMN).
- Extend Capella with a new system modeling perspective.
I would love to know if and how you approach such integration between various Domain Specific Models using Sirius. I would prefer not to have the same element appear separately in multiple models (a main point in Model Driven Engineering is to have a single source of truth, right?).
Also, specifically, I would appreciate your thoughts and/or guidance regarding the correct/desirable way to extend existing Sirius implementations. I would prefer to implement such extensions in a way which preserves the ability to upgrade the existing implementations once an update become available (to benefit from new features and bug corrections).
Powered by FUDForum
. Page generated in 0.08558 seconds