Modeling Project as a DSL Toolkit - Eclipse Modeling Project: A Domain-Specific Language Toolkit - page 23

bpmn.gmfgraphh scerario.ecore

scenario.gmfmap

MM

common.ecore
(TPTP)

scenario2testsulte.qvto requirements.ecore

Figure 2-7 Scenario DSL artifacts

dnc.encore oocore.encore

dnc.gmfmap

java.ecore

MM MT MT MT MT

dnc2jee.qvto jem2java.xpt dnc2java.xpt NodeEditPart.xpt* Class.javajet*

Figure 2-8 Color modeling DSL artifacts

Extending this set of sample projects involves many possibilities, such as pro-
ducing BPEL from BPMN-based scenario diagrams, transforming business
domain and scenario diagrams to and from their UML counterparts, transform-
ing scenarios to Eclipse cheat sheets, extending the mindmap to display task
information with a diagram better suited for temporal display (such as a Gantt
chart), synchronizing tasks in mindmaps with Bugzilla entries using an M2M,
and so on. All of these come to mind as feasible options using familiar techniques
and a common metamodel by leveraging the Modeling project for DSL and
model-driven software-development techniques. Of course, these extensions are
left as exercises for the reader.
Figures 2-9 through 2-11 illustrate sample application artifacts and how they
relate, using the notation introduced earlier. From the Practitioner's perspective,
mindmap, scenario, and business models are created and viewed with correspon-
ding diagrams. The requirements model can be produced from a mindmap model
and edited with a diagram and corresponding editor. The mindmap and require-
ments models can produce reports using M2M and M2T transformations.