Misplaced Pages

Model-driven engineering: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 03:07, 28 April 2007 edit88.6.141.172 (talk) →See also← Previous edit Revision as of 20:01, 15 May 2007 edit undo193.209.12.111 (talk) →External linksNext edit →
Line 33: Line 33:
* *
* *
* An independent organization of DSM tool vendors, practitioners and experts.
* DSM environment from MetaCase




Revision as of 20:01, 15 May 2007

This article provides insufficient context for those unfamiliar with the subject. Please help improve the article by providing more context for the reader. (Learn how and when to remove this message)

Model-Driven Engineering (or MDE) refers to the systematic use of models as primary engineering artifacts throughout the engineering lifecycle. MDE can be applied to software, system, and data engineering. Models are considered as first class entities. The best known MDE initiative is the Object Management Group (OMG) called Model-Driven Architecture (MDA), which is a registered trademark of OMG. Another related acronym is Model-Driven Development (MDD) which is an OMG trademark.

As it pertains to software development, Model-Driven Development refers to a range of development approaches that are based on the use of software modeling as a primary form of expression. Sometimes models are constructed to a certain level of detail, and then code is written by hand in a separate step. Sometimes complete models are built including executable actions. Code can be generated from the models, ranging from system skeletons to complete, deployable products. With the introduction of the Unified Modeling Language (UML), MDD has become very popular today with a wide body of practitioners and supporting tools. More advanced types of MDD have expanded to permit industry standards which allow for consistent application and results. The continued evolution of MDD has added an increased focus on architecture and automation.

MDD technologies with a greater focus on architecture and corresponding automation yield higher levels of abstraction in software development. This abstraction promotes simpler models with a greater focus on problem space. Combined with executable semantics this elevates the total level of automation possible. The Object Management Group (OMG) has developed a set of standards called Model Driven Architecture (MDA), building a foundation for this advanced architecture-focused approach.

Model Integrated Computing is yet another branch of MDE.

According to Douglas Schmidt, model-driven engineering technologies offer a promising approach to address the inability of third-generation languages to alleviate the complexity of platforms and express domain concepts effectively.

See also

References

  1. ^ Object Management Group (2006-05-24). "OMG Trademarks". Retrieved 2006-07-17.
  2. Schmidt, D.C. (2006). "Model-Driven Engineering" (PDF). IEEE Computer. 39 (2). Retrieved 2006-05-16. {{cite journal}}: Unknown parameter |month= ignored (help), "A promising approach to address platform complexity — and the inability of third-generation languages to alleviate this complexity and express domain concepts effectively — is to develop Model-Driven Engineering (MDE) technologies..."

External links

Categories: