ReVision is configured for a particular modeling language by a set of consistency-preserving edit operations. All generated edit operations for Ecore can be browsed here. The editing operations were generated by a set of patterns specified for each consistency rule.
- The edit operations are grouped by their context, the pattern from which they were derived, and the corresponding consistency-rule(s).
- A consistency-rule is annotated with <<constraint>>.
- A consistency-preserving edit operation is annotated with <<rule>>.
- Select a pattern or an edit operation to view the graph or transformation rule.
- Note: The (edge) labels can be moved by Drag’n’Drop.
Example: Interface, Abstract and Concrete Class
- <<constraint>> AClassThatIsAnInterfaceMustAlsoBeAbstract
- Concrete Class
- Abstract Class
- Interface
- <<rule>> Create: Abstract Class
- <<rule>> Delete: Abstract Class
- <<rule>> Transform: Abstract Class - To - Concrete Class
- <<rule>> Transform: Abstract Class - To - Interface
- <<rule>> Create: Concrete Class
- <<rule>> Delete: Concrete Class
- <<rule>> Transform: Concrete Class - To - Abstract Class
- <<rule>> Transform: Concrete Class - To - Interface
- <<rule>> Create: Interface
- <<rule>> Delete: Interface
- <<rule>> Transform: Interface - To - Concrete Class
- <<rule>> Transform: Interface - To - Abstract Class