The main features of the agent editor follow:

• It is based on the PAML metamodel it can be used to design PRACTIONIST agents and their interactions with the system (i.e. other agents and system artefacts)
• It supplies support to unify all the defined entities of the system within an agent, that is the most important entity to be developed
• The designer can model the agent initial belief base through a simple editor
• The diagram and the underlying model can be continuously validated fulfilling the PAML metamodel (even if a project property can be set in order to disable the validation marks)
• The code generator is able to generate the agent Java class, filling the initialize method in order to automatically aggregate the other entities composing the agent itself, and its belief base
• It takes advantages from all the MO2L architecture features

This editor is a work in progress tool so the known main lacks follow:

• It is not possible to design agent relationships in details
• There are no properties to model for the artefacts, even if the developer can model three different kinds of artefacts, according to PAML metamodel.

 

Figure 1 shows the main GUI of the editor, that is a classic Eclipse GUI with a custom perspective, with the editor area with its palette (Figure 2), the Model View (Figure 3) and the other common views.