Holon Architecture Definition
This activity aims at defining the architecture of each holon involved in the implementation of the previously design solution.
The major input of this activity is the result of the Holarchy Design phase. Role Assignation, Abstract holon architecture, holon government definition are exploited in this activity.
The output of the activity consists in the complete static description of the elements involved in the implemented solution. A class diagram is suggested to represent these elements. A text document completes the description of the holons by dealing also with government rules.
MAS Metamodel Elements
Define(JOrganization), Define(JAbstractRole), Define(JHolon), Define(JAgent), Define(JCapacity), Define(JService), Define(JAbstractParallelRole), Define(JRoleTask), Define(JHolonicRole), Define(JLightHolon), Define(JHeavyHolon), Relate(JOrganization,JAbstractRole), Relate(JAgent, JAbstractRole)
Work to be done
Each organisation and its set of roles and associated tasks have to be described. Each holon is associated with the set of roles it should play, the set of capacities and services that it owns. Two different approaches may be used to design a holon. A static approach consists in designing a specific holon architecture for each architecture designed in the Holarchy Design activity. This approach is the most simple and easy to maintain, but it may generate a relevant number of architectures in complex applications. Another approach consists in designing a dynamic holon architecture where holons will dynamically acquire roles and the corresponding set of required capacities. In this activity the designer also defines composed holons government rules and JAtomicAgents that may be used when an holonic structure is not required.
Figure 29 depicts a part of the Holons architecture implied in the implementation of our Robot Soccer Simulator example. In this example we have opted for a static approach. For each architecture identified in the Holarchy Design activity, a specific holon is designed. Three holon architectures and three organisations are partially described in the class diagram. Only the role JPlayersSimulator is described in terms of JRoleTask. Classes already introduced in the solution domain (see figure 28) correspond to class provided by the Janus platform that are refined to define problem dependent artefacts.
|Figure 29: The Holon Architecture designed for the proposed case study |