The Tropos Software Engineering Methodology

The agent-oriented software engineering methodology Tropos offers a structured development process for the development of socio-technical systems. Such systems explicitly recognise the interplay between social actors (humans and organisations) and technical systems (software). Tropos adopts the state-of-the-art i* requirements modelling language throughout the development cycle, giving special attention to the early phases of domain and requirements analysis. The system is modelled in terms of the goals of the involved actors and their social interdependencies, allowing for a seamless transition from the requirements to the design and potentially to an agent-oriented implementation. Tropos prescribes a limited set of domain-independent models, activities and artefacts, which can be complement with domain- and application-specific ones.

[1]  John Mylopoulos,et al.  High variability design for software agents: Extending Tropos , 2007, TAAS.

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

[3]  Anna Perini,et al.  Empirical Evaluation of Tropos4AS Modelling , 2011, iStar.

[4]  John Mylopoulos,et al.  Modeling security requirements through ownership, permission and delegation , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[5]  Anna Perini,et al.  Operational semantics of goal models in adaptive agents , 2009, AAMAS.

[6]  Tsvi Kuflik,et al.  An empirical study of requirements model understanding: Use Case vs. Tropos models , 2010, SAC '10.

[7]  John Mylopoulos,et al.  A design framework for generating BDI-agents from goal models , 2007, AAMAS '07.

[8]  Marco Pistore,et al.  Model checking early requirements specifications in Tropos , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

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

[10]  Lin Padgham,et al.  Agent-Oriented Software Engineering VIII, 8th International Workshop, AOSE 2007, Honolulu, HI, USA, May 14, 2007, Revised Selected Papers , 2008, AOSE.

[11]  Volha Bryl,et al.  Evaluating procedural alternatives: a case study in e-voting , 2009, Electron. Gov. an Int. J..

[12]  Daniel Moldt,et al.  Goal Representation for BDI Agent Systems , 2004, PROMAS.

[13]  Winfried Lamersdorf,et al.  Jadex: A BDI Reasoning Engine , 2005, Multi-Agent Programming.

[14]  John Mylopoulos,et al.  The Tropos Metamodel and its Use , 2005, Informatica.

[15]  Eric Yu,et al.  Modeling Strategic Relationships for Process Reengineering , 1995, Social Modeling for Requirements Engineering.

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

[17]  Anna Perini,et al.  Agent-oriented visual modeling and model validation for engineering distributed systems , 2005, Comput. Syst. Sci. Eng..

[18]  John Mylopoulos,et al.  Goal-driven risk assessment in requirements engineering , 2011, Requirements Engineering.

[19]  Anna Perini,et al.  Goal-oriented testing for MASs , 2010, Int. J. Agent Oriented Softw. Eng..

[20]  Anna Perini,et al.  Automated Mapping from Goal Models to Self-Adaptive Systems , 2008, 2008 23rd IEEE/ACM International Conference on Automated Software Engineering.

[21]  Anna Perini,et al.  Tool-Supported Development with Tropos: The Conference Management System Case Study , 2007, AOSE.

[22]  Agostino Poggi,et al.  Jade - a fipa-compliant agent framework , 1999 .

[23]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[24]  John Mylopoulos,et al.  Designing Cooperative IS: Exploring and Evaluating Alternatives , 2006, OTM Conferences.

[25]  John Mylopoulos,et al.  A Goal-Based Organizational Perspective on Multi-agent Architectures , 2001, ATAL.