This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Model Driven Engineering"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (New page: category:RIMBAA Issue Model Driven Engineering( MDE) aims to raise the level of abstraction in program specification and increase automation in program development. The idea promoted b...) |
Rene spronk (talk | contribs) |
||
| Line 4: | Line 4: | ||
Most [[RIMBAA]] implementations are examples of a MDE effort. | Most [[RIMBAA]] implementations are examples of a MDE effort. | ||
| − | *See [http://www.theenterprisearchitect.eu/archive/2009/01/15/mde---model-driven-engineering----reference-guide blogpost explaining MDE terms]. | + | *See [http://www.theenterprisearchitect.eu/archive/2009/01/15/mde---model-driven-engineering----reference-guide blogpost explaining MDE terms], [http://en.wikipedia.org/wiki/Model-driven_engineering MDE in Wikipedia]. |
Revision as of 14:12, 2 November 2009
Model Driven Engineering( MDE) aims to raise the level of abstraction in program specification and increase automation in program development. The idea promoted by MDE is to use models at different levels of abstraction for developing systems, thereby raising the level of abstraction in program specification. An increase of automation in program development is reached by using executable model transformations. Higher-level models are transformed into lower level models until the model can be made executable using either code generation or model interpretation.
Most RIMBAA implementations are examples of a MDE effort.
