[aosd-announce] CfP for LATE AOSD07

[david shepherd]

CALL FOR PAPERS
 LATE
 Linking Aspect Technology and Evolution ( Submit to LATE, but not too late )
 
 Held in conjunction with the 6th International Conference on Aspect-Oriented Software Development
 Vancouver, British Columbia, March 12-16, 2007
 
 http://aosd.net/workshops/late/2007/ 
 
 SUBJECT
 Software evolution lies at the heart of the software development process, and suffers from problems such as maintainability, evolvability, understandability, etc. Aspect-oriented software development (AOSD) is an emerging software development paradigm, that tries to achieve better separation of concerns. It is often claimed that this is actually beneficial for the maintainability, evolvability and understandability of the software. This workshop aims to investigate and explore 
 this relationship between software evolution and AOSD. 
 
 In particular, the workshop's objective is to study the impact of AOSD on software evolution on the one hand, and the impact of software evolution on AOSD on  the other hand. The former subject could for example deal with diverse issues such as how using AOSD improves the quality of the software, and thus eases  software evolution, or how existing applications can be evolved into AOSD applications. The latter subject is concerned with the way existing software evolution techniques (such as refactoring, f.e.) are affected by AOSD, i.e. how they should be extended in order to include AOSD concepts. 
 
 Answers to such questions are important, as there are many applications that continue to miss the advantages of AOSD, because appropriate tools and techniques  are not sufficiently mature, and the advantages are not yet entirely clear. The workshop is specifically intended to address these questions, identify other interesting  issues and bring together researchers from academia and people from industry working on applying AOSD techniques to already-existing applications.
 
 TOPICS
 The topics of interest lie in three distinct areas, and include but are not limited to:
     1. aspect mining and concern exploration
      - automated mining techniques such as structural pattern matching, concept analysis, clone detection, change history mining, etc.
          - code navigation tools
          - structural query tools
          - software search tools
          - concern benchmarks (i.e., examples of concerns to locate)
      2. aspect extraction
         - automated techniques such as slicing, refactoring, program transformations, etc.
         - pointcut generation techniques
         - experiences in migration toward AOSD
         - testing/verification implications
         - aspect benchmarks (i.e., examples of code that should be refactored into aspects)
      3. aspect evolution
         - refactoring of AOSD software
         - evolution of pointcuts, fragile pointcut problem
         - metrics to quantify evolution
 
 
 
 
 SUBMISSIONS
 Prospective participants are requested to submit a short paper (max. 5 pages) that describes their ideas, techniques, tools, experiences, etc. in the field of aspect-oriented software evolution. . The papers should be submitted electronically late at prog.vub.ac.be, in PDF (preferred), Postscript or MS Word format. All papers 
 (of reasonable quality and appropriateness) will receive valuable feedback, because we plan for at least two reviewers to give a thorough review. Authors of accepted papers will receive an invitation to attend the workshop and present their work. All accepted papers will be posted at the workshop web site prior to the workshop date, granting all participants the opportunity to read them before the workshop. 
 Additionally, the accepted papers will be included in a TU Eindhoven Technical Report. 
 
 In addition, authors are requested to include a section that specifies how the work presented in their paper provides answers to the following questions (if relevant) in their area of interest:
 1. aspect mining and concern exploration
 - Our technique captures crosscutting concerns by  & and the results of my technique are presented as  &
 - Our technique is fully-automated, semi-automated, or manual
 - Our technique is expected to require:
     - X amount of human effort
     - Y amount of processing time/theoretical runtime
 - Our technique can be assessed and compared with other techniques by :
 - Our technique does/does not identify all code related to a concern because ..
 - Our technique does/does not avoid false positives and negatives because ...
 - The software upon which I validated my technique is suitable as a common benchmark, because ...
 -  &
  2. aspect extraction
     - Our technique generates appropriate pointcuts by ...
     - Our technique extracts advice code by ... 
     - Our technique guarantees behavior preservation by ...
     -  &
 3. aspect evolution
     - Our technique tackles the fragile pointcut problem by ... 
     - Our technique leads to more evolvable aspects by ...
     - Our technique guarantees behavior preservation by ...
     -  &
 
 IMPORTANT DATES
 Workshop: March 12, 2007
 Position papers due: January 26, 2007
 Notification of acceptance: February 2, 2007
 
 ORGANISERS
 Tom Tourwé, Eindhoven University of Technology,  The Netherlands
 Mariano Ceccato,  ITC-irst Centro per la ricerca scientifica e tecnologica, Italy
 Andy Kellens, Vrije Universiteit Brussel, Belgium
 Marius Marin, Delft University of Technology, The Netherlands
 David Shepherd, University of Delaware,  U.S.A.