Abstract

This report developes the idea of a visual graphical editor for Epsilon and the process of developing it.
A fully working epsilon workflow builder and visualizer is also presented that helps users to compose Epsilon workflows and construct visual representations from textual ones.

Statement of Ethics

Why EWE ? What is the need ?
Workflow inherently visual - flow of order of tasks.
e.g. BPM tools all provide editors.
MDE is essentially a sequence of steps from start to finish.
Other model management languages, frameworks tools provide it as well. (Atlas, OpenAW, etc)
Therefore Epsilon, needs one too.

Documents the process of building such a tool using MDE techniques and Epsilon itself.

Introduce ALL concepts and technologies that are critical to understanding the tool.
Model driven engineering - tasks involved. Tasks constitute a workflow.
How does Epsilon handle it ? Internal architecture of Epsilon Workflow.
ANT, Java Modules, Eclipse Launch configuration, Working outside Eclipse.
Introduce idea of domain modeling. Separate the concern of design and architecture. This is the CORE idea.
Eclipse EMF technologies. How EMF supports Domain Modeling. Give a simple Library example.
- Library domain is expressed. An Editor for the domain is generated - but uses unique architecture. e.g. Adapter, Factory and Command patterns - which WE never specified while modeling the domain.
Make sure this concept is well understood. MDE in general and how EMF tools support MDE with practical examples.
Eclipse graphical technologies GEF -> SWT, JFace.
Eclipse GMF as a bridge between GEF and EMF.
How GMF is Model based and Generative
How it fits well for Epsilon since both are based on EMF.
Introduction to EuGENia.