Abstract
While today's agent oriented software engineering facilitates the development of complex, distributed systems, fundamental problems remain. One of the problems is that the developer sees only part of the system, or one side of the business, but not the whole context. The Business Process Modeling Notation BPMN is considered a remedy here, but while suitable for modelling some aspects of agenthood, there are others for which BPMN does not go very well. While well-suited for modelling behaviours and especially interactions at a high level of abstraction, BPMN is too cumbersome for modelling every detail of a process and too rigid for modelling dynamic behaviours. Therefore, BPMN has to be embedded into the agent engineering process such that its strengths can be exploited while avoiding its weaknesses. In this paper, BPMN is used mainly for modelling the agents' high-level behaviour and communication, leaving other aspects to established agent programming techniques. The approach is applied for the JIAC multi-agent framework, for which a respective mapping of concepts is given. Finally, the prospects of such an approach are discussed, especially regarding the usage of BPMN for modelling dynamic aspects in agent systems.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
