7 th International Workshop on Aspect-Oriented Modeling October 2, 2005 Half Moon Resort, Jamaica

Introduction to Participants Authors  Benoit Baudry  Stephan Bleicher  Jean-Paul Bodeveix  Colin Campbell  Vasian Cepa  Hassan Charaf  Siobhán Clarke  Thomas Cottenier  Steven A. Demurjian  Tzilla Elrad  Ricardo Ferreira  Franck Fleurey  Mamoun Filali  Robert France  Sudipto Ghosh International Representation: Argentina, France, Germany, Hungary, Portugal, Ireland, and USA  Wolfgang Grieskamp  Iris Groher  Andrew Jackson  Nicolas Kicillof  Sven Kloppenburg  László Lengyel  Tihamér Levendovszky  Mark Mahoney  Laurent Michel  Ana Moreira  Odile Nasr  Jaime Pavlich-Mariscal  Miloud Rached  Raghu Reddy  Christa Schwanninger  Aswin Van Den Berg

Introduction to Participants Program Committee:  Mehmet Aksit  Elisa Baniassad  Jean Bezivin  Siobhán Clarke  Sudipto Ghosh  Robert France  Stefan Hanenberg  Shmuel Katz  Raghu Reddy  Martin Robillard  Christa Schwanninger Organizing Committee:  Omar Aldawud  Tzilla Elrad  Jeff Gray  Mohamed Kandé  Jörg Kienzle  Dominik Stein International Representation: Canada, China, Germany, Ireland, Israel, Netherlands, Portugal, Switzerland, and USA

Last Workshop at UML 2004 (1) Reasons for Aspect-Oriented Modeling: Express crosscutting structures and behavior at a higher level of abstraction than aspect- oriented code Also:  Manage requirements  Enables modeling of business rules  Facilitates model evolution and maintenance  Helps to resolve conflicts in software models  Allows to express reusable functionality

Last Workshop at UML 2004 (2) Aspect-Orientation and UML  Are existing UML model elements capable of expression AO concepts?  We looked at classes / components / fragments / templates / packages Similar  Aspects are first-class entities  Instantiable classifiers  Encapsulate structural and behavioral properties Different  Provide introspection / intercession capabilities  Can define extrinsic properties of other elements  Break encapsulation of other elements

Last Workshop at UML 2004 (3) Aspect-Oriented Modeling and Terminology  Some thought that it would be beneficial to define an aspect- oriented vocabulary  "aspect“ Something now modular that otherwise crosscuts (vs. "concern", "view")  "join point“ Those points at which models can be woven together (too AspectJ)  "weaving“ (vs. merging, composition)  Final conclusion: too early Aspect-Oriented Modeling and the Software Development Process  Aspects differ depending on the development stage you're in  Aspects appear (and disappear!) at different development stages

Last Workshop at UML 2004 (4) Aspect-Oriented Modeling and Weaving  Weaving at model level more powerful than code weaving  Parallels to model transformation (MDA) -> horizontal transformation  When should weaving happen?  Symmetric vs. asymmetric AOM Questions for future workshop:  What are the reasons for using AOM at each software development phase?  What lessons can be learnt from other areas? OO, model composition and transformation, reflection?  How can we depict aspect-oriented introspection and intercession capabilities?

Let’s Introduce Ourselves Your name and affiliation Research interests Briefly  Any position you would like to state  Your goals in attending this workshop  Questions to be discussed  Where (with respect to the software development phases) do you want to use AOM?

Workshop Schedule – Session 1 TimeEvent 8:30am- 9:00am General Introduction and Overview of Workshop Goals 9:00am- 9:10am Benoit Baudry, Franck Fleurey, Robert France, Raghu Reddy Exploring the Relationship between Model Composition and Model Transformation 9:10am- 9:20am Wolfgang Grieskamp, Nicolas Kicillof, Colin Campbell Behavioral Composition in Symbolic Domains 9:20am- 9:30am Mark Mahoney, Tzilla Elrad Weaving Crosscutting Concerns into Live Sequence Charts Using the Play Engine 9:30am- 9:40am Jaime Pavlich-Mariscal, Laurent Michel, Steven Demurjian Role Slices and Runtime Permissions: Improving an AOP-based Access Control Schema 9:40am- 9:50am Miloud Rached, Jean-Paul Bodeveix, Mamoun Filfali, Odile Nasr Real Time Aspects: Specification and Composition in B 9:50am- 10:00am László Lengyel, Tihamér Levendovszky, Hassan Charaf Eliminating Crosscutting Constraints from Visual Model Transformation Rules

Workshop Schedule – Session 2 TimeEvent 10:30am- 10:50am Thomas Cottenier, Aswin Van Den Berg, Tzilla Elrad Modeling Aspect-Oriented Compositions 10:50am- 11:10am Ricardo Ferreira, Ricardo Raminhos, Ana Moreira Metadata Driven Aspect Specification 11:10am- 11:30am Raghu Reddy, Robert France, Sudipto Ghosh, Franck Fleurey, Benoit Baudry Model Composition - A Signature-Based Approach 11:30am 11:50am Iris Groher, Stephan Bleicher, Christa Schwanninger Model-Driven Development for Pluggable Collaborations 11:50am- 12:10pm Andrew Jackson, Siobhan Clarke Towards a Generic Aspect Oriented Design Process 12:10pm- 12:30pm Working Group Formation (3 groups) 12:30pm- 2:00pm LUNCH

Workshop Schedule - Discussion Groups 2:00pm-3:30pm Discussion Session I 3:30pm-4:00pm Break 4:00pm-5:00pm Discussion Session 2 5:00pm-5:45pm Working Group Summaries 5:45pm-6:00pm Group Photos

Breakout Discussion Groups For 3.5 hours, 3 groups discuss focused issues related to the workshop and report back to all participants The size of each group should be similar To reach consensus on the discussion topic areas:  Each workshop participant will suggest several issues to be discussed and write them on post-it notes “Is model weaving just a notational convention, or is tool support essential?” “Is a UML profile sufficient for modeling aspects, or is something additional needed?”  Related issues will be grouped together Each group should have a scribe and presenter (perhaps the same person) Try to stay focused and don’t get sidetracked on peripheral discussions (e.g., spending an hour defining the meaning of a specific word)