Communications of the ACM
Coordination languages and their significance
Communications of the ACM
Temporal logic (vol. 1): mathematical foundations and computational aspects
Temporal logic (vol. 1): mathematical foundations and computational aspects
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Representation and Management of Memory and Decision in Evolving Software Systems
EUROCAST '97 Proceedings of the A Selection of Papers from the 6th International Workshop on Computer Aided Systems Theory
HEDES: A System Theory Based Tool to Support Evolutionary Software Systems
EUROCAST '99 Proceedings on Computer Aided Systems Theory
Is it an Agent, or Just a Program?: A Taxonomy for Autonomous Agents
ECAI '96 Proceedings of the Workshop on Intelligent Agents III, Agent Theories, Architectures, and Languages
A Coordination Model to Specify Systems Including Mobile Agents
IWSSD '98 Proceedings of the 9th international workshop on Software specification and design
An antibody network inspired evolutionary framework for distributed object computing
Information Sciences: an International Journal
A study upon the architectures of multi-agent systems for petroleum supply chain
CDVE'07 Proceedings of the 4th international conference on Cooperative design, visualization, and engineering
Hi-index | 0.00 |
This paper presents an architectural model to construct cooperative and evolutionary agent-based software systems. Here, a software system is defined as one consisting of a set of agents which interact by executing actions and by determining system functionality. Because the agents need intercommunication and coordination, we propose a model that allows this communication between agents and preserves system activity. This coordination model uses a blackboard as the means of communication between the system agents. The system architecture presented is dynamic in the sense that the modelled system can evolve and be adapted to its new functions. To do this, we distinguish two levels in the architecture: the system and the metasystem levels. The system level describes the system's structure and its functionality, while the meta-system level allows us to effect changes in the system in such a way as to preserve the system's integrity and restrictions. Modifications at the system level are carried out when the developer interacts at the meta-system level. System users interact only at the system level.