You can use this glossary to understand MDriven terms when you model systems in MDriven Designer.
Metamodel
A metamodel is a model that defines the structure another model is expected to follow. In MDriven, a metamodel can describe the model elements that tools and definitions work with, rather than the business domain represented by your model.
For example, Modlr was built from a metamodel: the metamodel was used as the basis for the Modlr logic. A plugin model file contains its metamodel, but when MDriven Designer reads plugins, it ignores that metamodel and assumes that the plugin's ViewModels adhere to it.
This lets you create definitions that operate on the model itself. For example, a plugin ViewModel can search the classes in the model, rather than present business data to an application user.
Metamodel and ModelMeta
Do not confuse a metamodel with ModelMeta. ModelMeta is a model-information export used to document and navigate a specific model. Exporting a Model Information File (.mif) creates a ModelMeta model containing ViewModels, actions, classes, state machines, and information about expression usage. You can upload that file to ModelMetaViewer to search and cross-reference the exported model.
| Term | What it describes | Example |
|---|---|---|
| Metamodel | The structure that another model or definition is expected to follow. | A plugin ViewModel adheres to the metamodel assumed when MDriven Designer loads the plugin. |
| ModelMeta | Information exported from a specific model for documentation, search, and cross-reference. | A .mif export shows where a class attribute or association end is used.
|