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

A scenario model is transformed into a TPTP Manual Test model, for use in
its editor. Scenario models can also be embedded within requirements models.
The business model is transformed first to a Java EMF Model (JEM) and
then to text as Java class files. Alternatively, the business model is transformed
directly to Java classes using Xpand templates.
Figure 2-12 shows a Practitioner's workspace with each of the artifacts rep-
resented. The four open diagrams in the editor are the mindmap in the upper left,
the scenario in the upper right, the requirements in the lower left, and the color
modeling diagram in the lower right. The outline view shows the content of the
requirements editor, which is also visible using the Selection page in the editor
itself.

Figure 2-12 Practitioner's view of sample projects

The workspace has two projects, with the second being the target of the Java
code generation from the color model instance. The main project contains all the
Practitioner models and generated artifacts, other than Java. The mindmap CSV
output, requirements HTML report, mindmap XHTML report, intermediate
JEM, and TPTP test suite are all found in the org.eclipse.example project.
Also seen is a types.xmi file used by the color business domain model.