Model-driven engineering: Difference between revisions

From HandWiki
imported>CodeMe
linkage
 
Jport (talk | contribs)
0 edits
update
 
Line 1: Line 1:
{{Short description|Software development methodology}}
{{Short description|Software development methodology}}
{{more footnotes|date=August 2014}}
{{Software development process}}
{{Software development process}}
'''Model-driven engineering''' ('''MDE''') is a software development methodology that focuses on creating and exploiting [[Domain model|domain model]]s, which are [[Conceptual model (computer science)|conceptual models]] of all the topics related to a specific problem. Hence, it highlights and aims at [[Representation (mathematics)|abstract representations]] of the [[Knowledge representation and reasoning|knowledge]] and activities that govern a particular [[Software:Domain (software engineering)|application domain]], rather than the computing (i.e. algorithmic) concepts.
'''Model-driven engineering''' ('''MDE''') is a software development methodology that focuses on creating and exploiting [[Domain model|domain model]]s, which are [[Conceptual model (computer science)|conceptual models]] of all the topics related to a specific problem. Hence, it highlights and aims at [[Representation (mathematics)|abstract representations]] of the [[Knowledge representation and reasoning|knowledge]] and activities that govern a particular [[Software:Domain (software engineering)|application domain]], rather than the computing (i.e. algorithmic) concepts.


