| Jennings, N. R. and Wooldridge, M., "Agent-Oriented Software Engineering," in Handbook of Agent Technology, Bradshaw, J., Ed.: AAAI/MIT Press, 2001. |
....in industry and or enterprise depends on the existence of the necessary tools to support the analysis, design and implementation of agent based software. Over the last few years, the application of software engineering techniques to agents, known as Agent Oriented Software Engineering (AOSE ) [16] has produced several related research studies. These works have mainly centered on trying to search for development methods which are able to model real complex systems with clearly distributed characteristics. These works are principally based on a view of the system as a computational ....
N. R. Jennings and M. Wooldridge. Agent-oriented software engineering. Handbook of Agent Technology (ed. J. Bradshaw). AAAI/MIT Press, 2000.
....data. The resulting algorithms are provably exact in that the decision tree constructed from distributed data is identical to that obtained by the corresponding algorithm in the batch setting (i.e. when all of the data is available in a central location) Agent oriented software engineering [3, 1] o#ers an attractive approach to implementing modular and extensible distributed computing systems. For the purpose of this discussion, an agent is an encapsulated information processing system that is situated in some environment and is capable of flexible, autonomous action within the ....
N. Jennings, M. Wooldridge, Agent-oriented software engineering, in: J. Bradshaw (Ed.), Handbook of Agent Technology, AAAI/MIT Press, 2001.
....are directed to structure and support an effective development of agent systems. Decomposition, abstraction, and organization are Figure 2. 3D view of the RoboCup rescue simulator (http: www.robocup.org ) the basic strategies in designing multi agent systems, as Jennings and Wooldridge observe [38, 17]. That agent systems work largely by emergent behavior and handle errors gracefully [25] is another reason, which asks for simulation as an evaluation method employed during the agent development cycle 4 CONCLUSION The more software systems are needed that work autonomously in open dynamic ....
N.R. Jennings and M Wooldridge. Agent-Oriented Software Engineering. In J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press, to appear.
....application. Corresponding author. The work of this author has been partly carried out while visiting TU Wien. One of the main reasons for the successful rise of the agent oriented software paradigm is that it provides the right level of abstraction for engineering this kind of applications [24,43,61], representing a valuable help for handling their complexity and developing them. Agents and multi agent systems (MASs) are more and more successfully deployed and used in practice, even if many theoretical issues underlying them are not fully understood at this point and subject of current ....
N. R. Jennings and M. Wooldridge. Agent-Oriented Software Engineering. In J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press. To appear.
....depends on the their ability to use adaptive interaction protocols. Keywords Multi agent systems, agent conversations, adaptive systems. 1. INTRODUCTION There is a widely held view that multi agent systems provide a robust and scalable approach for the solution of complex problems [6]. Each individual agent is presumed to be a specialist for a particular task, and the expectation is that, just as in the sphere of human engineering, complex projects can be undertaken by a collection of agents, no one of which has the capability of performing all the required tasks for the ....
Jennings, N. R., "Agent-oriented software engineering", Proceedings of the 12th International Conference on Industrial and Engineering Applications of AI, (1999).
....will eventually reach up to 5 5 2 3 4 = 780 peers. Obviously, there will be peers that know about the same peers, so this number may be slightly smaller. Agent based computing [5] o ers the desired characteristics to implement a peer to peer system. Indeed, from a design viewpoint [6], agents are the right abstraction to represent peers, because of their autonomous and social natures [7] In such a peer to peer context, their complex interactions can be the basis of a cooperative multi agent system. Additionally, from an engineering viewpoint, agents systems [8] support ....
Jennings, N.R., Wooldridge, M.: Agent-Oriented Software Engineering. In: Handbook of Agent Technology. AAAI/MIT Press (2001)
....the role or purpose of a service is only known to itself. Moreover, unlike teamwork type environments where each agent is pre assigned certain duties during the creation of the agents, here the goal is set by a single client agent only when he needs to satisfy that goal. Jennings and Wooldridge [46] have described an agent oriented way to look at software engineering. The components that make up a component based software can be best designed using agents since it ensures least coupling and autonomy. The various agents in a software system interact with each other to ful ll both their ....
N.R. Jennings and M. Wooldridge. Agent-oriented software engineering. In Proc.Proc. 12th Int Conf on Industrial and Engineering Applications of AI. Cairo. Egypt., 1999.
....[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 the full lifecycle methodological support for the development of object oriented information systems. This synergy is underpinned by the recent proposals ....
Jennings, N.R. and Wooldridge, M. (2001). Agent-oriented software engineering. In J. Bradshaw (ed.), Handbook of agent technology (in the press). Cambridge, MA, USA: AAAI/MIT Press.
....4. Actions, which are the atomic actions that the agent can take. Each action has a name and may have parameters. 5. Behaviour rules, which determine the behaviour of the agent. Agents constmctively defined above have a number of features. First, they are autonomous in the sense of [17] and [19]. Second, they are communicative and social, yet it is independent of any particular agent communication language or protocol. Third, agents are situated in their designated environments. It requires an explicit and clear specification of the boundary and interface between an agent and its ....
Jennings, N.R.: Agent-Oriented Software Engineering. In: Garijo, F.J., Boman, M. (eds.): Multi-Agent System Engineering, Proc. of 9th European Workshop on Modelling Autonomous Agents in a Multi-Agent World, Valencia, Spain (June/July 1999). LNAI, Vol. 1647. Springer, Berlin (1999) 1-7
....system designers have the same possibility thanks to some modeling languages like Agent UML [9] 2] Agent UML is based on UML. As Odell and Bauer quoted it, it is not possible to use directly UML since several di erences exist between agents and objects like autonomy or ability to cooperate [8]. However, it seems to be important to capitalize on the skills of designers. Indeed, multiagent system designers are often software engineers who use UML or are aware of it. Even if a strong interest is manifest on Agent UML (see the Internet site http: www.auml.org for papers on the subject) ....
N. R. Jennings and M. Wooldridge. Agent-oriented software engineering. In J. Bradshaw, editor, Handbook in Agent Technology. MIT Press, 2000.
....it (ibid. it is important that designers have a modeling language which is not far from their usual modeling language. Actually, most of designers have rst designed software or they are aware of UML. Moreover, it is not possible to use directly UML since objects and agents are not the same [7]. Particularly, agents encompass the notion of autonomy and the ability to cooperate. The modeling language Agent UML is more and more an appealing approach if we consider the number of papers written on it (see Agent UML web site ) Designing multiagent systems with Agent UML needs to ....
N. R. Jennings and M. Wooldridge. Agent-oriented software engineering. In J. Bradshaw, editor, Handbook in Agent Technology. MIT Press, 2000.
....than the one in distributed systems. Actually, processes only send data through messages where agents use verbs and contents. Verbs are applied to contents. For instance, inform(b = 10) means that the receiver is informed that the sender believes that the value of b is 10. We let readers consult [12] for a more detailed presentation of the di erences between agents and objects. Interaction protocol designers have considered formal description techniques used for communication protocols: nite state machines [2] Petri nets [4] and languages such as LOTOS [13] and SDL [11] Another type of ....
N. R. Jennings and M. Wooldridge. Agent-oriented software engineering. In J. Bradshaw, editor, Handbook in Agent Technology. MIT Press, 2000.
....is a fine grained agent building toolkit that includes some ideas similar to those expressed in this paper, although to our understanding it has some architectural differences with our approach and has not been used as the basis for a coarse grained agent building infrastructure. software agents [2,3] are even more suited to the exploitation of the three notions listed above. For such an argument to hold in practice, however, it is necessary that there be a suitable agent building infrastructure available for software engineers so that they can employ agent constructs in the various ways that ....
N. R. Jennings and M. Wooldridge. Agent-oriented software engineering. In. J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press, 2000.
....is a fine grained agent building toolkit that includes some ideas similar to those expressed in this paper, although to our understanding it has some architectural differences with our approach and has not been used as the basis for a coarse grained agent building infrastructure. software agents [2,3] are even more suited to the exploitation of the three notions listed above. For such an argument to hold in practice, however, it is necessary that there be a suitable agent building infrastructure available for software engineers so that they can employ agent constructs in the various ways that ....
N. R. Jennings. Agent-oriented software engineering. In Proceedings of the 12th International Conference on Industrial and Engineering Applications of AI, pages 410, 1999.
....The advent of global computing platforms, like the Internet and the World Wide Web, has only increased the requirement of designing systems including complex interactions. Many researchers now believe that in future, computation itself will be understood as chiefly as a process of interaction [23]. This has in turn led to the search for new computational abstractions, models, and tools with which to conceptualise and implement interacting systems. Since the 1980s, software agents and multi agent systems have grown into what is now one of the most active areas of research and development ....
N. R. Jennings. On agent-base software engineering. Artificial Intelligence, 117:277-- 12 Agent-oriented Software Engineering 296, 2000.
....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 ....
N.R. Jennings and M. Wooldridge, Agent oriented software engineering, (M.J. Bradshaw Ed) Handbook of Agent Technology, MIT Press, 2000.
....physically distributed hardware and software resources. The design of the ConBa system presents three important aspects of agenthood: decomposition, autonomy and anthropomorphism. The system described is very naturally decomposable in agent components each with a specific objective to achieve [5] and representing a user of the system. Autonomy is displayed by the systems ability to perform actions without an explicit request of the user and possibly asynchronously with respect to the user activity (e.g. a Tutor agent may be querying another one whilst the user is surfing the site) ....
N.R.Jennings and M.Wooldridge, Agent Oriented Software Engineering, Handbook of Agent Technology J. Bradshaw Editor AAAI/MIT Press. (to appear)
....a multiagent system. In particular, multiagent systems can provide benefits such as processing speed up, reduced communication bandwidth, and increased reliability [10] However, the academic community, as well as industry, is still trying to determine which problems call for a multiagent approach [8, 11]. Once a designer has made the decision to use a multiagent design, a number of methodologies exist for building multiagent systems [2, 3, 4, 7, 14, 15, 19] The methodologies range from extensions of existing object oriented methodologies to new agent oriented techniques, which offer a new ....
....4 discusses the results of the survey. Section 5 provides the context in which we applied the criteria to the decision making framework. Finally, Section 6 presents our conclusions. 1. 1 Related Techniques The strategy taken by Jennings and Wooldridge was to provide intellectual justification [8] for the validity of the agent oriented techniques. Their justification, however, comes from a qualitative analysis of how well the technique addresses the principles that allow software engineering techniques to deal with complex problems proposed by Booch: abstraction, decomposition, and ....
[Article contains additional citation context not shown here]
Jennings, N.R., and Wooldridge, M.J.: Agent-Oriented Software Engineering. To appear in Bradshaw, J. (ed.): Handbook of Agent Technology. AAI/MIT Press (2001) 18
....application specific parts of a system. It will be supported by a software tool which is currently in development. 1 Introduction Agent oriented software engineering (AOSE) is a promising new approach to software engineering that uses the notion of an agent as the primary entity of abstraction [16]. The agent oriented approach is rapidly emerging as a powerful paradigm for designing and developing complex software systems. AOSE researchers hope that the use of the agent abstraction will provide a significant improvement to current software engineering practice, similar to the improvements ....
N. R. Jennings and M. Wooldridge. Agentoriented software engineering. In J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press, 2000.
....models in multiagent based simulation (MABS) and more generally in multi agent systems (MAS) 1 . Firstly, agent social interactions frequently occur through high level communication languages, and consequently are conducted on levels of abstraction within or above Newell s Knowledge Level [19,16]. On a practical level, the system designer usually prescribes the agent s goals. However, the unpredictable nature of the other agents motivations, and high level normative organizational behaviors, raises higher the dynamics of the other agents goals to the eye of the agent. Agents may not ....
Jennings N. (1999), Agent Oriented Software Engineering, Multi-Agent Systems Engineering, Proceedings of MAAMAW99, Garijo F. and Bosman M. editors, LNAI1647, Springer Verlag, pages 1-7.
....associated with specific model components may be changed. Organisation the process of identifying and managing the interoperation of complex components. It has been shown that it is plausible to consider agents to be e#ective entities for use in connection with all three of these techniques [11]. The consistent use of agents throughout the software development process in this manner is often termed agent based software engineering. For agent based software engineering to hold in practice, it is necessary that there be a suitable agent building infrastructure available for software ....
N. R. Jennings and M. Wooldridge. Agent-oriented software engineering. In J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press, 2000.
....the Opal framework for the construction of more complex agents that are based on the FIPA specifications. 1. INTRODUCTION It has been argued that the use of agents, particularly intelligent agents, can be useful for the modelling and construction of complex distributed information systems [9, 10]. Implicit in these arguments is the basic notion that the use of agents supports scalability; that as system complexity scales upward to highly distributed and dynamic environments, the use of agents will be essential for the successful operation and maintenance of these systems. Three important ....
N. R. Jennings. Agent-oriented software engineering. In Proceedings of the 12th International Conference on Industrial and Engineering Applications of AI, pages 4--10, 1999.
....which makes it quite difficult to coherently glue them together for developing a final efficient application. One of the main reasons for the successful rise of the agent oriented software paradigm is that it provides the right level of abstraction for engineering this kind of applications [18, 34, 52], representing a valuable help for handling their complexity and developing them. Agents and multi agent systems (MASs) are more and more successfully deployed and used in practice, even if many theoretical issues underlying them are not fully understood at this point and subject of current ....
N. R. Jennings and M. Wooldridge. Agent-Oriented Software Engineering. In J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press, 2001. To appear.
....in turn, reduces the system control complexity and communication overhead in a network environment at run time, and hence, increases the response time of the system. The agent paradigm has been highly advocated as a promising next generation software model for complex and distributed systems [17]. We propose an Adaptive Visualization Agent Model (AVAM) for Internet applications. The goals are to endow individual visualization pipeline processes with independent abilities and minimal communication needs and provide globally coherent and efficient behavior. In section 4, we will elaborate ....
Jennings, N.R. and Wooldridge M.; Agent-oriented Software Engineering, in: J. Bradshaw (Ed.), Handbook of Agent Technology, AAAI/MIT Press, 2000.
....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 ....
....in complexity. Thus, in both legacy code conversion and the pure agent development, for at least a very important class of agents, agent construction is partially characterized by a modeling based on a common agent theory. 1. 3 Syntax based Development Jenning s ABSE paper[6] based largely upon [7], is also largely lacking in the detail necessary for objective determination of agent based software engineering, with one important exception. Jennings, as have many others, notes that agents have their own persistent thread of control and notes later that this enables agents to select their ....
N. R. Jennings, and M. Wooldridge "Agent-Oriented Software Engineering" in Handbook of Agent Technology, (ed. J. Bradshaw) AAAI/MIT Press, 2000. See also ftp://ftp.elec.qmw.ac.uk/pub/isag/distributed-ai/publications/agt-handbook.pdf.
....and disadvantages of several approaches. Conceptually, it is also not inconsistent to follow different principles for different components of the same system. The two main paradigms that are under consideration are Distributed Object Computing [ref: OMG] and Agent based Computing [Jennings, 1999] [Jennings and Wooldridge, 2000]. In Distributed Object Computing as advocated for by OMG via CORBA and related technologies, the granularity of the components of the system is the object. The main advantage of this approach is that it is well understood and in principle fits well with the object oriented paradigm. As ....
....behaviour, trying to achieve their goals through autonomous action. While this seems 5 to be a promising perspective, there are some obvious disadvantages of this paradigm. It is mostly not verified yet, and lacks well established development tools and methodologies, as well as stable standards [Jennings and Wooldridge, 2000]. Through the communications aspects that were discussed in Section 2, which are very much connected with Agent based Computing, systems that follow this approach are well suited for open environments. In the following, a distinction will be made between two aspects of agent based computing. While ....
Jennings, N., and Wooldridge, M. (2000) "Agent-Oriented Software Engineering". In Handbook of Agent Technology (ed. J. Bradshaw) AAAI/MIT Press. (to appear)
....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 ....
N.R. Jennings, M. Wooldridge, Agent-oriented software engineering, in: J. Bradshaw (Ed.), Handbook of Agent Technology, AAAI/MIT Press, 2000, to appear.
....pressing if multi agent systems are to break out of being a niche technology used by the few, to something that is part of the armoury of a mainstream software engineer. In the last few years, several attempts have been made to develop agent oriented modelling techniques and methodologies [18, 20]. However, none of these techniques can yet be regarded as a comprehensive methodology for the analysis and design of multi agent systems. The Gaia methodology [35] is one of the few attempts that is specifically tailored to the analysis and design of multi agent systems and that deals with both ....
.... encapsulation and interaction among entities suggests that a multi agent system could actually be built by exploiting an object oriented methodology [27, 5, 30] However, object oriented approaches fall short in supporting the full notions of agents , and organisations as first class entities [12, 20]. This is hardly surprising since these represent the two main distinguishing features of multi agent systems with respect to objectbased systems. Object oriented methodologies have objects as their basic conceptual model and therefore have no support for capturing reactive and proactive ....
N. R. Jennings and M. Wooldridge. Agent-oriented software engineering. In Handbook of Agent Technology. ACM, 2000.
No context found.
Jennings, N. R. and Wooldridge, M., "Agent-Oriented Software Engineering," in Handbook of Agent Technology, Bradshaw, J., Ed.: AAAI/MIT Press, 2001.
No context found.
N. Jennings and M. Wooldridge. Agent-Oriented Software Engineering. Handbook of Agent Technology. AAAI/MIT Press, J. Bradshaw, edition, 2000.
No context found.
N. R. Jennings. Agent-Oriented Software Engineering. In 12th Int Conf on Industrial and Engineering Applications of AI, Cairo, Egypt, 4-10, 1999.
No context found.
Jennings, N. R. and Wooldridge, M., 2000, "Agent-Oriented Software Engineering", Handbook of Agent Technology, AAAI/MIT Press.
No context found.
N. R. Jennings, M. Wooldridge, "Agent-Oriented Software Engineering" in Handbook of Agent Technology (ed. J. Bradshaw) AAAI/MIT Press 2001
No context found.
Jennings, N., and Wooldridge, M. (2000) "Agent-Oriented Software Engineering". In Handbook of Agent Technology (ed. J. Bradshaw) AAAI/MIT Press. (to appear) http://citeseer.nj.nec.com/wooldridge99agentoriented.html
No context found.
Jennings, N. R. & Wooldridge, M. (2001). Agent-Oriented Software Engineering. in Handbook of Agent Technology (ed. J. Bradshaw) AAAI/MIT Press. (to appear)
No context found.
N. R. Jennings and MWooldridge (2000) "Agent-Oriented Software Engineering" in Handbook of Agent Technology (ed. J. Bradshaw) AAAI/MIT Press.
No context found.
Nicholas R. Jennings and Michael Wooldridge. Agent-oriented software engineering. In J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press, 2000.
No context found.
N. Jennings, "Agent-Oriented Software Engineering," Proceedings of the 9th European Workshop on Modeling Autonomous Agents in a Multi-Agent World: Multi-Agent System Engineering (MAAMAW-99), 1999.
No context found.
N.R. Jennings and M. Wooldridge. Agent-oriented software engineering. In J. Bradshaw, editor, Handbook of Agent Technology. AAAI/MIT Press, 2002.
No context found.
N. R. Jennings, M. Wooldridge, "Agent-Oriented Software Engineering" in Handbook of Agent Technology (ed. J. Bradshaw) AAAI/MIT Press 2001
No context found.
Jennings, N.R. and M. J. Wooldridge. "Agent-Oriented Software Engineering." In Handbook of Agent Technology, ed. J. Bradshaw, AAI/MIT Press (To Appear).
No context found.
Agent-Oriented Software Engineering. N. Jennings. Proceedings of MAAMAW99, Valencia, Spain. June, 1999.
No context found.
N. R. Jennings, M. Wooldridge, "Agent-Oriented Software Engineering", in Handbook of Agent Technology, J. Bradshaw Ed., AAAI/MIT Press, 2000.
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