. M. Wooldridge, Agent-based software engineering, IEEE Proc. Software Engineering 144 (1) (1997) 26-37  Home/Search   Document Details and Download   Summary   Related Articles   Check

....and has its own importance in the field of intelligent agents, even if it is well known the controversy between the traditional approach and the intelligent calculus in the field of Artificial Intelligence. Moreover, the only intelligence requirement we generally make for the agents is that [2] they can make an acceptable decision about what action to perform next in their environment, in time for this decision to be useful. Other requirements for intelligence will be determined by the domain in which the agent is applied: not all agents will need to be capable of learning, for ....

....agent is applied: not all agents will need to be capable of learning, for example. In such situations, a logic architecture is very appropriate, and o#ers, in our opinion, a simple and elegant representation for the agent s environment and desired behavior. According to the traditional approach [2], the symbolic representations are logical formulae, and the syntactic manipulation corresponds to logical deduction, or theorem proving. In such a logic approach, the agent could be considered as a theorem prover(if # is a theory that explains how an intelligent agent should behave, the system ....

[Article contains additional citation context not shown here]

Wooldridge, M., "Agent-Based Software Engineering", Mitsubishi Electric Digital Library Group, London, 1997

....sofare engineering involves identifying the key concepts of agent based computing. The first such concept is that of an agent: An agent is an encapsulated computer system that is situated in some environment and can act fiexibly and autonomously in that environment to meet its design objectives [7]. Several points about this definition require elaboration. Agents are (i) clearly identifiable problem solving entities with well defined boundaries and interfaces; ii) situated (embedded) in a particular environment over which they have partial control and observability they receive inputs ....

M. Wooldridge "Agent-based software engineering," IEE Proc Software Engineering, vol. 144, pp. 26-37, 1997.

....database so scientists who did not witness the analysis can recreate the event at a later date. 3.1.1. 2 Agents An agent is an encapsulated computer system that is situated in some environment and that is capable of flexible, autonomous action in that environment in order to meet its objectives [11]. The simplest way to view agents is by considering the Belief Desire Intention (BDI) model: an agent is programmed to have beliefs , which is pre defined information the agent knows about its environment; its desires represent the pre defined ultimate goals, which give the agent its raison ....

M. Wooldridge -- "Agent-based Software Engineering" (IEE Proc on Software Engineering).

.... In particular, the distributed components, whichwe call agents, should communicate using a suitable agent communication language (ACL) which prescribes particular semantic meaning to the communication acts (or speech acts) Also certain characteristics should be promoted within the agents [25]: reactivity to changes in the external environment, proactiveness at carrying out tasks to accomplish internally generated goals and cooperation within an agent community. These multi agent concepts have been used recently to develop systems for the integration, analysis and annotation of ....

M. Wooldridge. Agent-based software engineering. ### ########### ######## ###########, 144(1):26-37, 1997.

....methods are developed so that particular systems can be reliably produced as and when they are needed. Using agents as the essential components of such a process was first suggested by Shoham [17] this follows a general trend in software engineering towards the use of increased abstraction [19]. A critical element in engineering systems is that the results must be reliable, because people want to use them as a component tool in the execution of their plans. Two of the chief ways in which such systems are made reliable is via predictability and transparency. That is, the results of ones ....

Wooldridge, M. (1997). Agent-Based Software Engineering. IEE Transactions on Software Engineering, 144:26-37.

....these new ideas. Agent oriented and Object oriented Methodologies Agents are beginning to enter the mainstream of software engineering [1] emerging from the research laboratory into commercial utilization. While intelligent agents have emerged from artificial intelligence research [2], agent oriented methodologies have a closer relationship to object technology and to object oriented methodologies. Current methodology research [3 5] is focussed on different ways to capitalize on this synergistic merger between knowledge engineering techniques [6] and object technology for ....

Wooldridge, M. (1997). Agent-based software engineering, IEE Procs Software Eng., 144, 26-37.

....cooperation of multiple heterogeneous agents) and [BF95] that presents a shell for building Multi Agent Systems that provides reusable languages and services for agent construction. A challenge for the future is building MAS using techniques rising from Software Engineering. On this way goes [Woo97] that places the bases for an Agent based Software Engineering. In that paper the construction of a MAS is seen as a software engineering enterprise: issues concerning specification, implementation and verification of MAS are presented, focusing on a number of case studies. In the same journal ....

M. Wooldridge. Agent--based software engineering. In IEE Proceedings of Software Engineering [Iee97], pages 26--37.

.... small systems such as personalized email filters to large, complex, and mission critical systems such as air traffic control [3, 14] Due to the popularity and complexity of MAS (Multi Agent Systems) they require systematic development methodology, but support of them still lacks in practice [3, 23]. For MAS development, although object oriented methodologies are seemed to be natural, they have limitations to properly represent MAS [4, 12, 15, 16, 24] These limitations include the representing collaboration among agents and mental states of an agent. Several agent oriented design methods ....

....architecture is important for the MAS, current agentoriented methodologies do not provide models and modeling elements to analysis, design, and evaluate it. This paper suggests an architecture centric object oriented design method for MAS. It is based on considering MAS as a software system [23]. It uses objectoriented methods as a core development methodology, and extends them to properly represent collaborations among agents. The extensions are based on design principles that are derived from characteristics of MAS and concepts of software architecture. They have roles that are kinds ....

Wooldridge, M., "Agent-based Software Engineering", IEE Proceedings on Software Engineering, 144(1), pp. 26 - 37, February 1997.

