Description of the Conference Management System Example
Let us consider an agent-based system for supporting the process of producing the technical program for an international conference. The process may be subdivided into three phases: - The submission phase: the program committee chair (PC Chair) and the organizer distribute the call for papers. The authors submit their papers. The papers are classified (according to specific criteria), a submission number is assigned to each paper and the authors are notified about that. - The review phase: the PC Chair distributes the papers among the PC Members which are in charge of providing reviews for those papers. The PC Chair collects back reviews, decides upon the acceptance/rejection of papers, and eventually notifies authors of the decision. Considering all the accepted papers, the PC Chair prepares the conference program. - The publishing phase: the authors of the accepted papers have to produce a revised version of their papers. The publisher has to collect these final versions and compose the proceedings.
The process clearly involves three loosely interacting phases, each involving different actors, and naturally leads to conceiving one MAS for supporting the activities of each phases. There, personal agents will be naturally associated to the actors involved in the process (authors, PC Chair, PC Members, reviewers) to support their work. It is also natural that the roles played by each agent reflect the ones played by the associated actor in the conference organization. This may require agents to interact both directly with each other (according to patterns that will reflect the patterns of interactions in the real-world organizations), and indirectly (via exchanges of papers and review forms).
Agent Model
The design of agents is not particularly affected by the specific organizational structure, as far as the “intrinsic” roles and interactions are concerned.
The attached file shows the Agent model related to the reviewing process for a multilevel hierarchy organization.
Such a model shows two agent classes – Chair Agent and Reviewer Agent – and their corresponding instances, which are represented using the following annotation:
-
n means that there will be exactly n agents of this class in the run-time system.:
-
m..n means that there will be no less than m and no more than n instances of this class in a run-time system (m < n).
-
∗ means that there will be zero or more instances at run-time,
-
+ means that there will be one or more instances at run-time.
source: Reference of Dealing with Adaptive Multi-agent Organizations in the Gaia Methodology.
|