Java Reference
In-Depth Information
Because we're basing the notation for our Scenario diagram on the Business
Process Modeling Notation (BPMN) standard, we could simply use its descrip-
tion of the underlying domain model and semantics to develop our DSL. A bet-
ter approach would have been to find an XSD for BPMN and simply import it
into EMF. Unfortunately, no such schema is published with the specification—
even worse, a new specification from the OMG, the Business Process Definition
Metamodel (BPDM), is slated to provide a domain model for BPMN2. Also
unfortunate is that this specification has no serialized format that we can use and
is overly complicated for our Scenario DSL. This leaves us to create our own sce-
nario model.
In a new
org.eclipse.dsl.scenario
project, we can create our
sce-
nario.ecore
model as the base of our fictitious Requirements Scenario Project
(RSP) project. Figure 3-8 is the model to create using our Ecore diagram.
Figure 3-8
Scenario domain model
Elements of a scenario model are maintained in the
Process
class, which
itself extends
Element
. A
Connection
maintains target and source references
for
Elements
that are connected in
Sequence
or
Message
flows. An
Association
also connects elements.
Elements
come in a variety of types,
including
Tasks
,
Events
,
DataObjects
, and
Gateways
. These elements all
map in a straightforward manner to notation elements because the model is
Search WWH ::
Custom Search