Model-driven architecture: Difference between revisions

Revision as of 17:30, 6 June 2019

Revision as of 11:47, 22 September 2019

Line 25:

The OMG organization provides rough specifications rather than implementations, often as answers to [[Request for Proposal|Requests for Proposals]] (RFPs). The OMG documents the overall process in a document called the MDA Guide.

Basically, an MDA tool is a tool used to develop, interpret, compare, align, measure, verify, transform, etc. models or metamodels.<ref>{{cite paper|author=Bézivin, J, Gérard, S, Muller, P-A, and Rioux, L|title=MDA components: Challenges and Opportunities|version=In: Metamodelling for MDA|year=2003|url=http://www.sciences.univ-nantes.fr/lina/atl/www/papers/MDAComponents-ChallengesOpportunities.V1.3.PDF|deadurlurl-status=yesdead|archiveurl=https://web.archive.org/web/20061206191031/http://www.sciences.univ-nantes.fr/lina/atl/www/papers/MDAComponents-ChallengesOpportunities.V1.3.PDF|archivedate=2006-12-06|df=}}</ref> In the following section "model" is interpreted as meaning any kind of model (e.g. a UML model) or metamodel (e.g. the CWM metamodel). In any MDA approach we have essentially two kinds of models: ''initial models'' are created manually by human agents while ''derived models'' are created automatically by programs. For example, an analyst may create a UML initial model from its observation of some loose business situation while a Java model may be automatically derived from this UML model by a [[Model transformation]] operation.

An MDA tool may be a tool used to check models for completeness, inconsistencies, or error and warning conditions. Also used to calculate metrics for the model.<ref name="MonperrusJézéquel2008">{{cite journal|last1=Monperrus|first1=Martin|last2=Jézéquel|first2=Jean-Marc|last3=Champeau|first3=Joël|last4=Hoeltzener|first4=Brigitte|title=A Model-Driven Measurement Approach|year=2008|pages=505–519|issn=0302-9743|doi=10.1007/978-3-540-87875-9_36}}</ref>