Integration of Aspects with i* Models

The i* framework has been widely adopted for agent-oriented modeling, as it offers a notation that provides a description in terms of dependency relationships among agents. However, the resulting models may be large and complex, with scattered concerns within the same, or among several models. These crosscutting concerns are not handled explicitly in i* models, affecting several other elements in the same model. In this paper we investigate if the Early Aspects, as promoted by the Aspect-Oriented Software Development community, can help to deal with the complexity which may arise when i* is used to develop large multi-agent systems. To achieve this we identify crosscutting concerns, keeping them in separate models. The consequence is a reduction in complexity and size of the original model. Composition rules are defined simultaneously, to keep a record of these modularized crosscutting elements. Thus, these rules work as transformations in model-driven engineering allowing us to recover the original, more refined model.

[1]  Ivar Jacobson,et al.  Aspect-oriented software development with use cases , 2005, Addison Wesley object technology series.

[2]  João Araújo,et al.  aspect- oriented pr ogramming , 2006 .

[3]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[4]  Satoshi Matsuoka,et al.  ECOOP'97 — Object-Oriented Programming , 1997, Lecture Notes in Computer Science.

[5]  John Mylopoulos,et al.  Tropos: A Requirements-Driven Methodology for Agent-Oriented Software , 2005 .

[6]  Jaelson Brelaz de Castro,et al.  Deriving use cases from organizational modeling , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[7]  João Araújo,et al.  Multi-dimensional separation of concerns in requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[8]  João Araújo,et al.  Modularisation and composition of aspectual requirements , 2003, AOSD '03.

[9]  Carlos José Pereira de Lucena,et al.  Integrating scenarios, i*, and AspectT in the context of multi-agent systems , 2006, CASCON.

[10]  João Araújo,et al.  Aspect-Oriented Requirements with UML , 2002 .

[11]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

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

[13]  Eric S. K. Yu,et al.  Agent-Oriented Modelling: Software versus the World , 2001, AOSE.

[14]  Elisa Baniassad,et al.  Aspect-Oriented Analysis and Design , 2005 .

[15]  Hans-Arno Jacobsen,et al.  Linking goals to aspects , 2005 .

[16]  Yijun Yu,et al.  From goals to aspects: discovering aspects from requirements goal models , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[17]  K. G. van den Berg,et al.  A Conceptual Formalization of Crosscutting in AOSD , 2005 .

[18]  Michael Wooldridge,et al.  Agent-Oriented Software Engineering II , 2002, Lecture Notes in Computer Science.

[19]  João Araújo,et al.  Using Aspects to Simplify iModels , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[20]  Gregor Kiczales,et al.  Aspect-oriented programming , 1996, CSUR.

[21]  Siobhán Clarke,et al.  Aspect-oriented analysis and design - the theme approach , 2005, Addison Wesley object technology series.

[22]  Jean-Marc Jézéquel,et al.  ≪UML≫ 2002 — The Unified Modeling Language , 2002, Lecture Notes in Computer Science.

[23]  Ana Moreira,et al.  Integrating the NFR framework in a RE model , 2004 .