Understanding Agent-Oriented Software Engineering methodologies

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...

Full description

Saved in:
Bibliographic Details
Published in:Knowledge engineering review 2015-09, Vol.30 (4), p.375-393
Main Authors: Gómez-Sanz, Jorge J., Fuentes-Fernández, Rubén
Format: Article
Language:English
Subjects:
Agents (artificial intelligence)
Communities
Computer programs
Industrial development
Knowledge engineering
Life cycles
Methods
Phases
Software
Software development
Software engineering
Software reliability
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary: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.
ISSN:0269-8889
1469-8005
DOI:10.1017/S0269888915000053