Bertil Ekdahl

  • Citations Per Year
Learn More
This paper presents a novel approach to the problem of designing autonomous agents that is based on the idea of anticipatory systems. An anticipatory system has a model of itself and of the relevant part of its environment and will use this model to predict the future. The predictions are then utilised to determine the agent’s behaviour, i.e. it lets future(More)
This paper presents a new framework for autonomous agents that is based on the concept of anticipatory systems. It is a hybrid approach that synthesizes low-level reactive behavior and high-level symbolic reasoning. According to this framework, an agent, i.e. an anticipatory agent, consists of three main entities: a reactive system, a world model, and a(More)
A general agent theory requires a well-defined domain. We argue that this requirement is not met by most proposed agent theories. The reason is that they are based on assumptions about the internal structure of the agents, often described in terms of human-like “mental states” such as beliefs and intentions. In fact, there are strong indications that the(More)
Recently, several suggestions for (multi-) agent theories have been presented. In order to develop a meaningful formal theory it is necessary also to specify a model, i.e., how to interpret the theory. This, in turn, requires a well-defined domain, otherwise it is not possible to define predicates, etc. We argue that current suggested agent theories do not(More)
During the last ten years or so, much effort has been spent on developing software architecture by analogy with hardware architecture from where the idea seems to originate. Much of the work has been devoted to specifying standard program units, called components, and their connections. The architecture is then the specific organization of these components(More)
  • Bertil Ekdahl
  • 2009 Third International Conference on Digital…
  • 2009
Many people have experienced computers not doing what they were expected to do or, perhaps more often, met with computers that deliver faulty results. Frequently, if not always, such behavior is blamed the lack of a complete requirements specification. In this assertion, it is tacitly understood that if a specification is correct and comprehensive enough(More)