(Created page with 'This activity aims at identifying constraints between roles. This for instance includes roles that have to be played simultaneously, priorities in their executions, mutual exclus…')
Line 16: Line 16:
also defines which information is eventually required by other organisations and it
also defines which information is eventually required by other organisations and it
thus allows the identification of couples of roles that have to be played simultaneously.
thus allows the identification of couples of roles that have to be played simultaneously.
 +
 +
 +
 +
== Goal ==
 +
 +
 +
This activity aims at identifying constraints between roles. The ojbective
 +
consists in characterizing roles that have to be played simultaneously, priorities or mutual exclusion between role, preconditions for one role generated by another
 +
one, etc. Concurrency constraints are also important because they will drive the
 +
definition of role scheduling policies. So constraints between roles that prevent
 +
their concurrent execution and force a precise execution sequence have also to be
 +
precised. Roles can be played simultaneously if and only if they allow an exchange
 +
of information between two different organizations. A means for realizing this exchange
 +
can be using the agent internal context when both the roles belong to the
 +
same agent. This constitutes an alternative to the use of services and a simplification
 +
of information transfer.
 +
 +
 +
== Input ==
 +
 +
 +
Constraints between roles are identfied thanks to roles dependencies and associated
 +
knowledge described in the preivous acitivty. Role behavior description
 +
also precise which informations are eventually required from other orgnaizations
 +
and thus allow the identification of couplue of roles that have to be played simultaneously.
 +
 +
 +
== Output ==
 +
 +
Class Diagram, text document reporting constraints between roles.
 +
 +
 +
== MAS Meta-Model Elements ==
 +
 +
 +
Relate(AgentRole, AgentRole)

Revision as of 15:49, 29 July 2010

This activity aims at identifying constraints between roles. This for instance includes roles that have to be played simultaneously, priorities in their executions, mutual exclusions, preconditions for one role generated by another, and so on. Concurrency constraints are also important because they will guide the definition of role scheduling policies. Detailed constraints between roles must prevent their inopportune concurrent execution and force the correct execution sequence. Roles shall be played simultaneously if and only if they allow an exchange of information between two different organisations. A mean to realise this exchange can be the agent internal context when both roles belong to the same agent. This constitutes an alternative to the use of services and a simplification of information transfer.


Constraints between roles are identified thanks to roles dependencies and associated knowledge described in the previous activity. Role behaviour description also defines which information is eventually required by other organisations and it thus allows the identification of couples of roles that have to be played simultaneously.


Contents

Goal

This activity aims at identifying constraints between roles. The ojbective consists in characterizing roles that have to be played simultaneously, priorities or mutual exclusion between role, preconditions for one role generated by another one, etc. Concurrency constraints are also important because they will drive the definition of role scheduling policies. So constraints between roles that prevent their concurrent execution and force a precise execution sequence have also to be precised. Roles can be played simultaneously if and only if they allow an exchange of information between two different organizations. A means for realizing this exchange can be using the agent internal context when both the roles belong to the same agent. This constitutes an alternative to the use of services and a simplification of information transfer.


Input

Constraints between roles are identfied thanks to roles dependencies and associated knowledge described in the preivous acitivty. Role behavior description also precise which informations are eventually required from other orgnaizations and thus allow the identification of couplue of roles that have to be played simultaneously.


Output

Class Diagram, text document reporting constraints between roles.


MAS Meta-Model Elements

Relate(AgentRole, AgentRole)

Copyright 2010-2019 © IRTES Institute - UPR EA 7274 - Université de Technologie de Belfort-Montbéliard - Privacy policy