Lin Padgham and Michael Winikoff. A methodology for agent oriented software design. Technical Report TR-01-2, School of Computer Science and Information Technology, RMIT University, 2001.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....independent process rather than driving the design as in Tropos. Other work has identified the need for agent oriented software engineering [19, 22] Over the last several years we have been developing an agent oriented methodology in collaboration with Agent Oriented Software called Prometheus [18] Prometheus is a detailed and complete ( start to end ) process for specifying, designing, and implementing intelligent agent systems. It is this methodology that we use in our investigation into the use of interaction protocols within a debugging agent. 2.2 Interaction Protocols One of the ....

....rather than as an error, since interaction diagrams are not intended to be complete. Interaction protocols are but one instance of a design artifact that can be beneficially used in debugging. We are investigating how other design artifacts found in agent oriented methodologies such as Prometheus [18] can be used for debugging multi agent systems. Acknowledgements: We would like to acknowledge the support of Agent Oriented Software Pty. Ltd. and of the Australian Research Council (under grant CO0106934) We would also like to thank James Harland for comments on a draft of this paper. 7. ....

Lin Padgham and Michael Winikoff. A methodology for agent oriented software design. Technical Report TR-01-2, School of Computer Science and Information Technology, RMIT University, 2001.

....influence the choice of plans; events may cause changes in the current goals of the agent, which, in turn, may influence the choice of plan. An explicit goal representation allows reasoning with goals, such as checking for conflicts. 3. THE PROMETHEUS METHODOLOGY The Prometheus 4 methodology [10] is a detailed process for specifying, designing, and implementing intelligent agent systems which we have been developing over the last several years. Our goal in developing Prometheus is to have a process with defined deliverables which can be taught to industry practitioners and undergraduate ....

....the phases are described in a sequential fashion it is acknowledged that like most Software Engineering methodologies, practice involves revisiting earlier phases as one works out the details. The following description of the phases and deliverables is necessarily brief, for more information see [10]. 3.1 System Specification Agent systems are typically situated in a changing and dynamic environment, which can be influenced (but not totally controlled) by the agent system. One of the earliest questions which must be answered is how the agent system is going to interact with this ....

L. Padgham and M. Winikoff. A methodology for agent oriented software design. Technical Report TR-01-2, School of Computer Science and Information Technology, RMIT University, 2001.

....agent programs, teaching students and assisting them to build agent programs, and developing and running workshops for academia and industry 3 , we have developed an initial process of agent design and development for BDI systems. 4 This process is explained more fully in the technical report [15] and is still being refined and developed. This paper identifies the concept set which we have found to be important in developing BDI systems and the relationships between these concepts. These of course rely heavily on the standard BDI concepts though we have found it necessary to clarify some ....

....when designing a plan we may realise that the agent needs to know a certain piece of information which implies the addition of a belief which might imply the addition (or modification) of goals and plans. A comprehensive methodology for the detailed design of agent systems is described in [15]. Here we concentrate on illustrating the way in which instances of the relevant concepts are identified and defined. Decisions are not considered here since questions which an agent needs to answer as it runs aren t specific to a given application domain; rather, they are specific to a given ....

[Article contains additional citation context not shown here]

L. Padgham and M. Winikoff. A methodology for agent oriented software design. Technical Report TR-01-2, School of Computer Science and Information Technology, RMIT University, 2001.

....agent programs, teaching students and assisting them to build agent programs, and developing and running workshops for academia and industry 3 , we have developed an initial process of agent design and development for BDI systems. 4 This process is explained more fully in the technical report [8] and is still being refined and developed. This paper identifies the concept set which we have found to be important in developing intelligent agent systems and the relationships between these concepts. These of course rely heavily on the standard Belief Desire Intention (BDI) concepts [9, 10] ....

....when designing a plan we may realise that the agent needs to know a certain piece of information which implies the addition of a belief which might imply the addition (or modification) of goals and plans. A comprehensive methodology for the detailed design of agent systems is described in [8]. Here we concentrate on illustrating the way in which instances of the relevant concepts are identified and defined. Decisions are not considered here since questions which an agent needs to answer as it runs aren t specific to a given application domain; rather, they are specific to a given ....

[Article contains additional citation context not shown here]

L. Padgham and M. Winikoff. A methodology for agent oriented software design. Technical Report TR-01-2, School of Computer Science and Information Technology, RMIT University, 2001.

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