A. Kendall. A methodology for developing agent based systems for enterprise integration. Modelling and Methodologies for Enterprise Integration. Chapman and Hall, 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....characteristics. These works are principally based on a view of the system as a computational organization which consist of di#erent interacting entities. Some of the relevant existing approaches are: the work of Kinny on the BDI model [22] the GAIA methodology [30] the works of Kendall [21] and Bursmeister [6] the AUML approach [24] the specification of DESIRE [5] the methodologies MAS CommonKADS [15] and MASSIVE [23] and more recently the works of TROPOS [26] MaSE [29] and Message [10] The majority of these approaches entail di#erent phases, models and or artifacts, in order ....

A. Kendall. A methodology for developing agent based systems for enterprise integration. Modelling and Methodologies for Enterprise Integration. Chapman and Hall, 1996.

....description, Data world conceptual modelling and System user interaction modelling. The Design phase consists of MAS architecture scenario description, Object modelling, Agent Modelling, Conversation modelling and system design overall validation. The methodology proposed by Kendall et al. [14] is composed of the following models; the Function Model, Use Case Model, Dynamic Model and the Agent Oriented System which, in turn, consists of Agent Identification, Co ordination Protocols or Scripts, Plan invocation, Beliefs, Sensors, and Effectors. It is believed that with this methodology, ....

Kendall, E.A., Malkoun, M.T., Jiang, C.: A Methodology for Developing Agent-Based Systems for Enterprise Integration. In Luckose, D., Zhang, C., (eds.): Proceedings of the First Australian Workshop on DAI, Lecture Notes on Artificial Intelligence. Springer-Verlag: Heidelberg, Germany (1996)

....Analysis and Design [1] Agent Modelling Technique for Systems of BDI agents [23] Multi Agent Scenario Based Method [25] emphasize the roles modelling. Modelling technique (IDEF) widely used for BPR diagramming has been also applied in agent oriented methodology for enterprise modelling [21]. Particular attention on multiagent methodologies development has been paid by Wooldridge [35] For him a multiagent system is one that consists of a number of agents, which interact one with another, typically by exchanging messages through some computer network architecture. So the first ....

Kendall, E.A., Malkoun, M.T., Jiang, Ch.: A methodology for developing agent based systems for enterprise integration, in: Luckose D., Zhang C. (ed.) Proceedings of the First Australian Workshop on DAI, Lecture Notes on Artificial Intelligence, Springer-Verlag, Berlin (1996)

....Models (HLIM) 8] 5. The CoMoMAS Methodology and Environment for MultiAgent System Development [12] 6. Multi Agent Scenario Based Method (MASB) 4] 7. Analysis and Design of Multiagent Systems Using MASCommonKADS [5] 8. Agent Oriented Methodology for Enterprise Modelling (AOMEM) [9]; 9. Agent Oriented Design of Soccer Robot Team (Cassiopeia) 3] For reasons of space constraints, we will not go into the details of the comparative analysis here. We only present, in what follows, the main observations. The techniques used in the methodologies we have evaluated constitute ....

Kendall E.A., M.T. Malkoun & C. Jiang (1996). A Methodology for Developing Agent-based Systems for Enterprise Integration, In D.Luckose and Zhang C., editors, Proceedings of the First Australian Workshop on DAI, Lecture Notes on Artificial Intelligence, Springer-Verlag: Heidelberg, Germany.

....Methodology and Environment for MultiAgent System Development [NOR 96] 6. Multi Agent Scenario Based Method (MASB) Moulin and Brassard 1996] 7. Analysis and Design of Multiagent Systems Using MASCommonKADS [Carlos et al. 1998] 8. Agent Oriented Methodology for Enterprise Modelling (AOMEM) [Kendall et al. 1996]; 9. Agent Oriented Design of Soccer Robot Team (Cassiopeia) Anne et al. 1996] 10. Methodology for Engineering Systems of Software Agents (MESSAGE) Message 2001] We consider these 10 methodologies as representative of the main existing approaches. Except for validation, verification and ....

Kendall, E.A., Malkoun, M.T., and Jiang, C. 1996 A methodology for developing agent based systems for enterprise integration, In D.Luckose and Zhang C., editors, Proceedings of the First Australian Workshop on DAI, Lecture Notes on Artificial Intelligence, SpringerVerlag : Heidelberg, Germany.

....to every dimension of our MUCCMAS framework: 1. A Methodology and Modeling Technique for Systems of BDI Agents (MMTS) Kinny et al., 1996] 2. Agent Oriented Design of Soccer Robot Team (Cassiopeia) Collinot Drogoul, 1996] 3. Agent Oriented Methodology for Enterprise modeling (AOMEM) [Kendall et al., 1996] ; 4. An Agent Oriented Methodology: High Level and Intermediate Models (HLIM) Ealmmari Lalonde, 1999] 5. Analysis and Design of Multiagent Systems Using MAS CommonKADS [Iglesias et al.,1997] 6. GAIA [Wooldridge et al., 2000] 7. Multi Agent Scenario Based Method (MASB) Moulin et al., ....

Kendall, E.A., Malkoun, M.T., and Jiang, C. A Methodology for Developing Agentbased Systems for Enterprise Integration, in D. Luckose and C. Zhang, editors, Proceedings of the First Australian Workshop on DAI, Lecture Notes on Artificial Intelligence, Springer-Verlag :Heidelberg, Germany, 1996.

.... 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 have been suggested to cover limits of the past system development methodologies [4, 12, 15, 16, 24] These methodologies have been extended based on the ....

....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 have been suggested to cover limits of the past system development methodologies [4, 12, 15, 16, 24]. These methodologies have been extended based on the past development methodologies such as object oriented methodologies, knowledge engineering methodologies [12] and enterprise integration methodologies [16] They, however, have own special purpose notations and techniques. So, these ....

[Article contains additional citation context not shown here]

Kendall, E. A., M. Malkoun, and C. H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", Modelling and Methodologies for Enterprise Integration, Chapman and Hall, P. Bernus and L. Nemes, Editors, 1996.

....26.895 MEMO (Mediating and Monitoring Electronic Commerce) Copyright c # 2001 IEEE. Published in the Proceedings of the Hawai i International Conference On System Sciences, January 3 6, 2001, Maui, Hawaii. purpose of these approaches is to prescribe the behavior of actors in the enterprise [9]. The two approaches are merged within enterprise modeling tools like ARIS [12] The models produced by ARIS are used within ERP systems like SAP R 3 1 .ARIScovers organization structure, informational entities, business processes (control aspect) and business functions. However, in addition ....

E. Kendall, M. Malkoun, and C. Jiang. A methodology for developing agent based systems for enterprose integration. In Proceedings IFIG Working Conference on Architectures for Enterprise Integration, November 1995, Queensland, Australia, 1995.

....automated manufacturing system must understand how to balance local needs against system needs. Two examples of previous work in this domain are the ADEPT multi agent architecture (Jennings et al. 1996; Jennings et al. 1998a) and Kendall s work on agent based systems for enterprise integration (Kendall et al. 1996). ADEPT uses a hybrid hierarchical flat organizational structure to support the encapsulation and distribution of tasks among agents and currently focuses on business process management w.r.t collecting and publishing relevant information for a given task. Kendall s work similarly defines an agent ....

Kendall, E. A., Malkoun, M., and Jiang, C. H. 1996. A Methodology for Developing Agent Based Systems for Enterprise Integration. In Modelling and Methodologies for Enterprise Integration, Bernus, P. and Nemes, L., Eds.: Chapman and Hall.

....in a systematic way models at one level of abstraction into models at the next lower level. 1.0 Introduction The agent paradigm represents a significant shift in approach to the development of complex software systems. The need to model and understand agent system complexity is well recognized [11][12] 15] 20] However, a comprehensive method for designing agent systems is lacking. There is little that has been done in the area of analysis and design of multi agent systems. The current modelling techniques are too complex and are often modifications of object oriented techniques without ....

....is little that has been done in the area of analysis and design of multi agent systems. The current modelling techniques are too complex and are often modifications of object oriented techniques without taking into considerations the first class attributes of multi agent systems. Kendall et al. [11] model agent systems using workflow models and Kinny et al. 12] use extentions of objectoriented techniques. Other techniques in the agent community, such as COOL [1] and Shoham s AOP [16] represent agents formally with logic, with no visual representation. This is important since visual ....

E. Kendall, A Methodology for Developing Agent Based Systems for Enterprise Integration, IFIP Working Conference of TC5 Special Interest Group on Architectures for Enterprise Integration, Queensland, Australia, November 1995. 17

....in ADT by defining its requirements and mapping them onto the necessary agents and resources. A traditional process (Unified Method [23] is used to define the application in terms of the agent framework requirements and map them into an implementation. 6. 1 Agent Mapping Details Others [19,20] have been working on the problem of agent oriented programming of large complex systems. Our work supports their ideas and extends them. The system uses basic object techniques to discover requirements as in [23] but the large coarse grained nature of agents requires that functional techniques ....

....candidate agents. Briefly, the process steps are: Capture application requirements in use cases. Analyze the use cases to find actors, and control objects. Actors are candidates to become functional agents. Control objects are candidates to become scripts within the functional agents [23,19,3]. Produce an entity relationship diagram for the system. An added twist is that the data is also analyzed from the point of view of which functional agent would have responsibility for it [19,20] 6. Process . Analyze use cases to find the resources necessary to carry out the required ....

[Article contains additional citation context not shown here]

KENDALL, E.,A Methodology for Developing Agent Based Systems for Enterprise Integration, http://www.cse.rmit.edu.au/~rdesk/.

....community, there is a big gap between models at the BDI UCM level of abstraction and popular software design notations. Referring back to terminology used in Figure 1, software design notations express how in a detailed way, leaving what to emerge from the details. For example, Kendall [17] models agent systems using object oriented style diagrams that require commitment to agent centric details (e.g. pairwise interactions via messages, pairwise inheritance relationships) There are many tools in the object oriented community that support modeling of systems at this level of detail ....

....in the object oriented community that support modeling of systems at this level of detail (for example, 4] 21] In the agent community, the Clearlake tool [15] specifically supports design of agent systems at a similar level of detail. Workflow models (e.g. as discussed and applied by Kendall [17]) while less detailed than the design models just mentioned, are more detailed than UCMs because intercomponent workflows must be defined. None of these models provides an easy means of describing agent system self modification. When we depart from the world of low level software design models ....

E. Kendall, A Methodology for Developing Agent Based Systems for Enterprise Integration, IFIP Working Conference of TC5 Special Interest Group on Architectures for Enterprise Integration, Queensland, Australia, November 1995.

....a cooperation model (our coordination model) She proposes a very interesting extension to the CRC cards and a clear development process. Our graphical notation for modelling interactions seems to be more detailed, and the knowledge modelling is elaborated more in the CommonKADS framework. Kendall [16] proposes another AO methodology based on OO and enterprise modelling techniques. The use case model is very similar to our internal use cases. Coordination and knowledge modelling are not so well developed and the process development is not very clear. MASB [20, 21] proposes an AO methodology ....

Elisabeth A. Kendall, Margaret T. Malkoun, and Chong Jiang. A methodology for developing agent based systems for enterprise integration. In D. Luckose and Zhang C., editors, Proceedings of the First Australian Workshop on DAI, Lecture Notes on Artificial Intelligence. Springer-Verlag: Heidelberg, Germany, 1996.

....identifying agents: use cases [21] and classes responsibilities collaborations (CRC) cards [48] 2.2 Aspects not addressed In spite of the similarities between objects and agents, obviously, agents are not simply objects. Thus, object oriented methodologies do not address these different aspects [43, 5, 24]. Firstly, though both objects and agents use message passing to communicate with each other, while message passing for objects is just method invocation, agents distinguish different types of messages and model these messages frequently as speech acts and use complex protocols to negotiate. In ....

....agents have to be defined. 2. 3 Existing solutions In this section the followingagent oriented methodologies are reviewed: Agent Oriented Analysis and Design [5] Agent Modelling Technique for Systems of BDI agents [27] MASB [31, 32] and Agent Oriented Methodology for Enterprise Modelling [24]. Agent Oriented Analysis and Design by Burmeister Burmeister [5] defines three models for analysing an agent system: the agent model. that contains the agents and their internal structure (beliefs, plans, goals, the organisational model, that describes the relationships between agents ....

[Article contains additional citation context not shown here]

Elisabeth A. Kendall, Margaret T. Malkoun, and Chong Jiang. A methodology for developing agent based systems for enterprise integration. In D. Luckose and Zhang C., editors, Proceedings of the First Australian Workshop on DAI, Lecture Notes on Artificial Intelligence. Springer-Verlag: Heidelberg, Germany, 1996.

....case maps) is, to the authors knowledge, the only one that exists for system description at this level of abstraction. In both the agent community and other communities, such as the object oriented community, people use more detailed visual techniques to describe systems. For example, Kendall [13] models agent systems using object oriented style diagrams that require commitment to agent centric details (e.g. pairwise interactions via messages, pairwise inheritance relationships) There are many tools in the object oriented Desktop Caller User Phone Digits Connect View Active Call View ....

....support modelling of systems at this level of detail (for example, 4] 17] In the agent community, the Clearlake tool [11] specifically supports design of agent systems at a similar level of detail. From the perspective of this paper, workflow models (e.g. as discussed and applied by Kendall [13]) are a variation of data flow models. As Kendall points out, there are nuances that make them more useful for agent systems, but the following two basic properties of data flow models remain: they do not provide any easy means of describing one of the central features of agent systems, morphing; ....

