首页> 外文会议>Information Resources Management Association International Conference vol.1; 20040523-26; New Orleans,LA(US) >Addressing Agent Autonomy in Business Process Management - With Case Studies on the Patient Discharge Process
【24h】

Addressing Agent Autonomy in Business Process Management - With Case Studies on the Patient Discharge Process

机译:解决业务流程管理中的座席自治问题-以患者出院流程为例

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

摘要

This work argues for the need to represent and reason about agent autonomy in modeling and supporting business processes. We showed how to use the i~* framework to do that, recognizing that agents are allowed to pursue their goals in their own way, but also introducing constraints in the way some goals have to be achieved when necessary. Sequence of tasks can be expressed when needed [Liu 02]. A methodology presenting systematic guidelines to use i~* for requirements elicitation has been recently proposed [Cysneiros 03]. In order to diminish the gap between BPM and agent software paradigm, we propose to use the i~* framework as a front end to BPM techniques and languages. In such a way one should first use the i~* framework to understand the business and elicit requirements for the software-to-be. Once there is an established process suitable to all stakeholders, the process modelled in i~* may be mapped to BPMN [Owen 03]. Although this is future work, we have shown in section three a preliminary approach for this mapping. We also foresee that in the future, to cope with the need for flexibility, BPM may use software agents, in which case the use of i~* as a front end will be even more natural. A version of i~* called GRL [GRL] is being proposed as part of a User Requirements Notation as a standard for the ITU Telecommunication Standardization Sector (ITU-T). Future work includes studying how well the framework scales from small to very large systems.
机译:这项工作主张在建模和支持业务流程中需要代表和推理代理自主性。我们展示了如何使用i〜*框架来做到这一点,认识到代理被允许以自己的方式追求目标,而且还引入了一些限制,即在必要时必须达到一些目标。任务序列可以在需要时表达[Liu 02]。最近提出了一种提出系统准则以使用i *进行需求启发的方法[Cysneiros 03]。为了缩小BPM和代理软件范式之间的差距,我们建议使用i〜*框架作为BPM技术和语言的前端。以这种方式,应该首先使用i〜*框架来了解业务并得出将要开发的软件的要求。一旦建立了适合所有涉众的流程,就可以将i *中建模的流程映射到BPMN [Owen 03]。尽管这是将来的工作,但我们在第三部分中显示了此映射的初步方法。我们还预见到,为了应对灵活性的需求,BPM可能会使用软件代理,在这种情况下,使用i〜*作为前端将更加自然。作为用户需求表示法的一部分,提出了一种称为GRL [GRL]的i〜*版本,作为ITU电信标准化部门(ITU-T)的标准。未来的工作包括研究框架从小型系统扩展到大型系统的能力。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号