Poutakidis, D., Padgham, L. & Winikoff, M. (2002). Debugging multi-agent systems using design artifacts. In Proceedings of AAMAS-02.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....developed during design map to JACK constructs but does not provide a detailed process, heuristics, examples, or a discussion of the issues. Only MaSE and Prometheus mention testing debugging. It is unclear to what extent MaSE supports it, while Prometheus support is part of a research project [20] not yet integrated into tools for use by developers. Only MaSE discusses deployment and the level of support is unclear. Only one respondent (for MaSE) indicated any support for maintenance. Pragmatics: As we have mentioned earlier, the pragmatics of a methodology plays a very important role in ....

David Poutakidis, Lin Padgham, and Michael Winiko#. Debugging multi-agent systems using design artifacts: The case of interaction protocols. In Proceedings of the First International Joint Conference on Autonomous Agents and Multi Agent Systems (AAMAS'02), 2002.

....in the ontology area to support this. We also assume that all agents use the same language for encoding message content, such as XML. 1.2 Related Work Although transmitting protocols have been proposed in earlier research [4, 5, 6] they were primarily for closed systems. Research Refer to [8] for a detailed explanation of what Petri Nets are and how they work. Since Petri Nets are used to represent interaction protocols, we use the terms Petri Net and Protocol to mean the same thing. For our purposes, we assume that all agents in an open system can understand a generic ....

D. Poutakidis, L. Padgham, and M. Winikoff. Debugging multi-agent systems using design artifacts: The case of interaction protocols. In AAMAS'02, 2002.

....in the ontology area to support this. We also assume that all agents use the same language for encoding message content, such as XML. 1.2 Related Work Although transmitting protocols have been proposed in earlier research [4, 5, 6] they were primarily for closed systems. Research 2Refer to [8] for a detailed explanation of what Petri Nets are and how they work. Since Petri Nets are used to represent interaction protocols, we use the terms Petri Net and Protocol to mean the same thing. 3For our purposes, we assume that all agents in an open system can understand a generic ....

D. Poutakidis, L. Padgham, and M. Winikoff. Debugging multi-agent systems using design artifacts: The case of interaction protocols. In AAMAS'02, 2002.

....and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and or a fee. AAMAS 03, July 14 18, 2003, Melbourne, Australia. Copyright 2003 ACM 1 58113 683 8 03 0007 . 5.00. In an earlier paper [2] we proposed that protocol specifications, produced during the design stages of system development, could be used during debugging to monitor what message exchanges are expected and to locate bugs by detecting unexpected patterns of message exchange. We proposed a mechanism for taking protocol ....

.... diagrams being used were typical of those produced during the architectural design phase of the Prometheus design methodology for agent systems [1] The key point is that instead of presenting messages to the programmer and relying on him or her to detect problems, the debugging agent proposed in [2] monitors conversations and detects problems by identifying messages that are not permissible in the conversation defined by the protocols. 2. DEBUGGING WITH THE DEBUGGING AGENT The debugging agent takes as input a set of Petri net protocols, one for each AUML interaction protocol. The Petri net ....

[Article contains additional citation context not shown here]

D. Poutakidis and L. Padgham and M. Winikoff. Debugging Multi-Agent Systems using Design Artifacts: The case of Interaction Protocols. First International Joint Conference on Autonomous Agents and Multi-Agent Systems (AAMAS), 2002.

....Space limitations prevent us from describing in detail all aspects of the Prometheus methodology. However, we hope that some understanding of its structure, phases, artifacts and activities can be gained. We are not able to cover testing and debugging in this paper, but some of this is covered in [17]. 2.1 System specification Before starting to design or build any software system there is discussion with clients, managers or other stakeholders regarding the general purpose of the system. We do not cover the preliminary part of this discussion, but start from the point at which it is ....

....Evaluating a software engineering methodology is difficult to do well, but is important. We are also investigating how some of the design artifacts, such as the protocol definitions, and the capability diagrams, can be used for providing debugging and tracing support within the implemented system [17]. Having a design methodology which can be used through to testing and debugging is clearly advantageous in terms of an integrated and complete methodology. Acknowledgements: We would like to acknowledge the support of Agent Oriented Software Pry. Ltd. and of the Australian Research Council (ARC) ....

D. Poutakidis, L. Padgham, and M. Winikoff. Debugging multi-agent systems using design artifacts: The case of interaction protocols. In Proceedings of the First International Joint Conference on Autonomous Agents and Multi Agent Systems (AAMAS'02), 2002.

.... allows design diagrams to be drawn and generates corresponding skeleton code (in JACK) We are also investigating how some of the design artifacts, such as the protocol definitions, and the capability diagrams, can be used for providing debugging and tracing support within the implemented system [20]. Having a design methodology which can be used through to testing and debugging is clearly advantageous in terms of an integrated and complete methodology. Other areas for future work include: clearer integration of goals as a first class concept (currently goals are implicit in ....

D. Poutakidis, L. Padgham, and M. Winikoff. Debugging multi-agent systems using design artifacts: The case of interaction protocols. To appear in the proceedings of the First International Joint Conference on Autonomous Agents and Multi Agent Systems, 2002.

....a support tool for the methodology that allows design diagrams to be drawn and generates corresponding skeleton code in JACK. Future work includes clearer integration of goals, extension to social agent concepts (e.g. teams, roles) and investigating the use of design artifacts in debugging [8]. We are also in the process of writing a book on the design of intelligent agent systems. This will be a practical how to design agent systems aimed at industrial practitioners and undergraduate students. Acknowledgements: We would like to acknowledge the support of Agent Oriented Software ....

D. Poutakidis, L. Padgham, and M. Winikoff. Debugging multi-agent systems using design artifacts: The case of interaction protocols. Proceedings of Autonomous Agents and Multi Agent Systems (AAMAS), 2002.

No context found.

Poutakidis, D., Padgham, L. & Winikoff, M. (2002). Debugging multi-agent systems using design artifacts. In Proceedings of AAMAS-02.

No context found.

Poutakidis, D., Padgham, L. & Winikoff, M. (2002). Debugging multi-agent systems using design artifacts: The case of interaction protocols. In Proceedings of AAMAS-02, pp. 960-967. Bologna, Italy.

No context found.

Poutakidis, D., Padgham, L. & Winikoff, M. (2002). Debugging multi-agent systems using design artifacts. In Proceedings of AAMAS-02.

No context found.

Poutakidis, D., Padgham, L. & Winikoff, M. (2002). Debugging multi-agent systems using design artifacts. In Proceedings of AAMAS-02.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC