1
$\begingroup$

Where is the difference between a "meta model" and "design patterns"?

If you take, for example, Fowlers "Identity Field" from his book "Patterns Of Enterprise Application Architecture": Why is this a pattern and not a meta model?

Thanks!

$\endgroup$
1
$\begingroup$

Design Pattern: It is a "good practice". It can be considered as a possible solution for a problem that may ofter occur. The solution usually comes from the experience. Examples are MVC and Identify Field.

Metamodel: It can be considered as a set of rules, constraints and constructs that allow to model a problem. As an example you can consider a map.

enter image description here

A map allows to model the reality, so a map can be considered the model. The metamodel of a map is the legend: the constructs that you need to use in order to represent borders, rivers, lakes,...

In your case Identify Field is just a good practice that you can decide to follow or not. It's not a constraint/rule.

$\endgroup$
  • $\begingroup$ Thanks! Is this also stated somewhere in literature, so that I can cite it? $\endgroup$ – powerweb Apr 24 '17 at 5:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.