....would be indicative of the suitability of the agent based approach to the domain. Within the Artificial Intelligence (AI) community there is increasing agreement that the essential properties of agenthood are autonomy, situatedness, reactiveness, proactiveness, and social ability (Franklin 1997; Wooldridge 1997, 2000) Given this, the key question is to determine how and to what extent these properties of agenthood can be seen to be a useful means of characterising the behaviour and properties of the economic actors who are typically involved in a process of going public. Let us restrict our evaluation ....

Wooldridge, M. (1997). "Agent-Based Software Engineering", in IEE Proceedings on Software Engineering 144(1), 26-37.

.... Furthermore, the engineering topic of agents and multiagent systems is not only a technical matter that has been picked up by industry, it is also an interesting research field that can provide new methods and techniques for a better understanding and modeling of these highly complex systems (WOOLDRIDGE, 1997), JENNINGS et al. 1998) JENNINGS, 1999) However, development methods for agent based and multiagent systems are still in their infancy and must be more advanced in order to establish the technology in an industrial context. As stated in (PARUNAK, 1999) Relatively less attention has been ....

....the best possible actions. But even these more concrete specifications of agents are still difficult to break down into operational concepts. Therefore, a second level of abstraction is necessary that describes how the abstract concepts of the first level are made executable on computer hardware. (WOOLDRIDGE, 1997) suggests three possible means to achieve this goal. The first possibility is functional refinement as it is common in most standard Software Engineering environments, the second one is direct execution of the specifications which implies powerful description languages and runtime environments and ....

[Article contains additional citation context not shown here]

WOOLDRIDGE, M. (1997). Agent-based software engineering. IEE Proceedings on Software Engineering, 144(1):26--37.

....characteristic which many, but not all, consider important [13] Intelligence is always a desirable characteristic but is not strictly required by the paradigm. The paradigm is still forming. The roots of agent oriented (AO) methodology attain from OOP methodology [14] 15] 16] and AI studies [17]; hence, an intelligent agent may be defined as a decision making system that acts on and reacts to the environment . Agent to agent communication is the key to realize the potential of the agent paradigm, just as the development of human language was the key to the development of human ....

M. Wooldridge, "Agent-based software engineering", IEEE Proc.- Softw. Eng., Vol.144, No.1 , Frebruary 1997

....are being viewed in terms of autonomous agents. Agents are being espoused as a new theoretical model of computation that more closely reflects current computing reality than Turing Machines [58] Agents are being advocated as a next generation model for engineering complex, distributed systems [36,59]. Agents are also being used as an overarching framework for bringing together the component AI subdisciplines that are necessary to design and build intelligent entities [41,49] Yet despite this intense interest, a number of fundamental questions about the nature and the use of the ....

....conditions so they can always be extended. Here the key definitional problem relates to the term agent . At present, there is much debate [16] and little consensus, about exactly what constitutes agenthood. However, an increasing number of researchers find the following characterisation useful [59]: An agent is an encapsulated computer system that is situated in some environment and that is capable of flexible, autonomous action in that environment in order to meet its design objectives. There are a number of points about this definition that require further explanation. Agents are: i) ....

[Article contains additional citation context not shown here]

M. Wooldridge, Agent-based software engineering, IEE Proc. Software Engineering 144 (1) (1997) 26--37.

....approaches such as object oriented, expert systems, or distributed computing approaches. In general, Object oriented (OO) systems, expert systems, and distributed computing techniques do not offer solutions to the kind of problems for which multi agent systems are used, for a range of reasons (Wooldridge, 1997). OO techniques are good in general, but are rather low level for intelligent applications. They can be used, for instance, to implement knowledge representations, but they do not themselves provide a knowledge representation. OO development methodologies can, however, be seen as a low level ....

M. Wooldridge, 1997. "Agent-based Software Engineering". In IEE Proceedings on Software Engineering, 144(1):26--37.

....and prototyping environment for MAS, can enhance its flexibility and usability. 1 Introduction Intelligent agents and multi agent systems (MAS) are increasingly being acknowledged as the new modelling techniques to be used to engineer complex and distributed software applications [17, 9]. Agent based software development is concerned with the realization of software applications modelled as MAS. A two phase approach can be adopted to develop agent applications at the macro level before implementing the final application. 1. Specification of the MAS: describe the services ....

M. Wooldridge. Agent-based Software Engineering. IEE Proc. of Software Engineering, 144(1), 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, #, for infinite repetition (see Table 3. 1 for more details) They thus resemble # 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," IEEE Proc. Software Eng., 144(1):26--37, February 1997.

No context found.

. M. Wooldridge, Agent-based software engineering, IEEE Proc. Software Engineering 144 (1) (1997) 26-37

No context found.

M. Wooldridge, "Agent-based software engineering," IEE Proc. Software Eng., vol. 144, no. 1, pp. 26 -- 37, 1997.

No context found.

Wooldridge, M. Agent-based software engineering. IEE Proc. Software Engineering, 144. 26-37. 1997.

No context found.

Wooldridge, M. 1997. Agent-Based Software Engineering. IEE Proc. on Software Engineering, 144(1):26--37, 1997.

No context found.

Michael Wooldridge. Agent-Based Software Engineering. IEE Proc Software Engineering, 144:26--37, 1997.

No context found.

Wooldridge, M. Agent-based software engineering. IEE Proc. Software Engineering, 144. 26-37. 1997.

No context found.

Wooldridge, M.: Agent based software engineering. IEEE Proc Software Engineering 144(1) 1997, 26-37

No context found.

Wooldridge, M. 1997. Agent-Based Software Engineering. IEE Proc. on Software Engineering, 144(1):26--37, 1997.

No context found.

Agent-based Software Engineering. M. Wooldridge. Technical Report. September 1997.

No context found.

M. Wooldridge, "Agent-based Software Engineering, IEE Proc. Software Eng., Vol. 144, No. 1, IEE Press, London, 1997, pp. 26--37.

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