| B. Bauer, J. Muller, and J. Odell, " Agent UML: A formalism for specifying multiagent software systems," Int. Journal of Software Engineering and Knowledge Engineering, vol. 11(3), pp. 207--230, 2001. 164 |
....feature of the Tropos methodology is that it aspires to span the overall software development process, from early requirements to implementation. This is represented in Figure 5 which shows the relative coverage of Tropos as well as i [14] KAOS[5] GAIA [13] AAII [4] MaSE [6] and AUML [1]. While Tropos covers the full range of software development phases, it is at the same time well integrated with other existing work. Thus, for early and late requirements Kaos Early Late Requirements Detailed Design Architectural Design Requirements Tropos Gaia AAII AUML and Mase i ....
....It is interesting to note that much of the Tropos methodology can be combined with non agent (e.g. object oriented or imperative) software development paradigms. For example, one may want to use Tropos for early development phases and then use UMLfor later phases. At the same time, work on AUML [1]allows us to exploit existing UML techniques during (our version of) agent oriented software development. As indicated in Figure 5, our idea is to adopt AUML for the detailed design phase. An example of how this can be done is given in [11] The metamodel presented in Section 4 has been developed ....
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. Int. Journal of Software Engineering and Knowledge Engineering, 11(3):207-- 230, 2001.
....of various currently used methodologies for our purpose, including AUML, Petri nets and statecharts. This analysis also stands as a comparison between the di#erent notations and our approach for representing agent interaction protocols. 4. 1 Specifying Protocols in AUML Bauer et al. [2] have proposed AUML, Agent Unified Modeling Language) as an extension of UML to define interaction protocols between agents. AUML is intended to be a graphical specification technique, which relies partly on FIPA ACL by using a subset of its communicative acts as messages. An AUML Interaction ....
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A Formalism for Specifying Multiagent Software Systems. In AOSE, pages 91--104, 2000.
....of the system global architecture in terms of subsystems, that are represented as actors, and their data dependencies, that are represented as actor dependencies. The detailed design phase aims at specifying each architectural component in further detail (adopting a subset of the AUML diagrams [17, 1]) in terms of inputs, outputs, control and other relevant information. Finally, during the implementation phase, the actual implementation of the system is carried out, consistently with the detailed design. More details and motivation about these five phases can be found in [12, 11, 13, 19] ....
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software system. In P. Ciancarini and M. Wooldridge, editors, Agent-Oriented Software Engineering -- Proceedings of the First International Workshop (AOSE2000), volume 1957, pages 91--103, Limerick, Ireland, June 2000. Springer-Verlag Lecture Notes in Computer Science.
....design, implementation and validation phases of objectoriented software systems: all of which contributed to the universal acceptance of object oriented paradigm. Only recently there have been a few proposals for Agentoriented Software Engineering (see, 15] 17] and extensions to UML (e.g. AUML [2], 8] In our research, we are developing a framework and extensions to UML to address this need. Our approach is rooted in the BDI formalism, but stresses practical software design methods instead of reasoning theories. In this paper we describe our preliminary work on the framework and ....
B. Bauer, J. P. Muller and J. Odell. "Agent UML: A formalism for specifying multi-agent software systems", First International Workshop on Agent Oriented Software Engineering, Limerick, Ireland, June 2000, pp 91-104.
....development methods which fall short of adequate, intuitive and natural modeling techniques for agents, as well as the implementation of complex communication. In most of the existing AOSE methodologies, the developers are supplied with new notations, like extensions of UML for agents [1], so that the transition from a highlevel requirements document to executable code can be supported by an adequate series of intermediate modeling artifacts. The Gaia methodology [15] which is a representative state of the art AOSE methodology, guides developers through various analysis and ....
B. Bauer, J. Mueller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. In P. Ciancarini and M. Wooldridge, editor, First Int. Workshop on Agent-Oriented Software Engineering (AOSE-2000.
....similar to the Protocol Diagrams [3] which are based on Collaboration Diagrams in UML and allow to model the interactions between agents graphically without having to worry about formal agent semantics. Our process models have less expressive power than the linear swim lane diagrams of Agent UML [1]. However, these diagrams are hard to comprehend for people without formal training and can become unintelligible when more than two roles are involved in a conversation, while our process models exploit the freedom of full fledged two dimensional visualizations amid modeling tasks. The ....
B. Bauer, J. P. Mueller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. In P. Ciancarini and M. Wooldridge, editors, AgentOriented Software Engineering. Springer-Verlag, 2001.
....feature of the Tropos methodology is that it aspires to span the overall software development process, from early requirements to implementation. This is represented in Figure 7 which shows the relative coverage of Tropos as well as i [25] KAOS [11] GAIA [24] AAII [10] and MaSE [12] and AUML [18, 1, 5]. Kaos Early Late Requirements Detailed Design Architectural Design Requirements Tropos Gaia AAII AUML and Mase i Figure 7: Comparison of Tropos with other software development methodologies. While Tropos covers the full range of software development phases, it is at the same time ....
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. Int. Journal of Software Engineering and Knowledge Engineering, 11(3):207--230, 2001.
....engineering are: i) an understanding of the situations in which agent solutions are appropriate; and (ii) principled but informal development techniques for agent systems. While some attention has been given to the latter (in the form of analysis and design methodologies for agent systems [30, 60, 39, 10, 3, 29, 53]) almost no attention has been given to the former (but see [59] 8. How to Find Out More About Agents There are now many introductions to intelligent agents and multiagent systems. Ferber [14] is an undergraduate textbook, although as its name suggests, this volume focussed on multiagent ....
Bernhard Bauer, Jorg P. Muller, and James Odell. Agent UML: A formalism for specifying multiagent software systems. In P. Ciancarini and M. Wooldridge, editors, Agent-Oriented Software Engineering --- Proceedings of the First International Workshop (AOSE-
No context found.
B. Bauer, J. Muller, and J. Odell, " Agent UML: A formalism for specifying multiagent software systems," Int. Journal of Software Engineering and Knowledge Engineering, vol. 11(3), pp. 207--230, 2001. 164
No context found.
Bauer, B., Muller, J. P., and Odell, J., (2000), `Agent UML: A Formalism for Specifying Multi-agent Software Systems', in Agent-Oriented Software Engineering, vol. 1957, Ciancarini, P. and Wooldridge, M. J., Eds. Springer-Verlag, 2000, pp. 91-104.
No context found.
B. Bauer, J. P. Muller, and J. Odell, "Agent UML: A formalism for specifying multiagent software systems," Int. J. Software Eng. Knowl. Eng. vol. 11, no. 3, pp. 207 -- 230, 2001.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent uml: A formalism for specifying multiagent software systems. International Journal of Software Engineering and Knowledge Engineering, 11(3):207--230, April 2001. 54
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. Int. Journal of Software Engineering and Knowledge Engineering, 11(3):207-- 230, 2001.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. Int. Journal of Software Engineering and Knowledge Engineering, 11(3):207-- 230, 2001. http://aot.ce.unipr.it/auml/.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. Int. Journal of Software Engineering and Knowledge Engineering, 11(3):207-- 230, 2001.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software system. In P. Ciancarini and M. Wooldridge, editors, Agent-Oriented Software Engineering -- Proceedings of the First International Workshop (AOSE2000.
No context found.
B. Bauer, J. P. Mu ller, and J. Odell, "Agent UML: A formalism for specifying multiagent software systems," Int. J. Software. Eng. Knowl. Eng., vol. 11, no. 3, pp. 207--230, 2001.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software system. In P. Ciancarini and M. Wooldridge, editors, Agent-Oriented Software Engineering -- Proceedings of the First International Workshop (AOSE2000.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software systems. Int. Journal of Software Engineering and Knowledge Engineering, 11(3):207-230, 2001.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software system. In P. Ciancarini and M. Wooldridge, editors, Agent-Oriented Software Engineering -- Proceedings of the First International Workshop (AOSE2000.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A Formalism for Specifying Multiagent Software Systems. In AOSE, pages 91--104, 2000.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent UML: A formalism for specifying multiagent software system. In P. Ciancarini and M. Wooldridge, editors, Agent-Oriented Software Engineering -- Proceedings of the First International Workshop (AOSE2000.
No context found.
B. Bauer, J. P. Muller, and J. Odell, "Agent UML: A Formalism for Specifying Multiagent Software Systems", In Proceedings of the First International Workshop on Agent-Oriented Software Engineering AOSE'00, Limerick, Ireland, LNCS 1957.
No context found.
B. Bauer, J.P. Muller, and J. Odell. Agent UML: A Formalism for Specifying Multiagent Software Systems. Int. Journal on Software Engineering and Knowledge Engineering, 2001. Included in this special issue.
No context found.
B. Bauer, J. P. Muller, and J. Odell. Agent uml: A formalism for specifying multiagent software systems. International Journal of Software Engineering and Knowledge Engineering, 11(3):207--230, April 2001. 54
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