Transactions on Aspect-Oriented Software Development VII

1. Front Matter

   PDF

2. Crisis Management Systems: A Case Study for Aspect-Oriented Modeling

   • Jörg Kienzle, Nicolas Guelfi, Sadaf Mustafiz

   Pages 1-22

3. Requirements Modeling with the Aspect-oriented User Requirements Notation (AoURN): A Case Study

   • Gunter Mussbacher, Daniel Amyot, João Araújo, Ana Moreira

   Pages 23-68

4. Relating Feature Models to Other Models of a Software Product Line

   • Florian Heidenreich, Pablo Sánchez, João Santos, Steffen Zschaler, Mauricio Alférez, João Araújo et al.

   Pages 69-114

5. Aspect-Oriented Development Using Protocol Modeling

   • Ashley McNeile, Ella Roubtsova

   Pages 115-150

6. Using VCL as an Aspect-Oriented Approach to Requirements Modelling

   • Nuno Amálio, Pierre Kelsen, Qin Ma, Christian Glodt

   Pages 151-199

7. Workflow Design Using Fragment Composition

   • Sébastien Mosser, Mireille Blay-Fornarino, Robert France

   Pages 200-233

8. Modeling the Car Crash Crisis Management System Using HiLA

   • Matthias Hölzl, Alexander Knapp, Gefei Zhang

   Pages 234-271

9. Aspect-Oriented Design with Reusable Aspect Models

   • Jörg Kienzle, Wisam Al Abed, Franck Fleurey, Jean-Marc Jézéquel, Jacques Klein

   Pages 272-320

10. A Graph-Based Aspect Interference Detection Approach for UML-Based Aspect-Oriented Models

    • Selim Ciraci, Wilke Havinga, Mehmet Aksit, Christoph Bockisch, Pim van den Broek

    Pages 321-374

11. Discovery of Stable Abstractions for Aspect-Oriented Composition in the Car Crash Management Domain

    • Dimitri Van Landuyt, Eddy Truyen, Wouter Joosen

    Pages 375-422

12. Back Matter

    PDF

– Those who want to learn about AOM ?nd in this special issue a concise collection of descriptions of solid and mature AOM approaches. They only have to take the time to understand one case study in order to appreciate the sample models shown in all papers. – Those who want to apply AOM for a particular purpose and are looking for the most appropriate AOM technique can use the papers presented in this specialissue to identify the mostpromisingapproach(es).By identifying similarities between their problem and the case study they should be able to determine candidate AOM approaches easily. – Those working on their own AOM approach can readily identify approaches that were able to handle concerns that their own approach is not able to handle elegantly. This stimulates cross-fertilization between approaches and collaborative research. – Thoseengineering researchersthat areworkingon enhancing softwaredev- opment processes can use the example models presented in this special issue to understand the potential bene?ts of using AOM techniques at di?erent phases of the software development life-cycle.

• Unified Modeling Language (UML)
• aspect-oriented programming
• crisis management
• design
• modeling
• requirements engineering
• requirements modelling
• reusable models
• software architecture
• software engineering
• software life cycle

• Department of Computer Science, The Technion, Haifa, Israel

  Shmuel Katz

• Department of Computer Science , Darmstadt University of Technology, Darmstadt, Germany

  Mira Mezini

• School of Computer Science, McGill University , Montreal, Canada

  Jörg Kienzle

Policies and ethics