Meta-modeling technique: Difference between revisions

Revision as of 16:46, 8 May 2006

Revision as of 16:52, 8 May 2006

Line 2:

{{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 [[Modelmodel-driven Driven Architecturearchitecture]] 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]].

One important move in [[Model Driven Engineering]] is the systematic use of [[Model Transformation Language]]s. The OMG has proposed a standard for this calld [[QVT]] for Queries/Views/Transformations. [[QVT]] is based on the [[Meta-Object Facility]] or MOF. Among many other [[Model Transformation Language]]s (MTLs), some examples of implementations of this standard are [[AndroMDA]], [[VIATRA]] or [[ATLAS Transformation Language|ATL]].