| M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997. |
....composed of a number of autonomous agents which are able to communicate and collaborate with each other to achieve common goals. The skill of negotiating with other agents to bid for jobs is one of the characteristics of autonomous agents. Each autonomous agent should have the following properties [6,7,8]: Autonomy: agent encapsulates some state of its environment and makes decisions about what to do based on this state; Reactivity: agent perceives its environment and respond to changes that occur in the environment; Pro activeness: agent takes the initiatives to exhibit goal directed ....
Wooldridge, W.: Agent-Based Software Engineering. IEE Proceedings on Software Engineering 44(1) (1997) 26-37
....advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and or a fee. SAC 2002, Madrid, Spain Copyright 2002 ACM 1 58113 445 2 02 03 . 5.00. MASs [32]. Di#erent approaches to coordination impact di#erently on the engineering of MASs and it would be important to have a conceptual framework (or a meta model) to classify and to compare these approaches. The literature proposes some frameworks for the comparison of these approaches, however we ....
M. J. Wooldridge. Agent-based software engineering. IEE Proceedings Software Engineering, 144(1):26--37, 1997.
....which can be directly executed. Our approach is based upon the use of multi context systems and we illustrate its use through examples of the specification of a simple agents. 1 Introduction Agent based computing is fast emerging as a new paradigm for engineering complex, distributed systems [18, 36]. An important aspect of this trend is the use of agent architectures as a means of delivering agent based functionality (as opposed to work on agent programming languages [19, 31, 34] In this context, an architecture can be viewed as a separation of concerns it identifies the main functions ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144:26--37, 1997.
....The ever increasing importance of the Web in everyday life is driving the need of software capable of coping with open and dynamic environments. More than other technologies, software agents seem to have the necessary characteristics to support the development of open and flexible software systems [22,32,44]. This is the reason why the research on agents and multi agent systems has come to a new life in the recent years, leaving artificial intelligence laboratories to reach the realm of real world software development. The creation of FIPA, the decision of OMG to raise the status of the Agent ....
....Finally, section five presents some conclusions. 2. Software Agents We introduce our informal characterisation of software agents emphasising the features that we will exploit in the definition of the artefacts described in the following sections. The definition presented here is adapted from [44]: an agent is a software system that is (i) situated in some environment, ii) capable of autonomous actions in order to meet its objectives and (iii) capable of communicating with other agents. This definition raises several points that should be discussed to show that agents can be naturally ....
[Article contains additional citation context not shown here]
M. Wooldridge, Agent-based software engineering, IEE Proceedings on Software Engineering, 144(1), 1997, 26-37.
....SODA allow the agent environment to be explicitly modelled and mapped onto suitably defined agent infrastructures. 1 Introduction The engineering of complex applications in the Internet era raises new problems which require new models, languages and methodologies. Agent based approaches [21] exploit the agent abstraction to address issues like distribution, heterogeneity, decentralisation of control, unpredictability, and need for intelligence [22] Agents situatedness and their reactivity help to deal with dynamic and unpredictable environments; their pro activeness in pursuing ....
....software engineering, by exploiting coordination models and technologies [15] In particular, SODA allow the agent environment to be explicitly modelled and mapped onto suitably defined agent infrastructures. 2 Society and environment in agent systems Till now, agent oriented engineering [21] has been mainly concerned with intra agent aspects, that is, the analysis, design and development of individual agents. This is basically a computational issue [20] which involves the way in which each agent works when seen as an individual (software) system. As suggested by many recent ....
Michael J. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997.
....is introduced, and a case study is given to show how to analyze and design an electronic library. Keywords: Methodology, Software Agents, Components TUCS Research Group Programming Methodology Research Group 1 Introduction Agent based computing is emerging as a powerful new paradigm[7, 10], and will be the backbones for the next generation of mainstream software systems. However, it is essential to have complexity management and design methodology to support the development of large embedded systems. Lack of them is the main reason why many actual projects trying to apply agent ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26-37, February 1997.
....directly executed. Our approach is based upon the use of multi context systems and we illustrate its use with an example architecture capable of argumentation based negotiation. 1 Introduction Agent based computing is fast emerging as a new paradigm for engineering complex, distributed systems [13, 27]. An important aspect of this trend is the use of agent architectures as a means of delivering agent based functionality (cf. work on agent programming languages [14, 23, 25] In this context, an architecture can be viewed as a separation of concerns it identifies the main functions that ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144:26--37, 1997.
....organized as follows. First, in this section we provide a short introduction to MAS from a software architecture viewpoint (section 1. 1) a brief introduction to software architecture 1 Software engineering issues such as specification and verification of MAS were lately discussed by Wooldridge [35]. section 1.2) and some terminology that we use to refer to MAS (section 1.3) Then, in section 2, we present properties of multi agent systems relevant to software architecture and design. We also assess the advantages and disadvantages of different styles of MAS. We proceed in section 3, ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, 1997.
No context found.
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997.
No context found.
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26-- 37, February 1997.
No context found.
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997.
....computer system that is situated in some envi1 Figure 1.1: The society level of multi agent systems. A MAS consists of agents, coordination mechanisms and a context. ronment, and that is capable of flexible autonomous action in that environment in order to meet its design objectives. Wooldridge [95]) Agents are. components that communicate with their peers by exchanging messages in an expressive agent communication language. Genesereth and Ketchpel [35] An agent will set out to do something, and do it; therefore it has the competences for intending to act, for action in an ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144:26--37, 1997.
....we discuss an implementation which makes this direct execution possible. Keywords: Agent based computing, multi context systems, software engineering, executable specifications. 1 Introduction Agent based computing is fast emerging as a new paradigm for engineering complex, distributed systems [16, 34]. An important aspect of this trend is the use of agent architectures as a means of delivering agent based functionality (cf. work on agent programming languages [20, 29, 32] In this context, an architecture can be viewed as a separation of concerns it identifies the main functions that ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144, 26--37, 1997.
....Section discusses how implemented systems may be verified, to determine whether or not they satisfy their specifications. Finally, in section , we conclude with some comments on future issues for agent oriented software engineering. Note that sections through to include some material from [55], where a fuller examination of, in particular, the specification, implementation, and verification of agent based systems may be found. 2. Agent Based Systems By an agent based system, we mean one in which the key abstraction used is that of an agent. By an agent, we mean an abstraction that ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997.
....Keywords: Organisational abstractions; multi agent systems; agent oriented software engineering; computational organisations 1. Introduction Autonomous agents and multi agent systems (MASs) are rapidly emerging as a powerful paradigm for designing and developing complex software systems [17, 36]. Therefore, as is the case with any new software engineering paradigm, the successful 1 2 Organisational Rules and widespread deployment of MASs requires not only new models and technologies, but also new methodologies to support developers engineer such systems in a robust, reliable, and ....
M.J. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26-37, February 1997.
....an object is basically a reactive entity living in a closed world, where control is fully determined at the design level. Moreover, it offers no conceptual support, no natural place for embedding intelligent behaviour. Instead, most of these issues are properly addressed by the notion of agent [10], which may be fruitfully thought as a methodological abstraction, rather than a totally new and revolutionary concept. Despite the many different definitions of agenthood, there is a quite common agreement on the fact that an agent is characterised by autonomy, social ability, reactivity, and ....
Michael J. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997.
....the BDI component of the logic. Because, as we noted earlier, there is no clear relationship between the BDI logic and the concrete computational models used to implement agents, it is not clear how such a model could be derived. 3. 4 Discussion This section is an updated and modified version of [73], which examined the possibility of using logic to engineer agent based systems. Since this article was published, several other authors have proposed the use of agents in software engineering (see, e.g. 39] Structured but informal refinement techniques are the mainstay of real world software ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997.
....execution possible. This is a revised and expanded version of a paper which appeared at the 6th International Workshop on Agent Theories, Architectures and Languages [25] 1 1 Introduction Agent based computing is fast emerging as a new paradigm for engineering complex, distributed systems [16, 34]. An important aspect of this trend is the use of agent architectures as a means of delivering agent based functionality (cf. work on agent programming languages [20, 29, 32] In this context, an architecture can be viewed as a separation of concerns it identi es the main functions that ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144:26-37, 1997.
....agents which can be directly executed. Our approach is based upon the use of multi context systems and we illustrate its use through the specification of a simple agent. 1 Introduction Agent based computing is fast emerging as a new paradigm for engineering complex, distributed systems [15, 28]. An important aspect of this trend is the use of agent architectures as a means of delivering agent based functionality (cf. work on agent programming languages [16, 24, 26] In this context, an architecture can be viewed as a separation of concerns it identifies the main functions that ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144:26--37, 1997.
....development techniques (for example, object oriented analysis and design [2, 6] are unsuitable for this task. There is a fundamental mismatch between the concepts used by object oriented developers (and indeed, by other mainstream software engineering paradigms) and the agent oriented view [32, 34]. In particular, extant approaches fail to adequately capture an agent s flexible, autonomous problem solving behaviour, the richness of an agent s interactions, and the complexity of an agent system s organisational structures. For these reasons, this article introduces a methodology called Gaia, ....
....which are in turn essentially regular expressions. Our liveness expressions have an additional operator, w , for infinite repetition (see Table 2 for more details) They thus resemble w regular expressions, which are known to be suitable for representing the properties of infinite computations [32]. Liveness expressions define the potential execution trajectories through the various activities and interactions (i.e. over the protocols) associated with the role. The general form of a liveness expression is: ROLENAME = expression where ROLENAME is the name of the role whose liveness ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26-- 37, February 1997.
....succeed in a given task environment is helpful, but it would be more helpful if, knowing this, we also had such an agent to hand. How do we obtain such an agent The obvious answer is to manually implement the agent from the specification. However, there are at least two other possibilities (see [19] for a discussion) 1. we can try to develop an algorithm that will automatically synthesise such agents for us from task environment specifications; or 2. we can try to develop an algorithm that will directly execute agent specifications in order to produce the appropriate behaviour. In this ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, Feb. 1997.
....is not computationally grounded, then this must throw doubt on the claim that this logic can be useful for reasoning about computational agent systems. If we really intend our theories to be theories of computational systems, then computational grounding is an issue that must be addressed. In [25], I point out that computational grounding is essential if we are to treat agent theories as specifications for systems. J J J J J J L [ b) L mod(L) C [ a) C = mod(L) L [ L Figure 1. Computationally ungrounded (a) and computationally ....
M. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, February 1997.
No context found.
M. Wooldridge. Agent-based software engineering. IEE Proceedings Software Engineering, 144(1):26-- 37, 1997.
No context found.
M. J. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, 1997.
No context found.
M. J. Wooldridge. Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37, 1997.
First 50 documents
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC