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

问题描述

模型驱动架构是这样一种理念，即您创建模型来表达您需要解决的问题，而无需任何(或至少是大多数)实现技术，然后您为一个或多个特定平台生成实现.声称在更高的抽象级别上工作会更加强大和高效.此外，您的模型比技术更长寿(因此，当您的第一种语言/平台过时时，您仍有一些东西可以用于下一代解决方案).另一个声称的关键好处是可以生成大部分样板文件和繁重的工作".一旦计算机理解了你所处情境的语义，它就能为你提供更多帮助.

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 年内构建软件的方式.

然而，这只是理论.我想知道当橡胶遇到道路时会产生什么结果.另外，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 模型，然后想象使用这些模型来生成解决方案的重要部分，首先在一组技术中，然后在另一组技术中.

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(官方"与否)的人的意见.你在使用什么工具?效果如何?你能捕捉到多少理论上的承诺?您看到真正的 10 倍效率提升了吗?

推荐答案

我试过一次.大约在项目进行到一半的时候，我意识到我的模型与我的代码相比已经过时了，而且非常复杂，以至于让它们保持最新状态令人望而却步，拖慢了我的速度.

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.

问题在于软件充满了边缘情况.模型非常擅长捕捉更大的画面，但是一旦您开始对实现进行实际编码，您就会不断发现所有这些边缘情况，不久您就会注意到模型过于精细，您必须在维护模型或获取模型之间做出选择写了一些代码.也许样板生成对启动有好处，但在那之后，好处很快就消失了，我发现我的生产力急剧下降.这些模型最终从那个项目中消失了.

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屋！