M. Wooldridge and N. Jennings, Software Engineering with Agents: Pitfalls and Pratfalls, IEEE Internet Computing, vol. 3, issue 3, 1999.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....set of functionalities needed for his specific application. At the same time, these platforms have a large bundle of functionalities that are not necessary at all. Another problem regarding the currently available mobile agent platforms has to do with the You Ignore Related Technology pitfall [8]. Current MA platforms force the programmer to center all the development on the agents. Agents should be a small part of the distributed applications, not its corner stone. Currently, there is little or no support to develop applications that use MAs only as a small part of its infrastructure. ....

M. Wooldridge and N. Jennings, Software Engineering with Agents: Pitfalls and Pratfalls, IEEE Internet Computing, vol. 3, issue 3, 1999.

....in an ACL is generally left open to the extent that it is associated with an ontology. For example, in the Semantic Web 1 effort [3] a rich ontology language is developed by which machines may understand information. The many different ACLs and ontologies leads to an interoperability problem [61]. Solutions to this problem include the use of intermediary agents that find agents capable of translating between ontologies. Another approach is to devise information brokering agents that essentially act as intermediaries or gateways [32,31,53] 1 See also the article by Klein et al. in this ....

M. J. Wooldridge and N. R. Jennings. Software engineering with agents: Pitfalls and pratfalls. IEEE Internet Computing, 3(3):20--27, 1999.

....on the Web and users cannot wait for developers evolving their products to take advantage of these new resources. 3. Agent oriented Software Engineering The research on agent oriented software engineering is based on the possibility to model a software system at the agent level of abstraction [4,7,20,21, 26, 42, 47,46]. This level of abstraction considers agents as atomic entities that communicate to implement the functionality of the system. Various initiatives [26, 47] are devoted to establish a methodology for an agent oriented development process and this work shows a brief overview of the common ideas ....

M. Wooldridge, N. Jennings, Software Engineering with Agents: Pitfalls and Pratfalls, IEEE Internet Computing, 3(3), 1999, 20-27.

....disaster. Of the survivors many will be set back to a dicult economic status. But some of them can become real winners of the current situation, e.g. if they did not lose their property or if they are involved in the reconstruction. Thus it seems natural to resort to an agentoriented approach [10,35] rather than e.g. a macro level simulation model in which the key features of our application, e.g. the actor s preferences and a price dynamic that results from individual micro macro level interactions, could not be adequately accounted for. This approach enables to model a rather complex ....

M. Wooldridge and N.R. Jennings. Software Engineering with Agents: Pitfalls and Pratfalls. IEEE Internet Computing, May/June 1999.

....agents. The concept of intelligent agents is a useful tool for system analysis and design. That fact has led to a growing adoption of intelligent agents in the software engineering community, and the terms like agent oriented programming [29] 57] 60] agent oriented software engineering [63] [64], and agent oriented middleware [39] have been quickly coined. One key idea of agent oriented programming is that of directly programming agents in terms of mentalistic notions (such as belief, desire, and intention) 57] 63] For example, the agents intentions, i.e. how the agent acts, can ....

....for a user defined translation into the low level primitives. Agent oriented software engineering draws its justification from the fact that intelligent agents represent a powerful abstraction, perhaps as powerful as procedural abstraction, abstract data types, and object oriented programming [64]. In object oriented software engineering, systems are modeled as a collection of interacting but passive objects. In agent oriented software engineering, systems are understood and modeled as a collection of interacting autonomous agents. Thus, in a way, agentoriented approach complements the ....

M.J. Wooldridge and N.R. Jennings, Software Engineering with Agents: Pitfalls and Pratfalls, IEEE Internet Computing 3, May/June (1999), 20-27.

....search engines are http: www.searchenginebase.com and http: www.researchbuzz.com. 7 Conclusion This paper has sought to give an approach towards finding relevant litterature for agent research. Some of the references that was found using methods and information sources of this document are: [1, 2, 3, 8, 4, 5, 6, 7] One of the nicest databases (not presented in this document) is the science citation index, it provides a certain quantitative measure of how good a paper is since it counts how many who refers to it. The main problems are the cost and access of databases, and not being able to use the same ....

Wooldridge M. J. and Jennings N. R. Software Engineering with Agents: Pitfalls and Pratfalls. IEEE Internet Computing, 3(3):20--27, May/June 1999. 7 7

....Development (OOD) The word Development is sometimes interpreted as Programming , on the other hand it is frequently interpreted to include the full development process that covers the requirement specification and design, in addition to the programming itself. Software Engineering with Agents [33], Agent Based Software Engineering [12] Multiagent Systems Engineering (MaSE) 3, 31] and Agent Oriented Software Engineering (AOSE) 22, 20, 35, 15] are semantically equivalent terms, but MaSE refers to a particular methodology and AOSE seems to be the most widely used term. The di#erence ....

