你在干什么MDA（模型驱动架构）的权利吗？如果是这样，什么工具你使用，以及它是如何工作的？ [英] Are you doing MDA (Model Driven Architecture) right now? If so, what tools do you use, and how is it working out?

问题描述

模型驱动架构是你创建模型其中前preSS你需要的方式，是不受任何（或至少大多数）的实现技术来解决问题的思路，然后生成执行一个或更具体的平台。索赔的是，在更高的抽象水平的工作是更强大，更高效。此外，你的模型活得比技术（所以你还是有东西时，你的第一语言/平台变得过时，您可以使用您的下一代解决方案）。另一个关键权利好处是，大部分模板和咕噜工作可以生成。一旦计算机了解你的情况的语义，它可以帮助你。

Model Driven Architecture is the idea that you create models which express the problem you need to solve in a way that is free of any (or at least most) implementation technologies, and then you generate implementation for one or more specific platforms. The claim is that working at a higher level of abstraction is far more powerful and productive. In addition, your models outlive technologies (so you still have something when your first language / platform becomes obsolete that you can use for your next generation solution). Another key claimed benefit is that much of the boilerplate and "grunt work" can be generated. Once the computer understands the semantics of your situation, it can help you more.

的有人声称这种做法是10倍以上的效率，并且它的方式，我们都将在10年内构建软件。的

Some claim this approach is 10 times more productive, and that it is the way we will all be building software in 10 years.

然而，这一切只是理论。我想知道的结果是当橡胶符合道路。此外，MDA的官方版本是从 OMG ，似乎非常沉重。这主要是基于UML的，这可能会被认为是好还是坏取决于你问的谁（我倾向于坏）。

However, this is all just theory. I am wondering what the outcomes are when the rubber meets the road. Also, the "official" version of MDA is from the OMG, and seems very heavy. It is heavily based on UML, which might be considered good or bad depending on who you ask (I'm leaning towards "bad").

不过，尽管有这些顾虑，这是很难用抽象和教的计算机的更高层次合作，以了解您的问题和解决方案的语义的思想争论。想象一下，一系列ER模型的它只是前preSS真相，然后在另一组的技术又在一组的技术设想利用这些来生成您的解决方案的一部分显著，先

But, in spite of those concerns, it is hard to argue with the idea of working at a higher level of abstraction and "teaching" the computer to understand the semantics of your problem and solution. Imagine a series of ER models which simply express truth, and then imagine using those to generate a significant portion of your solution, first in one set of technologies and then again in another set of technologies.

因此​​，我很乐意从到底是谁在做MDA现在（官方与否）的人听到。你用什么工具？它是如何工作的？如何理论的承诺多少你能捕捉到？你看到一个真实的10X效益增加？

推荐答案

我试过一次。大约大约一半通过该项目，我意识到，我的模型是无可救药地过时了从我的code和过于复杂，保持他们最新的是高昂和减慢我失望。

I tried it once. Roughly about halfway through the project I realized that my models were hopelessly out of date from my code and were so complex that keeping them up to date was prohibitive and slowing me down.

问题是，软件是充分的边缘情况。模型捕捉较大的图片都是伟大的，但一旦你开始真正code你不断寻找那些边缘案件，不久您发现该模型是过于精细的实施，你必须做出维持之间的选择模型或得到写了一些code。也许样板代是开始了，但是，收益迅速消失，我发现，我得到了生产力的大幅下降后，一个好处。该模型最终从该项目中消失了。

The problem is that Software is full of edge cases. Models are great at capturing the larger picture but once you start to actually code the implementation you keep finding all those edge cases and before too long you notice that the model is far too granular and you have to make a choice between maintaining the model or getting some code written. Maybe the boilerplate generation is a benefit for starting up but after that the benefits quickly vanish and I found that I got a drastic drop in productivity. The models eventually disappeared from that project.

这篇关于你在干什么MDA（模型驱动架构）的权利吗？如果是这样，什么工具你使用，以及它是如何工作的？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！