E. Kendall, A Methodology for Developing Agent Based Systems for Enterprise Integration, IFIP Working Conference of TC5 Special Interest Group on Architectures for Enterprise Integration, Queensland, Australia, November 1995.

....that give a clearer system picture. The UCM technique is, to the authors knowledge, unique at its level of abstraction. In both the agent community and other communities, such as the object oriented community, people use more detailed visual techniques to describe systems. For example, Kendall [14] models agent systems using object oriented style diagrams that require commitment to agent centric details (e.g. pairwise interactions via messages, pairwise inheritance relationships) There are many tools in the object oriented community that support modelling of systems at this level of ....

....support modelling of systems at this level of detail (for example, 2] 16] In the agent community, the Clearlake tool [13] specifically supports design of agent systems at a similar level of detail. From the perspective of this paper, workflow models (e.g. as discussed and applied by Kendall [14]) are a variation of data flow models. As Kendall points out, there are nuances that make them useful for agent systems, but the following two basic properties of data flow models remain: they do not show continuity of causal paths through a system; and they do not provide any direct or easy means ....

E. Kendall, A Methodology for Developing Agent Based Systems for Enterprise Integration, IFIP Working Conference of TC5 Special Interest Group on Architectures for Enterprise Integration, Queensland, Australia, November 1995.

....on the pro blem . Having reviewed the available literature, we determined that an agent based information gathering system can potentially solve our problem. This is because an agent is autonomous, social, reactive and proactive [26] and it can also model policies and proactive behaviours [12]. In other words, agents provide high level communication and interaction, which can perceive the situation of the environment and respond appropriately. Agents are different from objects, which are static and cannot change with the environment. For example, to gather information, an agent will ....

Kendall, E.A., Malkoun, M. and Jiang C.: A Methodology for Developing Agent Based Systems for Enterprise Integration. EI'95, IFIP TC5 SIG Working Conference on Modeling and Methodologies for Enterprise Integration. Heron Island, Queensland, Australia, (1995).

No context found.

Kendall, E.A., M.T. Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI '95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, 1995.

No context found.

Kendall, E. A., M. Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI'95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, November, 1995a.

No context found.

Kendall, E. A., M. Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI'95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, November, 1995.

No context found.

Kendall, E.A., M.T. Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI '95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, 1995.

.... are represented on the team, and the agents work together, negotiating with each other to develop a sound, concurrently engineered product. 2. 0 CONTEXT All of the Layered Agent patterns presented in this paper share the same context that is based upon the following model of agent behavior [13]. Strong agents reason about their models of the world and themselves to select a capability or plan that could achieve their stated goal(s) A plan from the capabilities library is instantiated by the interpreter when a triggering event occurs, and an instantiated plan is an intention. An ....

....or decentralized management. Strong agent collaboration across disciplines often requires the use of ontologies [20] so that cross disciplinary semantics can be exchanged. Kendall and Malkoun, The Layered Agent Patterns 2 These aspects or components of agent behavior are summarized in Figure 1 [13]. The agent s reasoning is within its declarative knowledge or models, interpreter, and capabilities library. The agent s knowledge is affected by sensors that monitor external objects. A capability is chosen by the interpreter and manifested as an intention; three sample intentions are shown. One ....

Kendall, E.A., M.T. Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI '95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, 1995.

No context found.

Kendall, E. A., M. Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI'95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, November, 1995a.

....the implementation language because of its support for platform independence, concurrency, and mobility. 1. INTRODUCTION Agents appear in a wide range of applications, including personalized user interfaces, electronic commerce, enterprise integration, manufacturing, and business process support[3, 8, 11, 22]. However, all agent development to date has been home grown [3] and done from scratch, independently, by each development team. This has led to the following problems [3] Lack of an agreed definition: Agents built by different teams have different capabilities. Duplication of effort: ....

....interact and cooperate with each other. However, if development efforts are not coordinated, the resulting agents are not compatible with one another. This chapter describes the product of several years of research, development, and implementation in agent systems that has been carried out at RMIT [11 14]. The effort has concentrated on producing a methodology and platform for developing robust and maintainable agent systems through object oriented software engineering. During framework development, the primary invariants and abstractions of agent based systems were identified and analysed. ....

Kendall, E.A., M.T. Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI '95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, 1995.

No context found.

Kendall, E.A., M.T.Malkoun, and C.H. Jiang, "A Methodology for Developing Agent Based Systems for Enterprise Integration", EI'95, IFIP TC5 SIG Working Conference on Models and Methodologies for Enterprise Integration, Heron Island, Australia, 1995.

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