This diagram shows the development process of this project.
In short:
(1) "Business Modeling"
First a bit of business modeling is done to get the business class diagram "model/source/darlehen.uml".
(2) "M2M Transformation"
The next step is model transformation from "model/source/darlehen" (= umlfk) to "model/target/darlehen" (= umlejb). The target model realizes some aspects of an EJB based architecture. The model transformation is done
- either with a Relations Language script "qvt/UML2EJB.qvt"
- or with an Operational Mappings script "qvt/UML2EJB.qvto".
(3) "Conceptual Modeling"
Now you can do some more design and PSM modeling on the target model, for instance defining data types. That modifies the umlejb model "model/target/darlehen" in some way.
(4) "MTL Transformation"
The umlejb model is the input of a model2text transformation, "src/Generator/files/generateJava.mtl" and the modules "src/uml2java/*.mtl", to get the Java sourcecode, "gen_src/darlehen/*".
We may need some additional architecture modeling activities to build a metamodel and/or a profile:
(5) "Metamodeling"
The class modeling is done with UML2. It is also possible to build a modeling
language "SimpleUML" for modeling simple class diagrams. We did it, "model/metamodel/Ecore", but we won't use it.
(6) "Profile Development"
We need an UML-Profile "model/profile/UMLEJB-Profil" for marking the EJB candidates of the source-model with the stereotype "entity".