Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MDT/Papyrus/Model-Based-Tracing-of-UML-models-in-Papyrus"
(New page: =Profile Management and lifecycle= ==Modeling OCL constraints== Bugzilla : [https://bugs.eclipse.org/bugs/show_bug.cgi?id=370815 Bug 370815] It should be possible to model OCL constraint...) |
(→Profile Management and lifecycle) |
||
Line 1: | Line 1: | ||
− | = | + | =Model Based Tracing of UML models in Papyrus= |
− | == | + | ==Tracing support== |
Bugzilla : [https://bugs.eclipse.org/bugs/show_bug.cgi?id=370815 Bug 370815] | Bugzilla : [https://bugs.eclipse.org/bugs/show_bug.cgi?id=370815 Bug 370815] | ||
Line 16: | Line 16: | ||
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. | 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. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 09:15, 29 May 2012
Model Based Tracing of UML models in Papyrus
Tracing support
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.