....In other words, agents have the right to say no [9] Can agents solve all software problems Since this is a new and rapidly growing filed, there is a danger that researchers become overly optimistic regarding the abilities of agent oriented software engineering. 2 Wooldridge and Jennings [7, 33] discuss the potential pitfalls of agent oriented software engineering. They have classified pitfalls in five groups: political, conceptual, analysis and design, agent level, and society level pitfalls. Political pitfalls can occur if the concept of agents is oversold or sought applied as a the ....

Wooldridge M. J. and Jennings N. R. Software Engineering with Agents: Pitfalls and Pratfalls. IEEE Internet Computing, 3(3):20--27, May/June 1999. 8

....have been drawing increasing attention within the agents community. In a recent paper, Wooldridge Jennings describe the possible pitfalls of applying agents inappropriately, especially on account of the limited robustness of most existing techniques for developing agent based applications [40]. We now review some of the most relevant literature on multiagent architectures and methodologies, especially those geared toward coordination. Koning et al. develop an approach based on Petri Nets to model and validate interaction protocols among agents [20] Like our approach, this approach ....

Michael J. Wooldridge and Nicholas R. Jennings. Software engineering with agents: Pitfalls and pratfalls. IEEE Internet Computing, 3(3):20--27, May 1999.

.... platforms have been proposed e.g. for the programming languages Java [LO98, VB99, Fn98] and Tcl [Gra98] The term agent is also occupied by other research communities, namely the artificial intelligence research (intelligent agents) MJ99] and the software engineering community (software agents) WJ99] Both communities have influenced the mobile agent research, so a mobile agent is also a paradigmatic software abstraction and includes autonomous behaviour (intelligence) Mobile agents are proposed for different tasks such as network search (more recently e commerce [HGF # 99] network ....

Michael J. Wooldridge and Nicholas R. Jennings. Software engineering with agents: Pitfalls and pratfalls. IEEE Internet Computing, pages 20--27, May/June 1999.

....even during runtime due to asynchronous text parsing based message exchange, and reuse of the outer language as well as generic agents as a programming environment. 1 1 Agent Development Characteristics Jennings and Wooldridge have described Agent Oriented Software Engineering (AOSE)[19] [7] AOSE effectiveness claims are based upon three strategies for addressing complex systems: decomposition, abstraction, and organization and that the agent oriented mindset gives one an advantage in using these strategies. That agents have objectives gives one a clear way to decompose the ....

M. Wooldridge, and N. R. Jennings "Software Engineering with Agents: Pitfalls and Pratfalls " in IEEE Internet Computing, 3 (3), May/June 1999.

....approach is that although a user may be interested in many things (perhaps too many sometimes) there should be only a limited number of subjects conveyed at any time according to the active profile. Agent Society Communication and Collaboration In our approach we intend to exploit and benefit [20] from the inherent distributed nature of agents, which if considered as a whole, appear as an intelligent machine [21] Collections of agents, if broadly modeled on the real world, can form societies, which may be assembled from communities to which different groups may belong according to their ....

Wooldridge, M.J. & Jennings, N.R.: "Software engineering with agents: pitfalls and pratfalls", IEEE Internet Computing v3 n3, May-June 1999, pp. 20--27

....have been drawing increasing attention within the agents community. In a recent paper, Wooldridge Jennings describe the possible pitfalls of applying agents inappropriately, especially on account of the limited robustness of most existing techniques for developing agent based applications [40]. We now review some of the most relevant literature on multiagent architectures and methodologies, especially those geared toward coordination. Koning et al. develop an approach based on Petri Nets to model and validate interaction protocols among agents [20] Like our approach, this approach ....

Michael J. Wooldridge and Nicholas R. Jennings. Software engineering with agents: Pitfalls and pratfalls. IEEE Internet Computing, 3(3):20--27, May 1999.

.... having to maintain an ongoing interaction with a dynamic and unpredictable environment [45] Finally, the aim is to concentrate on issues that are intrinsic to the agent based philosophy (cf. the many social and pragmatic problems often associated with developing systems using any new technology [61]) Against this background, there are two major drawbacks associated with the very essence of an agent based approach: the patterns and the outcomes of the interactions are inherently unpredictable; predicting the behaviour of the overall system based on its constituent components is ....

M. Wooldridge, N.R. Jennings, Software engineering with agents: Pitfall and pratfalls, IEEE Internet Computing 3 (3) (1999) 20--27.

No context found.

M. Wooldridge and N. R. Jennings. Software Engineering with Agents: Pitfalls and Pratfalls. In IEEE Internet Computing, May/June 1999.

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