Multi-Agent Communication in JAFMAS Alan K. Galan and Albert D. Baker Department of Electrical and Computer Engineering and Computer Science University of Cincinnati Cincinnati, Ohio 45221-0030 This paper shows the approach used in JAFMAS for specifying and analyzing the conversations in a multi-agent system. Conversations are specified using an automata model and converted into a Petri net representation. Using a Petri net analyzer, the conversations are checked for consistency and coherency. We show the conversion of the conversation model to a Petri net and outline the properties that need to be verified. Introduction The conversations of a multi-agent system dictate the behavior of the system. In order to ensure that the multi- agent system will exhibit the desired system level behavior, one must ensure that the interactions between agents is consistent with the goals of the system. This means that the conversations that an agent can engage in must be logically consistent and coherent. Therefore, it is necessary to specify the conversations in such a way that the coherency of the entire system can be proven. The Java-based Agent Framework for Multi-Agent Systems (JAFMAS) uses an approach as part of it’s multi-agent system design methodology, that allows one to show that a given set of conversations in the system are consistent and coherent. The JAFMAS (Chauhan 1997) methodology uses automata models to specify conversations, which can then be converted into a Petri net representation to analyze for system consistency and coherency. In current work at the University of Cincinnati, the JAFMAS Development Environment (JAFMAS/DE) (Galan) automates the JAFMAS methodology using a graphical interface and an external Petri net analyzer. (Brink 1996) This paper provides an overview of conversation analysis in JAFMAS/DE. Specifying Conversations S1 S2 S3 S4 Received: Reject from Q2 Transmit: Propose to Q2 Received: Accept from Q2 Received: Reject from Q2 Transmit: Propose to Q2 CR1 CR3 CR2 CR4 S5 S6 S7 Recv’d: Propose from Q1 Trans: Propose to Q3 Received: Propose from Q1 Transmit: Reject to Q1 Received: Reject from Q3 Transmit: Propose to Q3 Received: Accept from Q3 Transmit: Accept to Q1 Received: Reject from Q3 Transmit: Reject to Q1 CR5 CR6 CR7 CR8 CR9 S8 S9 Received: Propose from Q2 Transmit: Accept to Q2 Received: Propose from Q2 Transmit: Reject to Q2 CR10 CR11 Queen 1 Queen 2 Queen 3 Figure 1 - 3-queens conversations