Metamodeling Process Overview

Generally, one builds up metamodels from available components. Thus, the overall process looks like:

• The modeling starts by defining reusable attributes promoting data standardization among business objects. These attributes can be of any basic type (e.g., integer, string, date, or enumeration), In addition, there are more interactive types like (email, web URL, or phone number), which allow one to send an email, make a phone call, etc., from within the implemented model when it is populated.
• Business objects are then created based on these reusable attributes and custom associations can be created, including regular reference relationships, composition links (UML aggregations), and UML generalization allowing you to define abstract business objects.
• Finally, business objects are associated to custom models, ready to be populated. MM is pre-populated with a few standard (system read only) custom models (starting with the glossary model) and a few model extensions. Associations can therefore refer to business objects across different custom models.

Users can then go to the user interface for data entry, analysis, and reporting on instantiated custom models, In fact, in the UI, custom models are presented with the same capabilities as are (harvested) technical models, including their use in the Metadata Query Language (MQL), Worksheets, and Dashboards. In addition, custom models also have a hierarchy tab allowing you to drill down in both data entry (including bulk editing) and reporting. Workflow may also be applied to particular custom models, as with the glossary.

Integrators have external bulk editing/reporting available through CSV import/export capabilities, as well as the REST API, allowing you to define actual connectors (bulk or real time synchronization) with external tools / applications behind the business or an organizations custom DQ applications for their business rule model.