您是否使用MDA/MDD/MDSD，任何一种模型驱动的方法?会是未来吗? [英] Do you use MDA/MDD/MDSD, any kind of model-driven approach? Will it be the future?

问题描述

编程语言在其历史上经历了几个(r)进化的步骤.有人认为，模型驱动的方法将是下一件大事".有诸如openArchitectureWare，AndroMDA，Sculptor/Fornax平台之类的工具，它们有望极大地提高生产力.但是，我的经验是，一开始就很容易，但是在尝试一些意料之外的事情时会卡在某个点上，或者很难找到足够的信息来告诉您如何开始您的项目，因为可能有很多事情要考虑.

Programming languages had several (r)evolutionary steps in their history. Some people argue that model-driven approaches will be The Next Big Thing. There are tools like openArchitectureWare, AndroMDA, Sculptor/Fornax Platform etc. that promise incredible productivity boosts. However, I made the experience that it is either rather easy in the beginning to get started but as well to get stuck at some point when you try something that was unanticipated or pretty hard to find enough information that tells you how to start your project because there may be a lot of things to consider.

我认为从模型驱动的东西中获取任何东西的重要见解是要理解模型不一定是一组漂亮的图片或树模型或UML，而是一个文本描述(例如状态机) ，业务规则等).

I think an important insight to get anything out of model-driven something is to understand that the model is not necessarily a set of nice pictures or tree model or UML, but may as well be a textual description (e.g. a state machine, business rules etc.).

您如何看待，您的经历告诉您什么?

What do you think and what does your experience tell you? Is there a future for model-driven development (or whatever you may want to call it)?

更新:该主题似乎没有引起太多兴趣.如果您对模型驱动的方法有任何(好的或坏的)经验，或者为什么认为这一点都不有趣，请告诉我.

Update: There does not seem to be a lot of interest in this topic. Please let me know, if you have any (good or bad) experience with model-driven approaches or why you think it's not interesting at all.

推荐答案

我认为，这需要时间，直到工具变得更加完善，更多的人获得了使用MDD的经验.目前，如果您想从MDD中获得收益，则必须投入大量资金，因此其使用仍然受到限制.

I think, it will take time, till the tools get more refined, more people gain experience with MDD. At the moment if you want to get something out of MDD you have to invest quite a lot, so its use remains limited.

例如，以openArchitectureWare为例:尽管它非常强大并且存在基本文档，但是缺少内部工作文档，并且仍然存在可伸缩性问题，这些都是未记录的-也许当Xtext和Xpand被重写时会变得更好.

Looking at openArchitectureWare for example: While it is quite robust and basic documentation exists, documentation on the inner workings are missing and there are still problems with scalability, that are undocumented - maybe that will get better when Xtext and Xpand get rewritten.

但是，使用oAW消除这些限制本身就很容易，您可以像在Xtend和Xpand中一样吸引人地浏览模型，并且通过将多个工作流程组合成更大的工作流程，还可以完成非常复杂的事情.如果需要，您可以求助于Java，因此在模型处理方面具有很大的灵活性.同样，在oAW中使用Xtext编写自己的DSL也很快完成，但是基本上可以免费获得元模型，解析器和非常好的编辑器.您也可以基本上从任何地方获得模型，例如可以将数据库转换为元模型的组件，而无需花费大量精力即可编写相应的模型.

But despise those limitations the generation itself is quite easy with oAW, you can navigate your models like a charm in Xtend and Xpand and by combining several workflows into bigger workflows, you can also do very complex things. If needed you can resort to Java, so you have a very big flexibility in what you can do with your models. Writing your own DSL with Xtext in oAW, too, is quickly done, yet you get your meta-model, a parser and a very nice editor basically for free. Also you can get your models basically from everywhere, e.g. a component that can convert a database into a meta-model and corresponding models can be written without big effort.

所以我想说，随着工具和经验的增加，MDD仍在建立.如果您具有必要的专业知识，并准备将其推入公司，它已经可以成功使用.最后，我认为这是一件非常好的事情，因为可以并且应该生成很多胶水代码(也称为复制粘贴).我认为，使用MDD做到这一点是一种非常好的结构化方式，可以促进可重用性.

So I would say, MDD is still building up, as tools and experience with it increases. It can already used successfully, if you have the necessary expertise and are ready to push it within your company. In the end, I think, it is a very good thing, because a lot of glue code (aka copy paste) can and should be generated. Doing that with MDD is a very nice and structured way of doing this, that facilitates reusability, in my opinion.

这篇关于您是否使用MDA/MDD/MDSD，任何一种模型驱动的方法?会是未来吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！