Meta-modeling technique: Difference between revisions

Content deleted Content added
moving to metamodel
MDE (talk | contribs)
Cleaning and progressive transport Metamodel
Line 1:
{{mergeto|Meta-model}}
{{mergeto|Meta-modeling}}
 
The following discussion can be viewed as a detailed application of [[Meta-modeling|metamodeling]] techniques, related to [[Model Driven Engineering]]. In software engineering, data engineering and software engineering, the use of [[Model|models]] is more and more recommended. this should be contrasted with the classical code-based development techniques. A [[Model|model]] always conform to a unique [[Meta-model|metamodel]]. One of the currently most active branch of [[Model Driven Engineering]] is the approach named [[model-driven architecture]] proposed by [[OMG]]. This approach is based on the utilization of a language to write metamodels called the [[Meta-Object Facility|Meta Object Facility or MOF]]. Typical metamodels proposed by [[OMG]] are [[Unified Modeling Language|UML]], [[SysML]], SPEM or CWM. All the languages presented below could be defined as MOF [[Meta-model|metamodels]].
 
The recommended standard orthography is ''metamodeling'' (see for example [http://www.metamodel.com/], [http://www.modelsconference.org/], [http://www.isis.vanderbilt.edu/publications/archive/Ledeczi_A_9_5_2001_On_Metamod.pdf], etc.); the alternative ''meta-modeling'' is also sometimes used, less and less frequently. The current trend seems now to write "metamodel" and not "meta-model", "metamodeling" and not "meta-modeling". This is consistent with classical usage like [[Metaphysics]], [[Metaprogramming]], [[Metacognition]], [[Metamathematics]], [[Metalogic]], [[Metalanguage]], etc.
 
== Examples of metamodeling approaches==