Understanding Agent-Oriented Software Engineering methodologies

Abstract

For many years, the progress in agent-oriented development has focused on tools and methods for particular development phases. This has not been enough for the industry to accept agent technology as we expected. Our hypothesis is that the Agent-Oriented Software Engineering (AOSE) community has not recognized the kind of development methods that industry actually demands. We propose to analyze this hypothesis starting with a more precise definition of what an AOSE methodology should be. This definition is the first step for a review of the current progress of an illustrative selection of methodologies, looking for missing elements and future lines of improvement. The result is an account of how well the AOSE community is meeting the software lifecycle needs. It can be advanced that AOSE methodologies are far from providing all the answers industry requires and that effort has grounded mainly in requirements, design, and implementation phases.

Agent-Oriented Methodologies Evaluation Frameworks: A Review

“…The 34 review and evaluation papers, all from 1998 to 2020, are brie°y summarized in the table provided in Appendix A. In some of these papers (such as [30][31][32][33][34]), the focus is on the origin of AOM, the components of these methodologies, the phases of MAS development and the main conceptual models. In another set of these papers, an evaluation framework is proposed for comparison of AOM.…”

“…Not all the AO methodologies cover all phases of SDLC and not even those which cover the same phases name or de¯ne these phases identically. The lack of coverage of all phases of the SDLC by di®erent methodologies might be one of the reasons limiting industrial acceptance of most of the AO methodologies [30,64]. Table 1 shows a brief overview of di®erent phases of SDLC covered by di®erent methodologies discussed in more than one review paper.…”

“…These methodologies di®er mainly based on the technical capabilities and features considered for agents, their communications and interactions, other essential components of the system and phases covered in the methodology. These methodologies use di®erent terms for di®erent phases and essential components and consider different sets of activities in each phase of system development [29,30]. When developers select the methods to be employed, they need to identify which system development life cycle (SDLC) phases are relevant to the analysis goals.…”

Research on Digital Power Grid Information Integration Solution

“…Service Oriented Architecture (SOA) is an application architecture for all functions of digital grid information system, which is precisely defined, invoked, independent service, and can be arranged orderly to construct the application architecture of business process. The typical features of SOA are that it's independent of MATEC Web of Conferences 173, platform, loosely coupled and it has oarse-grained service, good encapsulation and flexibility [17][18]. In a service-oriented architecture, there are mainly three types roles: service requester, service provider and service registration center.…”

Supporting the platform extensibility for the model-driven development of agent systems by the interoperability between domain-specific modeling languages of multi-agent systems

“…5). The methodology described above is currently the dominating MAS DSML engineering approach and also the most preferred way of model-driven agent development in AOSE [4,5,53]. Instead, we can follow the approach introduced in Sect.…”