2003
DOI: 10.1007/3-540-39173-8_12
|View full text |Cite
|
Sign up to set email alerts
|

ADELFE: A Methodology for Adaptive Multi-agent Systems Engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
87
0
6

Year Published

2005
2005
2018
2018

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 153 publications
(93 citation statements)
references
References 8 publications
0
87
0
6
Order By: Relevance
“…It allows to specify the first elements necessary for a minimal fault-tolerance. Moreover, it enable to identify cooperative or non-cooperative situations [2] and to define recognition states in order to analyse, for example, the selforganizational process of an application. This activity allows to take into account the safety of the users plunged in the physical system as a human agent.…”
Section: Figure 1 Lifecyle Of the Diamond Methodsmentioning
confidence: 99%
“…It allows to specify the first elements necessary for a minimal fault-tolerance. Moreover, it enable to identify cooperative or non-cooperative situations [2] and to define recognition states in order to analyse, for example, the selforganizational process of an application. This activity allows to take into account the safety of the users plunged in the physical system as a human agent.…”
Section: Figure 1 Lifecyle Of the Diamond Methodsmentioning
confidence: 99%
“…There is currently only few related work concerning emergence engineering for agent societies. The most notable work here is ADELFE [5] which is an engineering approach explicitly exploiting emergence among a set of cooperative agents. We call ADELFE an online emergence engineering approach, due to the fact that the agents are situated in the real environment and need to self-organize to respond to changes in the environment.…”
Section: Related Workmentioning
confidence: 99%
“…Multiagent method generally use notations and models from only one origin (Bernon et al, 2002) like UML ( Mase , AAII, MESSAGE, PASSI). Other methods use many notation like TROPOS (notation i* coming from the knowledge engineering, A-UML (Koning et al, 2001) for interaction protocols and plan) or DESIRE (graph-based notation for knowledge modelling and specific hierarchical notation for tasks description).…”
Section: Models and Notationsmentioning
confidence: 99%
“…DIAMOND begins by using UML use cases because they proved reliable for the definition of requirements. The interpretation of our use case diagrams is slightly different than their common use (as in (Bernon et al, 2002)) because actors are necessarily outdoor to the system or its entities. Moreover, an actor can not be in the interaction diagram (this would be amazing in a traditional use of UML use cases) in the case of physical interactions.…”
Section: Models and Notationsmentioning
confidence: 99%