Disadvantages Of Model Driven Architecture

Abstract -The purpose of this paper is to provide a general overview of Model Driven Architecture (MDA). The paper describes the advantages and disadvantages in using the MDA from a business perspective. It also provides the basic specifications and functionality of the MDA as defined by OMG and gives a brief introduction to the most commonly used modeling languages and tools that support the MDA standard.

Keywords: Model Driven Architecture, MDA, Model Driven Development, MDD, UML, XMI, CWM, MOF, Modeling, OMG.

History

OMG was established in 1989 and today has a consortium from more than 800 organizations over the world. Some of OMG's achievements are the Common Object Request Broker Architecture™ (CORBA™), Unified Modeling Language™

These days the most ordinarily utilized models are the UML models. In his book Martin Fowler clarifies three employments for the UML: UML as a Sketch, UML as a Blueprint and UML as a Programming language. The last one turned into a probability with the new UML which we well talk about later on, and likewise a decent establishment for utilizing the MDA. Today a substantial percent of the engineers utilize the UML models parallel with the product frameworks they outline. It gives a successful approach to correspondence between the originators particularly if the frameworks are mind boggling and include a number of groups in the outline.

The higher reflection level is assumed to make MDA simpler to utilize and less demanding to get it. It additionally gives to certain level of stage autonomy. Some of the other key benefits from using MDA are:

• Portability, expanding application re-utilize and diminishing the expense and intricacy of application improvement and administration, now and into what's to come.

• Cross-stage-Interoperability, utilizing thorough strategies to ensure that measures in view of numerous usage advances all actualize indistinguishable business capacities.

• Platform Independence, enormously diminishing the time, expense and multifaceted nature related with re-focusing on applications for various stages including those yet to be

However, this is not generally the situation. There is additionally a drawback in utilizing MDA. "Raising the level of reflection may prompt misrepresentation when there is insufficient subtle element for any helpful reason" Case in point it makes the issue of repetition. As indicated by the MDA standards there are numerous representations of antiques intrinsic in a product improvement process, speaking to various perspectives of or levels of deliberation on the same ideas. At the point when these are physically made, copy work and consistency administration are required. Another issue that originates from displaying is the round-trek issue. In complex frameworks a considerable measure of models and curios are required, and a few unique levels of deliberation. This additionally builds the many-sided quality of the connections between them. So when a change should be done in a relic that influences different curios and connections now and again it is difficult to mechanize the whole process. So a manual intercession is required. What's more, this is particularly troublesome if a change is done in the lower levels given the actuality the majority of the models at the lower levels are consequently