The role of requirements engineering in the development of multi-agent systems

There has been an increasing number of literature dealing with the software engineering aspect of building “agent oriented software”. In principle, agent oriented software is software implemented in platforms in which software pieces behave with a certain level of independence from other software pieces. An important characteristic of agent oriented software is the level of intelligence available for each software piece, or agent. (Párrafo extraído del texto a modo de resumen)Facultad de Informátic

Designing and specifying mobility within the multiagent systems engineering methodology

Recently, researchers have created many platforms and applications for mobile agents; however, current Agent-Oriented Software Engineering (AOSE) methodologies have yet not fully integrated the unique properties of these mobile agents. This paper attempts to bridge the gap between current AOSE methodologies and mobile agent systems by incorporating mobility into the established Multiagent Systems Engineering (MaSE) methodology. We accomplished this by adding a move command to the MaSE analysis models and then defined the required transformations to incorporate the required functionality into the design. Finally, we translated the design models into Java-based agents that operate within a mobile agent environment. 1

Object-oriented Tools for Distributed Computing

Distributed computing systems are proliferating, owing to the availability of powerful, affordable microcomputers and inexpensive communication networks. A critical problem in developing such systems is getting application programs to interact with one another across a computer network. Remote interprogram connectivity is particularly challenging across heterogeneous environments, where applications run on different kinds of computers and operating systems. NetWorks! (trademark) is an innovative software product that provides an object-oriented messaging solution to these problems. This paper describes the design and functionality of NetWorks! and illustrates how it is being used to build complex distributed applications for NASA and in the commercial sector

A new model for solution of complex distributed constrained problems

In this paper we describe an original computational model for solving different types of Distributed Constraint Satisfaction Problems (DCSP). The proposed model is called Controller-Agents for Constraints Solving (CACS). This model is intended to be used which is an emerged field from the integration between two paradigms of different nature: Multi-Agent Systems (MAS) and the Constraint Satisfaction Problem paradigm (CSP) where all constraints are treated in central manner as a black-box. This model allows grouping constraints to form a subset that will be treated together as a local problem inside the controller. Using this model allows also handling non-binary constraints easily and directly so that no translating of constraints into binary ones is needed. This paper presents the implementation outlines of a prototype of DCSP solver, its usage methodology and overview of the CACS application for timetabling problems

An Abstract Formal Basis for Digital Crowds

Crowdsourcing, together with its related approaches, has become very popular in recent years. All crowdsourcing processes involve the participation of a digital crowd, a large number of people that access a single Internet platform or shared service. In this paper we explore the possibility of applying formal methods, typically used for the verification of software and hardware systems, in analysing the behaviour of a digital crowd. More precisely, we provide a formal description language for specifying digital crowds. We represent digital crowds in which the agents do not directly communicate with each other. We further show how this specification can provide the basis for sophisticated formal methods, in particular formal verification.Comment: 32 pages, 4 figure

Pitfalls of Agent-Oriented Development

While the theoretical and experimental foundations of agent-based systems are becoming increasingly well understood, comparatively little effort has been devoted to understanding the pragmatics of (multi-) agent systems development - the everyday reality of carrying out an agent-based development project. As a result, agent system developers are needlessly repeating the same mistakes, with the result that, at best, resources are wasted - at worst, projects fail. This paper identifies the main pitfalls that await the agent system developer, and where possible, makes tentative recommendations for how these pitfalls can be avoided or rectified