In what case do you like reading so much? What about the type of the agent communication book? The needs to read? Well, everybody has their own reason why should read some books. Mostly, it will relate to their necessity to get knowledge from the book and want to read just to get entertainment. Novels, story book, and other entertaining books become so popular this day. Besides, the scientific books will also be the best reason to choose, especially for the students, teachers, doctors, businessman, and other professions who are fond of reading.
Design patterns document a field’s systematic knowledge derived from experiences. Despite the vast body of work in the field of multi-agent systems (MAS), design patterns for MAS are not popular among software practitioners. As MAS have features that are widely considered as key to engineering complex distributed applications, it is important to provide a clear overview of existing patterns to make this knowledge accessible. To that end, we performed a systematic literature review (SLR) covering the main publication venues of the field since 1998, resulting in 206 patterns. The study shows that (1) there is a lack of a standard template for documenting design patterns for MAS, which hampers the use of patterns by practitioners, (2) associations between patterns are poorly described, which results in a lack of overview of the pattern space, (3) patterns for MAS have been used for a variety of application domains, which underpins their high potential for practitioners, and (4) classifications of design patterns for MAS are bounded to specific pattern catalogs, a more holistic view on the pattern space is missing. From our study, we outline a number of guidelines that are important for future work on design patterns for MAS and their adoption in practice.
This paper introduces advances made in the INGENIAS methodology to deal with Ambient Intelligence (AmI). The work considers the particular features of AmI systems and how an agent-oriented methodology can help to address their development. Being INGENIAS a model-driven methodology, a first step has been to compare the concepts used in INGENIAS and those required by AmI developments. This analysis identifies required changes to be applied in the INGENIAS metamodel. A case study on a tracking system to locate people illustrates this discussion.
In this paper we propose a methodological approach to model driven design of multiagent systems (MAS). However, several methodologies for MAS have already been proposed and we do not want to present yet another new methodology. Our aim is rather to explain how our MAS development framework Bochica, which we already presented in [1], relates to such methodologies and how the proposals from literature can be integrated to extend the Bochica framework. As a result, we propose an iterative process for MAS design where several stakeholders work cooperatively in a food chain for the design of MAS and each stakeholder gets the tool support that he or she needs.
Multiagent simulation emerges to be one of the “killer applications” of multiagent system technology. For several reasons, there is a serious lack of engineering approaches in developing simulation models, so connecting AOSE with Multiagent Simulation seems to end in a win-win situation. A basic prerequisite is hereby to understand the current state and challenges of developing multiagent simulations. This is the objective of this contribution.
We propose an approach for implementing secure mobile agent systems. In the first step, we define a meta-model which extends the UML deployment diagram by concepts related to the security and mobility of multi-agent systems. We propose also a UML profile as an implementation of this meta-model. All defined concepts are based on formal specifications. In the second step, we project the application model in AGLETS-specific model, which describes the structure and the main functionalities of the application using the AGLETS concepts. In the third step, we generate Java skeleton code from the obtained model, and we generate also AspectJ code for enforcing security properties defined in the application model. The generated aspects will be woven, in modular way, into the functional application code.
