Task: Confirm the Adequacy of a MAS Approach
In this task, the system's need to be implemented as an adaptive MAS is examined. According to the AMAS theory, there are several exclusion criteria such as closed and non-complex systems or the existence of an algorithm that solves the focal problems.
Relationships
RolesPrimary: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Main Description

Early on in the project, the adequacy of using a multi-agent system to solve the problem should be determined. If the system can indeed be modeled as a closed, non-distributed system or if there are powerful algorithms that can solve the problems posed by the requirements centrally, it might not be beneficial to pursue implementation as a MAS. However, some requirements, especially with regard to adaptivity strongly favour the use of agent technology.

The verification happens both on a local and on a global level. At the global level, this means to answer to the question: is a MAS required to implement the system? On the local level, it means to understand if there are agents that can themselves by implemented as a MAS or not. The MAS Adequacy Criteria can be used for the confirmation.

Originally from ADELFE, "Adequacy Verification fragment" (Cossentino & Seidita 2005)

Steps
Identify requirements that are in favour of a MAS approach
Use the MAS Adequacy Criteria as a foundation for the decision of whether or not pursuing an agent-oriented approach is worthwhile.
Review existing literature to find examples of similar requirements being solved by a MAS

Identifying other examples of multi-agent systems that have been implemented for similar purposes can help tremendously in the decision by providing guidance and pointing out issues that have come up in the implementation. They might also provide solutions for problems the development team might encounter later on and can thus form the basis for design decisions in later stages of the process.

Identify alternative solution approaches that do not require an agent-oriented approach
Consider possible alternatives such as service-oriented architectures or component systems and identify how well suited such approaches would be to the problem at hand.
Weigh the increased complexity of a MAS solution against the expected benefits
The previous steps should provide insights into the expected benefits and the drawbacks of the use of an agent-oriented approach. These should be considered carefully and a decision based on this information and potential other solution approaches should be made.
Document the decision process and the factors involved in it in the MAS Adequacy Synthesis work product
To make the considered approaches, alternatives, and the reasons for the final decision transparent, these aspects should be documented in the according work product. If, at a later point in time, the rationale behind the use of an agent-oriented approach is called into question, this documentation can provide guidance and allow to justify the initial decision.
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable
More Information
Guidelines