model transformation from bpmn to devs in a prototype implementation of the mdd4ms framework
DESCRIPTION
Presentation at the 2nd International Workshop on Model-driven Approaches for Simulation Engineering (held within the SCS/IEEE Symposium on Theory of Modeling and Simulation part of SpringSim 2012) Please see: http://www.sel.uniroma2.it/mod4sim12/ for further detailsTRANSCRIPT
Model Transformation from BPMN to DEVS in the MDD4MS Framework
Deniz Cetinkaya, Alexander Verbraeck and Mamadou D. Seck
27 March 2012,Orlando, FL
2/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Outline
•MDD4MS Framework
• M&S Life-cycle
• Metamodeling: Models and Metamodels
• Model Transformations
• Tool Architecture for MDD4MS
•BPMN to DEVS Transformation
• BPMN Metamodel
• DEVS Metamodel
• Transformation Rules from BPMN to DEVS
•Conclusion
3/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
1.
MDD4MS Framework
4/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
M&S Life-cycle
Problem Definition
Conceptual Modeling
Specification
Implementation
Experimentation
Validation
Verification
5/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Outputs of the M&S Life-cycle
Stage Output Output Type Output Format
Problem Definition
Source System Requirements
Generally a written document
Expressed in a natural language
Conceptual Modeling
Conceptual Model A visual and/or textual conceptual model
Defined by a well-defined conceptual modeling language
Specification Platform Independent Simulation Model
A visual and/or textual simulation specification
Defined by a specification language for a certain formalism
Implementation Platform Specific Simulation Model
Compiled or executable source code
Written in a programming language or automatically generated
Experimentation Experimentation Results
Output of the simulator Depends on the simulator
6/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Why MDD for M&S? • Simulation conceptual modeling is performed mostly
with general purpose diagramming techniques and tools.
• There is a lack of tool support during the entire simulation model development life-cycle.
• The conceptual models are not explicitly reused in the further stages as formal model transformation methods are not available.
•MDD will be a cost and effort saving solution. As well as, existing MDD tools and techniques can be utilized.
• This research applies MDD principles into M&S in order to obtain the model continuity throughout the M&S life-cycle.
7/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Metamodeling Layers in MOF
Meta-metamodel
Metamodel
Model
Information
M3 Level
M2 Level
M1 Level
M0 Level
MOF Model
Application Metamodel
Application MetaData
Application Data
8/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
M0 level
M1 level
M2 level
M3 level M&S
Meta-Metamodel
conforms to
Simulation Conceptual
Model (CM)
Platform Specific
Simulation Model (PSSM)
Platform Independent
Simulation Model (PISM)
Simulation Model
Implementation Metamodel
Conceptual Modeling
Metamodel
Simulation Model
Specification Metamodel
conforms to conforms to conforms to
Simulation
Conceptual Model (CM)
MetaData
Platform Specific
Simulation Model (PSSM)
MetaData
Platform Independent
Simulation Model (PISM)
MetaData
conforms to conforms to conforms to
instance of instance of instance of Model transformations (M&S life-cycle stages)
Meta
modelin
g
MDD4MS Framework
9/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Tool for Simulation Conceptual Modeling
Role: Simulation Programmer
Role: Conceptual Modeler
ModelToModel Transformer
Simulation Conceptual Model
(CM)
Tool for Simulation Model Implementation
Platform Specific Simulation Model
(PSSM)
Tool for Simulation Model Specification
Platform Independent Simulation Model (PISM)
ModelToModel Transformer
Modeling and Simulation Environment
Role: Simulation Modeler
Requirements
Problem Owner uses
prepares
uses
prepares
uses
prepares
ModelToCode Transformer
Simulator
Role: Simulation Expert
Results Computer
executable PSSM
Tool Architecture for MDD4MS
10/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
MDD4MS Prototype
11/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
2.
BPMN to DEVS Transformation
12/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
A case study: MDD of executable
DEVS from BPMN
Modeling Layer
Metamodeling Layer
Simulation Conceptual Model
(CM)
Platform Specific DEVSDSOL
Model (PSSM)
Platform Independent DEVS
Model (PISM)
DEVSDSOL Implementation
Metamodel
instance of
BPMN Conceptual Modeling
Metamodel
DEVS Specification Metamodel
ModelToModel Transformation
ModelToModel Transformation
instance of instance of
13/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
BPMN Metamodel
14/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Conceptual Modeling with BPMN
15/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
DEVS Metamodel
16/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Model to model transformation with ATL
Generating Visual DEVS Model
17/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Generating Executable DEVSDSOL Model
Model to code transformation with Java
18/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Running the Generated Code
19/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Transformation Rules from
BPMN to DEVS •The transformation is written in ATL (ATLAS Transformation Language).
•The transformation has two steps: • In the first step, all BPMN model elements are transformed to specific DEVS elements; and all connections are transformed to internal couplings.
• In the second step, external input couplings and external output couplings are defined for nested components.
•The transformation satisfies syntactic correctness, completeness, readability and efficiency criteria.
20/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Transformation Pattern
21/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Hierarchical Models
•the source component is nested n levels. • n * DEVS Output Port
• n * DEVS EOC Connection
•the target component is nested m levels. • m * DEVS Input Port
• m * DEVS EIC Connection
22/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
3.
Conclusion
23/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Advantages of MDD Approach
•Availability of the existing MDD tools and techniques.
•Formal definition of the models and modeling languages.
•Good understanding of the conceptual models by different parties.
•More efficient and error-free simulation model implementation.
24/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Conclusion
•This research applies MDD principles into M&S in order to obtain the model continuity throughout the M&S life-cycle.
•In this work, a procedural DEVS metamodel, a BPMN metamodel and a model transformation from BPMN to DEVS are presented.
•The BPMN to DEVS transformation proves that the gap between the conceptual modeling and specification stages can be filled in by MDD approach.
25/25 Model Transformation from BPMN to DEVS in the MDD4MS Framework
Questions?
Deniz Cetinkaya [email protected]
Alexander Verbraeck
Mamadou D. Seck [email protected]
Thank you.