首页> 外文会议>UML Satellite Activities Conference; 20041011-15; Lisbon(PT) >Incremental MDD Through Generative Causal Connectedness
【24h】

Incremental MDD Through Generative Causal Connectedness

机译:通过生成的因果联系建立增量MDD

获取原文
获取原文并翻译 | 示例

摘要

In most MDA and MDD implementations there is a separation between the modeling environment and the run-time environment. As a result, applying changes to a run-time system can be awkward. For example adding a new type to a running system means regenerating the code of the system, recompiling and restarting the system. This leads to downtime of the system, thus blocking the normal business. Riehle et al made the observation that in order to enable such changes without having to stop the run-time system and thus to allow incremental model-driven development, a direct "causal" connectedness is needed between the modeling environment and the run-time environment, such that every change or addition can also directly, and only locally (without disturbing other models and their run-time instances), affect the run-time system. describes a causally connected implementation of a UML-based model driven system. It is based on the principle of "Adaptive Object-models" (AOMs). The idea of AOMs is that an object-oriented application can be adapted through meta-data available at run-time. However, a problem of all AOM implementations known to us is that they are based on interpretation. Both instance structure and behavior is realized interpretatively. As a result the storage structures for instances is not efficient, e.g., each property value will be stored in a separate object. Moreover, programming support such as optimization, type checking and normal debugging is lost. The approach of [6] is therefore only used to create satisfactory applications through interactive model-driven development. The final system is still generated in a "traditional" way, and can no longer be changed incrementally.
机译:在大多数MDA和MDD实现中,建模环境和运行时环境之间是有区别的。结果,将更改应用于运行时系统可能很麻烦。例如,将新类型添加到正在运行的系统意味着重新生成系统代码,重新编译并重新启动系统。这导致系统停机,从而阻碍了正常业务。 Riehle等人观察到,为了能够在不停止运行时系统的情况下进行此类更改,从而允许进行增量模型驱动的开发,在建模环境与运行时环境之间需要直接的“因果关系” ,这样每次更改或添加也可以直接且仅在本地(不打扰其他模型及其运行时实例)会影响运行时系统。描述了基于UML的模型驱动系统的因果关系实现。它基于“自适应对象模型”(AOM)的原理。 AOM的想法是,可以通过在运行时可用的元数据来适应面向对象的应用程序。但是,我们所知道的所有AOM实现的问题在于它们基于解释。实例结构和行为都是通过解释实现的。结果,实例的存储结构效率不高,例如,每个属性值将存储在单独的对象中。而且,丢失了诸如优化,类型检查和常规调试之类的编程支持。因此,[6]的方法仅用于通过交互式模型驱动的开发来创建令人满意的应用程序。最终系统仍以“传统”方式生成,无法再进行增量更改。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号