AOSE Methodologies and Comparison of Object Oriented and Agent Oriented Software Testing

In today's world, the complexities in developing software is growing faster. So, the software is failed to produce flexibility, robustness, efficiency and reliability. To satisfy these demands, agent oriented technique is evolved in the software engineering field. The agent oriented model is an alternative for object oriented model because the object orientation is not capable of solving these problems. The agent oriented technology is adapted because it solves the problems related to the social and organization which is not possible by the traditional model. It also provides solutions for real world problems. This is successful by introducing a new paradigm called agent. An agent is autonomous, proactive, responsiveness and sociality. So, it can act individually or it can interact with other agents in MAS (Multi-Agent System) to solve the problems. It can handle complex tasks and also has the ability to perform flexible action in an unpredictable environment. Hence, we need a methodology to implement the agent oriented technology for developing a system. Therefore, the Agent Oriented Software Engineering (AOSE) methodologies are evolved. Even though the AOSE methodologies has many advantages, they are not complete. The Software Development Life Cycle (SDLC) includes phases such as analysis, design, implementation and testing. A methodology is said to be complete only when it covers all the phases of the SDLC. The AOSE methodology does not include the testing phase and so it is not complete. Testing is defined as the process of detecting the errors. As testing is essential, it should be included in the AOSE methodologies. The Object Oriented Software Testing (OOST) is used in the object oriented methodologies, but it cannot be incorporated in the agent oriented methodologies. This is because the object and the agent differs in some categories like agent properties which cannot be adapted by an object. Hence, a new testing technique was introduced to test the agent oriented systems is called as Agent Oriented Software Testing (AOST). It is the extension of OOST in which the objects are replaced by the agents. The individual agent, the communication between the agents and the communication between agent and environment are tested using AOST technique.

[1]  Jianming Zhao,et al.  Engineering Adaptive Multi-Agent Systems with ODAM Methodology , 2007, PRIMA.

[2]  Andrea Omicini,et al.  SODA: Societies and Infrastructures in the Analysis and Design of Agent-Based Systems , 2000, AOSE.

[3]  Lin Liu,et al.  Modelling Trust for System Design Using the i* Strategic Actors Framework , 2000, Trust in Cyber-societies.

[4]  Jörg P. Müller,et al.  Agent UML: A Formalism for Specifying Multiagent Software Systems , 2001, Int. J. Softw. Eng. Knowl. Eng..

[5]  Pankaj Mudholkar,et al.  Software Testing , 2002, Computer.

[6]  Richard F. Paige,et al.  The Single Model Principle , 2002, J. Object Technol..

[7]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[8]  Brian Logan,et al.  Agent programming with priorities and deadlines , 2011, AAMAS.

[9]  Lin Padgham,et al.  Enhancing the Adaptation of BDI Agents Using Learning Techniques , 2009, Int. J. Agent Technol. Syst..

[10]  M. Cossentino.  PASSI : a Process for Specifying and Implementing Multi-Agent Systems Using UML , 2001 .

[11]  Boris A. Galitsky.  Exhaustive simulation of consecutive mental states of human agents , 2013, Knowl. Based Syst..

[12]  Aamer Nadeem,et al.  An Approach to Model Based Testing of Multiagent Systems , 2015, TheScientificWorldJournal.

[13]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[14]  Glenford J. Myers,et al.  Art of Software Testing , 1979 .

[15]  Zina Houhamdi,et al.  Multi-Agent System Testing: A Survey , 2011 .

[16]  Fausto Giunchiglia,et al.  The Tropos Software Development Methodology: Processes, Models and Diagrams , 2002, AOSE.

[17]  James A. Whittaker,et al.  What is software testing? And why is it so hard? , 2000 .

[18]  Scott A. DeLoach,et al.  Lecture Notes in Artificial Intelligence. Springer-Verlag, Berlin, 2001. Developing Multiagent Systems with agentTool , 2022 .

