This parameter indicates if an object belongs to the metamodel layer or to the meta-metamodel layer of the MOF (Meta Object facility) architecture.

Do not set a value for this property if you are not an expert.

 

The MEGA Software environment is based on a four-layer architecture as standardized by the OMG:

 

- M0: The information layer comprises data of the 'real world' which the user describes using MEGA products. (e.g. 'Alan Smith')

 

- M1: The model layer comprises models that describe data in the information layer. Since MEGA software is a true modeling environment, we can say that this is the 'MEGA world' (e.g. 'Sales Director')

 

- M2: The metamodel layer comprises several domain-specific metamodels. A metamodel is an "abstract language" defined to write models. A set of concepts relating to the domain being modeled. MEGA products provide an extensive collection of such metamodels, for example the UML metamodel, the workflow (BPMN) metamodel and the business process metamodel. These metamodels can be modified or extended to suit specific requirements. 'Metamodel' is the default value and should be used for extensions. (e.g. 'Org-Unit')

 

- M3: The meta-metamodel layer comprises the 'top level' metamodel required to describe any type of metamodel.

 

The MEGA meta-metamodel complies with the MOF (Meta Object Facility) recommendations of the OMG. It is reflexive, i.e. able to define itself as well as any type of metamodel. MOF is a very high level standardized metamodel, modification of which we do not recommend. Conventionally, meta-meta-objects are prefixed 'Meta'. (e.g. 'MetaClass')