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.
Difference between revisions of "Papyrus/Neon Work Description/Improvements/Model Refactoring"
| Line 16: | Line 16: | ||
* The user should be able to launch the refactoring from Papyrus's added interfaces such as a menu items. | * The user should be able to launch the refactoring from Papyrus's added interfaces such as a menu items. | ||
| + | |||
| + | === Navigation through the tool === | ||
[[File:Papyrus_Refactoring_Lifecycle_Sequence.png|thumb|center|400px|alt=Papyrus Refactoring Lifecycle]] | [[File:Papyrus_Refactoring_Lifecycle_Sequence.png|thumb|center|400px|alt=Papyrus Refactoring Lifecycle]] | ||
Revision as of 12:50, 5 April 2016
Overview
This tool should allow the user to easily refactor a created model by applying a transformation on the model's selected elements previously requiring the user to edit them each by hand.
User perspective
- The user should have the possibility to visualize, without modification of the model, the changes brought by the refactoring; i.e. display the model should the refactoring be accepted.
- Once this is done the user should be able to accept the refactoring or cancel it, retrieving its pristine model.
- During this visualization the user should be able to decide which elements should be affected by the transformation
- The user should be warned if the refactoring should corrupt its model. As a rule of thumb a model is considered corrupted if it does not respect the constraints of the metamodel or applied profiles.
- Once the refactoring is accepted the user should be able to undo all of it, returning to the initial state of the model.
- The user should be able to launch the refactoring from Papyrus's added interfaces such as a menu items.
