Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
MDT/Papyrus/Model-Based-Tracing-of-UML-models-in-Papyrus
Contents
Profile Management and lifecycle
Modeling OCL constraints
Bugzilla : Bug 370815
It should be possible to model OCL constraints for a profile, with a specific OCL editor. It should be possible to generate an EMF Validation plug-in from these constraints. The constraints should be validated either in real-time or in batch-mode, according to a user preference. It should be possible to define this preference either globally or constraint by constraint.
Concretely, this will be realized in three steps:
- Embedding the OCL X-Text editor in the property view, and associating it to UML Opaque expressions using the OCL language
- Creating a generator, which inputs a Profile and outputs an EMF Validation plug-in
- If necessary, adapt the Papyrus validation framework
Profile evolution
Bugzilla : Bug 370816
Profiles defined in the workspace typically evolve quickly. They should be automatically re-applied when the users open a diagram for the first time after the profile has evolved. The user should be asked whether the modification is ok or not.
Model/Profile packaging
Bugzilla : Bug 370817
When packaging a Model on which a local profile is applied, the Profile should also be packaged, either in the same plug-in or in another plug-in.
Import by copy
Bugzilla : Bug 370818
Currently, the only import option available in Papyrus is an external reference to another model. It should also possible to import an external model (Or subset of a model) by copying it.