首页> 外文OA文献 >Enabling Multi-Stakeholder Cooperative Modelling in Automotive Software Development and Implications for Model Driven Software Development
【2h】

Enabling Multi-Stakeholder Cooperative Modelling in Automotive Software Development and Implications for Model Driven Software Development

机译:在汽车软件开发中启用多方利益相关者协作建模以及对模型驱动的软件开发的启示

代理获取
本网站仅为用户提供外文OA文献查询和代理获取服务,本网站没有原文。下单后我们将采用程序或人工为您竭诚获取高质量的原文,但由于OA文献来源多样且变更频繁,仍可能出现获取不到、文献不完整或与标题不符等情况,如果获取不到我们将提供退款服务。请知悉。

摘要

One of the motivations for a model driven approach to software development is to increase the involvement for a range of stakeholders in the requirements phases. This inevitably leads to a greater diversity of roles being involved in the production of models, and one of the issues with such diversity is that of providing models which are both accessible and appropriate for the phenomena being modelled. Indeed, such accessibility issues are a clear focus of this workshop.udHowever, a related issue when producing models across multiple parties,often at dierent sites, or even dierent organisations is the management of such model artefacts. In particular, different parties may wishudto experiment with model choices. For example, this idea of prototypingprocesses by experimenting with variants of models is one which has been used for many years by business process modellers, in order to highlightudthe impact of change, and thus improve alignment of process and supporting software specications. The problem often occurs when such variants needed to be merged, for example, to be used within a shared repository.udThis papers reports upon experiences and ndings of this merging problem as evaluated at Bosch Automotive. At Bosch we have dierent sites where modellers will make changes to shared models, and these models will subsequently require merging into a common repository. Currently,udthis work has concentrated on one type of diagram, the class diagram. However, it seems clear that the issue of how best to merge models where collaborative multi-party working takes places is one which has a significantudpotential impact upon the entire model driven process, and, given the diversity of stakeholders, could be particularly problematic for the requirements phase. In fact, class diagrams can also be used for informationudor data models created in the system analysis step. Hence, we believe that the lessons learned from this work will be valuable in tackling the realities of a commercially viable model driven process.
机译:采用模型驱动的软件开发方法的动机之一是增加需求阶段中众多利益相关者的参与。这不可避免地导致在模型的产生中涉及的角色更多的多样性,并且这种多样性的问题之一是提供对于模型化的现象而言既可访问又适合的模型。确实,此类可访问性问题是本研讨会的明确重点。 ud然而,在多方(通常是在不同地点或什至在不同组织)之间生成模型时,相关的问题是此类模型工件的管理。特别是,不同的各方可能希望 ud来尝试模型选择。例如,这种通过对模型的变体进行试验来进行原型处理的想法是业务流程建模者已经使用了很多年的想法,以便强调/理解变更的影响,从而改善流程的一致性并支持软件规范。当需要合并这样的变体时,例如在共享存储库中使用这些变体时,常常会发生此问题。 ud本文报告了在Bosch Automotive评估的该合并问题的经验和发现。在博世,我们有许多站点,建模者可以在其中更改共享模型,这些模型随后需要合并到一个公共存储库中。目前, ud这项工作集中于一种类型的图,即类图。但是,很显然,如何最好地合并协作多方工作所在的模型这一问题对整个模型驱动过程具有重大的或潜在的影响,并且鉴于利益相关者的多样性,这可能尤其成问题在需求阶段。实际上,类图也可以用于在系统分析步骤中创建的信息数字数据模型。因此,我们认为,从这项工作中学到的经验教训对于解决商业上可行的模型驱动过程的现实将是有价值的。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号