Hello Researchers,
I am working on a meta-model in the automotive field therefore i am looking for:
1) A guideline that defines which concepts should be put on the meta-model (MOF M2) and which on the meta-model (MOF M1).
2) Example meta-models
Example Engine-Concept:
M2: Engine
M1: Electric-Engine
M0: Induction Motor, Bosch, 100kW, SerialNr:123
Thank you for your help!
Dear Martin,
I suggest to have a look at this specification:
http://www.omg.org/spec/MOF/2.4.1/PDF
And the following books which can help you to improve your modelling skill well:
https://www.amazon.com/Model-Driven-Software-Engineering-Practice-Synthesis/dp/1627057080
https://www.amazon.com/MDA-Explained-Architecture%C2%BF-Practice-Promise/dp/032119442X
Regards,
Alireza
M0 is concerned with the real world (or code execution).
M1 is a model of M0, i.e. a representation of the real world using a specific modelling language (UML, BPMN, ERD, etc.).
M2 is a model of the modelling language used in M1, i.e. a meta-model.
M3 is a model of the modelling language used in M2, i.e. a meta-meta-model. It can be sued to model itself.
Different modelling languages can be used in M1 to represent different perspectives of M0. All those modelling languages need to be represented with their own meta-model in M2. M3 is the level where the modelling language used to represent all modelling languages in M2 is defined. There is only one modelling language at M3 and it is usually a simplified version of the UML class diagram meta-model.
Towards a precise definition of the OMG/MDA framework
Jean Bézivin, Olivier Gerbé
Proceedings. 16th Annual International Conference on Automated Software Engineering, 2001 (ASE 2001)
http://ai2-s2-pdfs.s3.amazonaws.com/6586/b19c6edf8850ac97fffb4ea6f65144200b1b.pdf
Thank you all for your help, lets sum it up:
- All the domain specific concepts which are needed by the domain users have to be packed into the metamodel (MOF M2)
- M1 models are models decribed with the metamodel (M2), different models (M1) are used to describe perspectives of model (M0)
- M0 models are the real word/code exectution
With that another question anrises ?
If i create one metamodel and my domain users operate at different level of abstraction the concepts relevant for the metamodel will be different. How to tackle that in the metamodel M2 ?
e.g. for my user group 1 "CAR" is an important aspect but for my 2 user group "ELECTRIC CAR" is important. Should i add now the concept "CAR" or "ELECTRIC CAR"?
"Normaly" i would solve that with a generalization releation between ELECTRIC CAR and CAR but that makes the metamodel very fast overloaded and hard to read.
Best Regards,
Martin
Dear Dominik,
Thank you for your support.
- I will think about using attributes for specializing my "super classes" of the metamodel M2.
- I will also use different views on the model: one management view and one or more developers view.
Best Regards,
Martin
I suggest using a view-oriented system modelling. Science a Metamodel cannot cover the whole system aspects. Moreover, the MDA community claimed using different kind of models to represent system views at different abstraction levels and software manufacturing steps. For instance CIM, PIM, PDM, PSM.
- Badges
- Science topic
- Similar topics
- Engineering
- Modeling