[19]  Uirá Kulesza,et al.  Unit testing in multi-agent systems using mock agents and aspects , 2006, SELMAS '06.

[20]  Leon Sterling,et al.  ROADMAP: extending the gaia methodology for complex open systems , 2002, AAMAS '02.

[21]  John Mylopoulos,et al.  Specifying and analyzing early requirements in Tropos , 2004, Requirements Engineering.

[22]  N. Sivakumar,et al.  Comparing the Testing Approaches of Traditional, Object-Oriented and Agent- Oriented Software System , 2012 .

[23]  Massimo Cossentino,et al.  From Requirements to Code with PASSI Methodology , 2005 .

[24]  Onn Shehory,et al.  Agent-Oriented Software Engineering , 2014, Springer Berlin Heidelberg.

[25]  Jorge J. Gómez-Sanz,et al.  The MESSAGE Methodology for Agent-Oriented Analysis and Design , 2005 .

[26]  Richa Setiya,et al.  Evaluation of Agent Oriented Software Engineering (AOSE) Methodologies-A review , 2012 .

[27]  Michael Winikoff,et al.  Prometheus design tool , 2005, AAMAS '05.

[28]  James Odell,et al.  Objects and Agents Compared , 2002, J. Object Technol..

[29]  Michael Luck,et al.  A Manifesto for Agent Technology: Towards Next Generation Computing , 2004, Autonomous Agents and Multi-Agent Systems.

[30]  P. D. Ratna Raju,et al.  Object Oriented Software Testing , 2011 .

[31]  Nicholas R. Jennings,et al.  The Gaia Methodology for Agent-Oriented Analysis and Design , 2000, Autonomous Agents and Multi-Agent Systems.

[32]  John Mylopoulos,et al.  Goal-oriented requirements analysis and reasoning in the Tropos methodology , 2005, Eng. Appl. Artif. Intell..

[33]  Praveen Ranjan Srivastava,et al.  Extension of Object-Oriented Software Testing Techniques to Agent Oriented Software Testing , 2008, J. Object Technol..

[34]  Michael Winikoff,et al.  Adding debugging support to the Prometheus methodology , 2005, Eng. Appl. Artif. Intell..

[35]  Ron Patton.  Software Testing (2nd Edition) , 2005 .

[36]  Scott A. DeLoach,et al.  Multiagent Systems Engineering , 2001, Int. J. Softw. Eng. Knowl. Eng..

[37]  Jorge J. Gómez-Sanz,et al.  A Survey on Agent-Oriented Oriented Software Engineering Research , 2004 .

[38]  Eric Yu,et al.  Modelling Trust in the i* Strategic Actors Framework , 2000 .

[39]  Michael Luck,et al.  Agent technology: Enabling next generation computing , 2003 .

[40]  Fausto Giunchiglia,et al.  Tropos: An Agent-Oriented Software Development Methodology , 2004, Autonomous Agents and Multi-Agent Systems.

[41]  Michael Winikoff,et al.  Comparing Agent-Oriented Methodologies , 2003, AOIS.

[42]  Michael Winikoff,et al.  The Prometheus Design Tool - A Conference Management System Case Study , 2007, AOSE.

[43]  Mary Jean Harrold,et al.  Testing: a roadmap , 2000, ICSE '00.

[44]  Anna Perini,et al.  eCAT: a tool for automating test cases generation and execution in testing multi-agent systems , 2008, AAMAS.

[45]  Michael Winikoff,et al.  The Prometheus methodology , 2004 .

[46]  Michael Wooldridge,et al.  Agent-Oriented Software Engineering: The State of the Art , 2009, AOSE.

[47]  Massimo Cossentino,et al.  Designing a multi-agent solution for a bookstore with the PASSI methodology , 2002, AOIS@CAiSE.

[48]  Anna Perini,et al.  A Goal-Oriented Software Testing Methodology , 2007, AOSE.