Call for papers

Prospective participants are invited to submit a 2-5-page position paper. All submissions will be reviewed by members of the program committee and the organizing committee for quality and relevance.  Attendance is by having a paper accepted, or by special invitation.  Papers should use IEEE Proceedings format, as described at http://www.computer.org/cspress/instruct.htm, and submitted in PDF format to clements@sei.cmu.edu.   Authors of accepted papers will then be asked to prepare and submit a 3-viewgraph presentation aimed at stimulating workshop discussion and progress.  Details will be sent with acceptance notices.

Topics of interest for the workshop will include, but will not be limited to:

• Aspect-oriented requirements engineering
  • How can we identify aspects at the requirements level?
  • How can we model aspects at the requirements level?
  • What are ways to integrate and compose aspects with other modeling mechanisms, such as goals, viewpoints and use cases, and establish trade-offs?
  • How does one trace requirements aspects through later development stages and during re-engineering?
  • How are aspects identified at the requirements level validated?
     
• Aspect-Oriented domain engineering
  • What are the criteria for domain aspect decomposition?
  • How can we derive aspects from domain knowledge?
  • How can we abstract and generalize domain aspects for reuse?
  • What are the composition relations between domain aspects?
  • How to represent domain aspects?
     
• Aspect-oriented architecture design
  • How can aspects be used to support system quality attributes in the architecture?
  • How can we reason about architectures and aspects to know that the architecture is a good one? 
  • How can we reason about trade-offs among aspects?
  • How can we model the architecture to take aspects into account?
  • When designing an architecture, how and when can we identify aspects?
  • How can we set the scope for a software product line architecture using aspects?
  • How do aspects fit in the Model-Driven Architecture approach?
     
• Mapping between aspects in requirements, domain analysis, and architecture
  • Should the mapping be formal or informal?
  • To what is a requirements concern mapped onto?
  • What language features are required to support a mapping?
  • What are the pros and cons of mapping?
     
• Tool support and automation for aspect-orientation
  • Which tools are there to support aspect-oriented development?
     
• Formalisms and notations for specifying early aspects
  • What formalisms can be used at early software development stages?