Software Architectures and Multiagent Systems

Arcangeli, Jean‐Paul; Noël, Victor; Migeon, Frédéric

doi:10.1002/9781118945087.ch5

Cited by 5 publications

(7 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In order to face these challenges, we currently develop a solution based on multi-agent systems (MAS) which offer several advantages from an architectural point of view (Arcangeli et al, 2014), and precisely on cooperative MAS (Georgé et al, 2011), which support the emergence of functions through local interactions between cooperative agents. In order to select relevant compositions, agents have learning capabilities and are able to consider user's feedback.…”

Section: Discussionmentioning

confidence: 99%

Opportunistic Software Composition: Benefits and Requirements

Triboulot

Trouilhet

Arcangeli

et al. 2015

Proceedings of the 10th International Conference on Software Engineering and Applications

Self Cite

View full text Add to dashboard Cite

OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. This is an author-deposited version published in : http://oatao.univ-toulouse.fr/ Eprints ID : 15305The contribution was presented at :http://www.icsoft.org/?y=2015 Abstract: Traditional software development relies on building and assembling pieces of software in order to satisfy explicit requirements. Component-based software engineering simplifies composition and reuse, but software adaptation to the environment remains a challenge. Opportunistic composition is a new approach for building and re-building software in open and dynamic contexts. It is based on the ability to compose software components in a bottom-up manner, merely because they are available at a point and not because the construction of a specific software has been demanded. In this way, software emerges from the environment. This paper analyzes the advantages of such an approach in terms of flexibility and reuse, along with the requirements that an infrastructure supporting opportunistic composition should satisfy: it should be decentralized, autonomic, and dynamically adaptive. The state of the art of automatic software composition shows that few solutions are actually bottom-up, and that none of them fully satisfies the requirements of opportunistic composition.

show abstract

Section: Discussionmentioning

confidence: 99%

Opportunistic Software Composition: Benefits and Requirements

Triboulot

Trouilhet

Arcangeli

et al. 2015

Proceedings of the 10th International Conference on Software Engineering and Applications

Self Cite

View full text Add to dashboard Cite

show abstract

“…This can be explained by the fact that the existing methodological guidelines in the literature do not directly promote such advantages, while the strategy presented here does. Some of these architectural advantages of the strategy were already identified in the context of MAS [3]: here we improve their rationalisations by linking them to the proposed strategy.…”

Section: Architectural Advantages For Developmentmentioning

confidence: 95%

“…The components are the agents, their environment connects them together and the relations between agents and with the environment are often dynamically changing at runtime [3]. Figure 1 is thus a SOMAS C&C view.…”

Section: Software Architecture Problems and Requirementsmentioning

confidence: 99%

“…From a software architecture point of view, it is known that using (SO)MAS is an architectural response to a certain problems with requirements such as complexity, distribution, dynamicity, scalability, or adaptation [3,15,47,48]. These are other ways of saying that the actual specification of what the system should do changes at runtime and can't be predefined.…”

Section: Requirements and Underspecificationmentioning

confidence: 99%

“…Figure 1 is thus a SOMAS C&C view. Another important aspect of software architectures concerns modules views (i.e., the description of units of implementation and their relations): while the design of SOMAS does not usually directly cover them [3], as we will see in Section 3.6 the choices made during their engineering still impact them.…”

Section: Software Architecture Problems and Requirementsmentioning

confidence: 99%

See 2 more Smart Citations

Methodological Guidelines for Engineering Self-organization and Emergence

Noël

Zambonelli

2015

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

The ASCENS project deals with the design and development of complex self-adaptive systems, where self-organization is one of the possible means by which to achieve self-adaptation. However, to support the development of self-organising systems, one has to extensively re-situate their engineering from a software architectures and requirements point of view. In particular, in this chapter, we highlight the importance of the decomposition in components to go from the problem to the engineered solution. This leads us to explain and rationalise the following architectural strategy: designing by following the problem organisation. We discuss architectural advantages for development and documentation, and its coherence with existing methodological approaches to self-organisation, and we illustrate the approach with an example on the area of swarm robotics

show abstract