MDE is a subfield of a [[Software design|software design]] approach referred as [[Round-trip engineering|round-trip engineering]]. The scope of the MDE is much wider than that of the [[Model-driven architecture]].<ref>{{Cite web |title=8 Reasons Why Model-Driven Approaches (will) Fail |url=https://www.infoq.com/articles/8-reasons-why-MDE-fails/ |access-date=2023-07-26 |website=InfoQ |language=en}}</ref>
MDE is a subfield of a [[Software design|software design]] approach referred as [[Round-trip engineering|round-trip engineering]]. The scope of the MDE is much wider than that of the [[Model-driven architecture|Model-Driven Architecture]].<ref>{{Cite web |title=8 Reasons Why Model-Driven Approaches (will) Fail |url=https://www.infoq.com/articles/8-reasons-why-MDE-fails/ |access-date=2023-07-26 |website=InfoQ |language=en}}</ref>


== Overview ==
==Overview==
The MDE approach is meant to increase productivity by maximizing compatibility between systems (via reuse of standardized models), simplifying the process of design (via models of recurring design patterns in the application domain), and promoting communication between individuals and teams working on the system (via a standardization of the terminology and the [[Best practice|best practice]]s used in the application domain). For instance, in model-driven development, technical artifacts such as source code, documentation, tests, and more are generated algorithmically from a domain model.<ref>{{Cite book |last=Flatt |first=Amelie |title=Model-Driven Development of Akoma Ntoso Application Profiles - A Conceptual Framework for Model-Based Generation of XML Subschemas |last2=Langner |first2=Arne |last3=Leps |first3=Olof |publisher=Sprinter Nature |year=2022 |isbn=978-3-031-14131-7 |edition=1st |location=Heidelberg |language=en}}</ref>
The MDE approach is meant to increase productivity by maximizing compatibility between systems (via reuse of standardized models), simplifying the process of design (via models of recurring design patterns in the application domain), and promoting communication between individuals and teams working on the system (via a standardization of the terminology and the [[Best practice|best practice]]s used in the application domain). For instance, in model-driven development, technical artifacts such as source code, documentation, tests, and more are generated algorithmically from a domain model.<ref>{{Cite book |last=Flatt |first=Amelie |title=Model-Driven Development of Akoma Ntoso Application Profiles - A Conceptual Framework for Model-Based Generation of XML Subschemas |last2=Langner |first2=Arne |last3=Leps |first3=Olof |publisher=Sprinter Nature |year=2022 |isbn=978-3-031-14131-7 |edition=1st |location=Heidelberg |language=en}}</ref>


Line 11: Line 12:


Some of the better known MDE initiatives are:
Some of the better known MDE initiatives are:
* The [[Organization:Object Management Group|Object Management Group]] (OMG) initiative Model-Driven Architecture (MDA) which is leveraged by several of their standards such as [[Organization:Meta-Object Facility|Meta-Object Facility]], [[XML Metadata Interchange|XMI]], CWM, CORBA, [[Unified Modeling Language]] (to be more precise, the OMG currently promotes the use of a subset of UML called [[Executable UML#fUML and ALF|fUML]] together with its action language, [[Executable UML#fUML and ALF|ALF]], for model-driven architecture; a former approach relied on Executable UML and [[Object Constraint Language|OCL]], instead), and [[QVT]].<ref name="omgtm">{{cite web|author=Object Management Group|title=OMG Trademarks|url=http://www.omg.org/legal/tm_list.htm|access-date=2008-02-26|date=2006-05-24}}</ref>
* The [[Organization:Object Management Group|Object Management Group]] (OMG) initiative Model-Driven Architecture (MDA) which is leveraged by several of their standards such as [[Organization:Meta-Object Facility|Meta-Object Facility]], [[XML Metadata Interchange|XMI]], CWM, CORBA, [[Unified Modeling Language]] (to be more precise, the OMG currently promotes the use of a subset of UML called [[Executable UML#fUML and ALF|fUML]] together with its action language, [[Executable UML#fUML and ALF|ALF]], for model-driven architecture; a former approach relied on Executable UML and [[Object Constraint Language|OCL]], instead), and [[QVT]].<ref name="omgtm">{{cite web|author=Object Management Group|title=OMG Trademarks|url=https://www.omg.org/legal/tm_list.htm|access-date=2008-02-26|date=2006-05-24}}</ref>
* The [[Software:Eclipse|Eclipse]] "eco-system" of programming and modelling tools represented in general terms by the (Eclipse Modeling Framework). This framework allows the creation of tools implementing the MDA standards of the OMG; but, it is also possible to use it to implement other modeling-related tools.
* The [[Astronomy:Eclipse|Eclipse]] "eco-system" of programming and modelling tools represented in general terms by the (Eclipse Modeling Framework). This framework allows the creation of tools implementing the MDA standards of the OMG; but, it is also possible to use it to implement other modeling-related tools.


== History ==
==History==
[[File:Métamodèle, modèle et original.png|thumb|A chart showing the instantiations and representation links between a metamodel, a model and an original (in French).|250px|right]]The first tools to support MDE were the Computer-Aided Software Engineering (CASE) tools developed in the 1980s. Companies like Integrated Development Environments (IDE – StP), Higher Order Software (now Hamilton Technologies, Inc., HTI), Cadre Technologies, [[Biography:Charles Bachman#Bachman Information Systems|Bachman Information Systems]], and Logic Works (BP-Win and ER-Win) were pioneers in the field.


[[File:Métamodèle, modèle et original.png|thumb|A chart showing the instantiations and representation links between a metamodel, a model and an original (French?)|250px|right]]The first tools to support MDE were the Computer-Aided Software Engineering (CASE) tools developed in the 1980s. Companies like Integrated Development Environments (IDE - StP), Higher Order Software (now Hamilton Technologies, Inc., HTI), Cadre Technologies, [[Biography:Charles Bachman#Bachman Information Systems|Bachman Information Systems]], and Logic Works (BP-Win and ER-Win) were pioneers in the field.
The US government got involved in the modeling definitions creating the [[IDEF]] specifications. With several variations of the modeling definitions (see [[Booch method|Booch]], [[Object-modeling technique|Rumbaugh]], [[Object-oriented software engineering|Jacobson]], Gane and Sarson, [[State diagram#Harel statechart|Harel]], [[Shlaer–Mellor method|Shlaer and Mellor]], and others) they were eventually joined creating the [[Unified Modeling Language]] (UML). Rational Rose, a product for UML implementation, was done by Rational Corporation (Booch) responding 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 [[Organization:Object Management Group|Object Management Group]] (OMG) has developed a set of standards called [[Model-driven architecture|Model-Driven Architecture]] (MDA), building a foundation for this advanced architecture-focused approach.


The US government got involved in the modeling definitions creating the [[IDEF]] specifications. With several variations of the modeling definitions (see [[Booch method|Booch]], [[Object-modeling technique|Rumbaugh]], [[Object-oriented software engineering|Jacobson]], Gane and Sarson, [[State diagram#Harel statechart|Harel]], Shlaer and Mellor, and others) they were eventually joined creating the [[Unified Modeling Language]] (UML). Rational Rose, a product for UML implementation, was done by Rational Corporation (Booch) responding 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 [[Organization:Object Management Group|Object Management Group]] (OMG) has developed a set of standards called [[Model-driven architecture|model-driven architecture]] (MDA), building a foundation for this advanced architecture-focused approach.
==Advantages==
 
According to [[Biography:Douglas C. Schmidt|Douglas C. 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.<ref>{{cite journal|last=Schmidt|first=D.C.|title=Model-Driven Engineering|journal=IEEE Computer|volume=39|issue=2|date=February 2006|doi=10.1109/MC.2006.58|s2cid=10006139|url=https://www.cs.wustl.edu/~schmidt/PDF/GEI.pdf|access-date=2006-05-16|archive-url=https://web.archive.org/web/20060909034327/http://www.cs.wustl.edu/%7Eschmidt/PDF/GEI.pdf|archive-date=2006-09-09|url-status=dead}}, ''"A promising approach to address platform complexity&mdash;and the inability of third-generation languages to alleviate this complexity and express domain concepts effectively&mdash;is to develop Model-Driven Engineering (MDE) technologies..."''</ref>
== Advantages ==
According to [[Biography:Douglas C. Schmidt|Douglas C. 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.<ref>{{cite journal|last=Schmidt|first=D.C.|title=Model-Driven Engineering|journal=IEEE Computer|volume=39|issue=2|date=February 2006|doi=10.1109/MC.2006.58|s2cid=10006139|url=http://www.cs.wustl.edu/~schmidt/PDF/GEI.pdf|access-date=2006-05-16|archive-url=https://web.archive.org/web/20060909034327/http://www.cs.wustl.edu/%7Eschmidt/PDF/GEI.pdf|archive-date=2006-09-09|url-status=dead}}, ''"A promising approach to address platform complexity&mdash;and the inability of third-generation languages to alleviate this complexity and express domain concepts effectively&mdash;is to develop Model-Driven Engineering (MDE) technologies..."''</ref>


==Tools==
==Tools==
Notable software tools for model-driven engineering include:
Notable software tools for model-driven engineering include:
{{div col|colwidth=27em}}
{{div col|colwidth=27em}}
* AADL from Carnegie-Mellon Software Engineering Institute
* [[Architecture Analysis & Design Language|AADL]] from Carnegie-Mellon Software Engineering Institute
* Acceleo an open source code generator from Obeo
* [[Software:Acceleo|Acceleo]] an [[Open source|open source]] code generator from Obeo
* [[Software:Actifsource|Actifsource]]
* [[Software:Actifsource|Actifsource]]
* AgileUML an open source MDE toolset from AgileMDE Ltd
* AgileUML an open source MDE toolset from AgileMDE Ltd
* Ash Framework an open source Elixir-based declarative application framework
* [[ATLAS Transformation Language]] or ATL, a model transformation language from Obeo
* [[ATLAS Transformation Language]] or ATL, a model transformation language from Obeo
* [[Engineering:DUALLy|DUALLy]], an MDE framework to create interoperability
* [[Engineering:DUALLy|DUALLy]], an MDE framework to create interoperability
* Eclipse Modeling Framework (EMF)
* Eclipse Modeling Framework (EMF)
* [[Software:Enterprise Architect|Enterprise Architect]] from Sparx Systems
* [[Software:Enterprise Architect|Enterprise Architect]] from Sparx Systems
* [[Software:ETrice|eTrice]] an Open Source implementation of the [[Real-Time Object-Oriented Modeling]] standard
* [[Software:ETrice|eTrice]] an open source implementation of the [[Real-Time Object-Oriented Modeling]] standard
* [[Software:Generic Eclipse Modeling System|Generic Eclipse Modeling System]] (GEMS)
* [[Software:Generic Eclipse Modeling System|Generic Eclipse Modeling System]] (GEMS)
* [[Software:GeneXus|GeneXus]] a Knowledge-based, declarative, multi-platform, multi-language development solution
* [[Software:GeneXus|GeneXus]] a knowledge-based, declarative, multi-platform, multi-language development solution
* [[Software:Graphical Modeling Framework|Graphical Modeling Framework]] (GMF)
* [[Software:Graphical Modeling Framework|Graphical Modeling Framework]] (GMF)
* JetBrains MPS, a [[Metaprogramming|metaprogramming]] system from [[Company:JetBrains|JetBrains]]
* JetBrains MPS, a [[Metaprogramming|metaprogramming]] system from [[Company:JetBrains|JetBrains]]
* [[Software:MagicDraw|MagicDraw]] from No Magic Inc
* [[Software:MagicDraw|MagicDraw]] from No Magic Inc
* MDriven – a UML-based, model-driven development platform that generates .NET and web applications from executable models.
* [[MERODE]] JMermaid from KU Leuven (educational)
* [[MERODE]] JMermaid from KU Leuven (educational)
* MetaEdit+ from MetaCase
* [[Software:MetaEdit+|MetaEdit+]] from MetaCase
* ModelCenter from Phoenix Integration
* [[Software:ModelCenter|ModelCenter]] from Phoenix Integration
* [[Software:Open ModelSphere|Open ModelSphere]]
* [[Software:Open ModelSphere|Open ModelSphere]]
* [[Software:OptimalJ|OptimalJ]] from [[Company:Compuware|Compuware]]
* [[Software:OptimalJ|OptimalJ]] from [[Company:Compuware|Compuware]]
* PREEvision from Vector Informatik
* PREEvision from Vector Informatik
* Rhapsody from [[Company:IBM|IBM]]
* Rhapsody from [[Company:IBM|IBM]]
* [[Software:RISE Editor|RISE Editor]] from RISE to Bloome Software
* [[Software:PowerDesigner|PowerDesigner]] from [[Company:SAP SE|SAP]]
* PowerDesigner from [[Company:SAP SE|SAP]]
* [[Software:Simulink|Simulink]] from [[Company:MathWorks|MathWorks]]
* [[Software:Simulink|Simulink]] from [[Company:MathWorks|MathWorks]]
* [[Software:Software Ideas Modeler|Software Ideas Modeler]] from Dusan Rodina
* [[Software:Software Ideas Modeler|Software Ideas Modeler]] from Dusan Rodina
* Sirius an Eclipse Open Source project to create custom graphical modeling workbenches
* Sirius an Eclipse open source project to create custom graphical modeling workbenches
* [[Software:Borland Together|Together Architect]] from [[Company:Borland|Borland]]
* [[Software:Borland Together|Together Architect]] from [[Company:Borland|Borland]]
* Umbrello by KDE
* Umbrello by KDE
* [[Umple]] from the University of Ottawa
* [[Umple]] from the University of Ottawa
* [[Uniface (programming language)|Uniface]] from Compuware
* [[Uniface (programming language)|Uniface]] from Compuware
* [[Software:YAKINDU Statechart Tools|YAKINDU Statechart Tools]] open source tool build on top of [[Software:Eclipse|Eclipse]]
* [[Software:YAKINDU Statechart Tools|YAKINDU Statechart Tools]] open source tool build on top of [[Astronomy:Eclipse|Eclipse]]
{{div col end}}
{{div col end}}


Line 83: Line 84:
==Further reading==
==Further reading==
* [[Biography:David S. Frankel|David S. Frankel]], ''Model Driven Architecture: Applying MDA to Enterprise Computing'', John Wiley & Sons, {{ISBN|0-471-31920-1}}
* [[Biography:David S. Frankel|David S. Frankel]], ''Model Driven Architecture: Applying MDA to Enterprise Computing'', John Wiley & Sons, {{ISBN|0-471-31920-1}}
* Marco Brambilla, Jordi Cabot, Manuel Wimmer, ''Model Driven Software Engineering in Practice'', foreword by [[Biography:Richard Soley|Richard Soley]] ([[Organization:Object Management Group|OMG]] Chairman), Morgan & Claypool, USA, 2012, Synthesis Lectures on Software Engineering #1. 182 pages. {{ISBN|9781608458820}} (paperback), {{ISBN|9781608458837}} (ebook). http://www.mdse-book.com
* Marco Brambilla, Jordi Cabot, Manuel Wimmer, ''Model Driven Software Engineering in Practice'', foreword by [[Biography:Richard Soley|Richard Soley]] ([[Organization:Object Management Group|OMG]] Chairman), Morgan & Claypool, USA, 2012, Synthesis Lectures on Software Engineering #1. 182 pages. {{ISBN|9781608458820}} (paperback), {{ISBN|9781608458837}} (ebook). https://www.mdse-book.com
* {{cite journal|first=Alberto Rodrigues |last=da Silva |title=Model-Driven Engineering: A Survey Supported by a Unified Conceptual Model |journal=Computer Languages, Systems & Structures |volume=43 |pages=139–155 |number=43 |date=2015|doi=10.1016/j.cl.2015.06.001 |doi-access=free }}
* {{cite journal|first=Alberto Rodrigues |last=da Silva |title=Model-Driven Engineering: A Survey Supported by a Unified Conceptual Model |journal=Computer Languages, Systems & Structures |volume=43 |pages=139–155 |number=43 |date=2015|doi=10.1016/j.cl.2015.06.001 |doi-access=free }}


==External links==
==External links==
* [http://www.omg.org/mda/mda_files/Model-Driven_Architecture.pdf ''Model-Driven Architecture: Vision, Standards And Emerging Technologies''] at omg.org
* [https://www.omg.org/mda/mda_files/Model-Driven_Architecture.pdf ''Model-Driven Architecture: Vision, Standards And Emerging Technologies''] at omg.org
{{Software engineering}}
{{Software engineering}}


Latest revision as of 07:37, 22 May 2026

Short description: Software development methodology
Software development
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Practices
Tools
Standards and Bodies of Knowledge
Glossaries

Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem. Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing (i.e. algorithmic) concepts.

MDE is a subfield of a software design approach referred as round-trip engineering. The scope of the MDE is much wider than that of the Model-Driven Architecture.[1]

Overview

The MDE approach is meant to increase productivity by maximizing compatibility between systems (via reuse of standardized models), simplifying the process of design (via models of recurring design patterns in the application domain), and promoting communication between individuals and teams working on the system (via a standardization of the terminology and the best practices used in the application domain). For instance, in model-driven development, technical artifacts such as source code, documentation, tests, and more are generated algorithmically from a domain model.[2]

A modeling paradigm for MDE is considered effective if its models make sense from the point of view of a user that is familiar with the domain, and if they can serve as a basis for implementing systems. The models are developed through extensive communication among product managers, designers, developers and users of the application domain. As the models approach completion, they enable the development of software and systems.

Some of the better known MDE initiatives are:

  • The Object Management Group (OMG) initiative Model-Driven Architecture (MDA) which is leveraged by several of their standards such as Meta-Object Facility, XMI, CWM, CORBA, Unified Modeling Language (to be more precise, the OMG currently promotes the use of a subset of UML called fUML together with its action language, ALF, for model-driven architecture; a former approach relied on Executable UML and OCL, instead), and QVT.[3]
  • The Eclipse "eco-system" of programming and modelling tools represented in general terms by the (Eclipse Modeling Framework). This framework allows the creation of tools implementing the MDA standards of the OMG; but, it is also possible to use it to implement other modeling-related tools.

History

A chart showing the instantiations and representation links between a metamodel, a model and an original (in French).

The first tools to support MDE were the Computer-Aided Software Engineering (CASE) tools developed in the 1980s. Companies like Integrated Development Environments (IDE – StP), Higher Order Software (now Hamilton Technologies, Inc., HTI), Cadre Technologies, Bachman Information Systems, and Logic Works (BP-Win and ER-Win) were pioneers in the field.

The US government got involved in the modeling definitions creating the IDEF specifications. With several variations of the modeling definitions (see Booch, Rumbaugh, Jacobson, Gane and Sarson, Harel, Shlaer and Mellor, and others) they were eventually joined creating the Unified Modeling Language (UML). Rational Rose, a product for UML implementation, was done by Rational Corporation (Booch) responding 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.

Advantages

According to Douglas C. 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.[4]

Tools

Notable software tools for model-driven engineering include:

See also

References

  1. ↑ "8 Reasons Why Model-Driven Approaches (will) Fail" (in en). https://www.infoq.com/articles/8-reasons-why-MDE-fails/. 
  2. ↑ Flatt, Amelie; Langner, Arne; Leps, Olof (2022) (in en). Model-Driven Development of Akoma Ntoso Application Profiles - A Conceptual Framework for Model-Based Generation of XML Subschemas (1st ed.). Heidelberg: Sprinter Nature. ISBN 978-3-031-14131-7. 
  3. ↑ Object Management Group (2006-05-24). "OMG Trademarks". https://www.omg.org/legal/tm_list.htm. 
  4. ↑ Schmidt, D.C. (February 2006). "Model-Driven Engineering". IEEE Computer 39 (2). doi:10.1109/MC.2006.58. https://www.cs.wustl.edu/~schmidt/PDF/GEI.pdf. Retrieved 2006-05-16. , "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..."

Further reading

  • David S. Frankel, Model Driven Architecture: Applying MDA to Enterprise Computing, John Wiley & Sons, ISBN 0-471-31920-1
  • Marco Brambilla, Jordi Cabot, Manuel Wimmer, Model Driven Software Engineering in Practice, foreword by Richard Soley (OMG Chairman), Morgan & Claypool, USA, 2012, Synthesis Lectures on Software Engineering #1. 182 pages. ISBN 9781608458820 (paperback), ISBN 9781608458837 (ebook). https://www.mdse-book.com
  • da Silva, Alberto Rodrigues (2015). "Model-Driven Engineering: A Survey Supported by a Unified Conceptual Model". Computer Languages, Systems & Structures 43 (43): 139–155. doi:10.1016/j.cl.2015.06.001. 



Retrieved from "https://handwiki.org/wiki/index.php?title=Model-driven_engineering&oldid=4346167"