Early Aspects 2004: 
Aspect-Oriented Requirements Engineering and Architecture Design

Workshop March 22, 2004, Lancaster, UK

Home
Call for Papers
Organising Committee
Program Committee
Workshop Program
Workshop Papers
Related Links

Early Aspects


In conjunction with 3rd International Conference on Aspect-Oriented Software Development 
March 22-26, 2004,
Lancaster, UK


Supported by
BCS RESG


 

Call for papers

Prospective participants are invited to submit a 5-8 pages position paper. Your submission should be send in PDF, PS or Word format to bedir@cs.utwente.nl and apply to the IEEE proceedings format.

All submissions will be reviewed by members of the program committee and the organising committee for quality and relevance. The authors of the accepted papers will be selected to participate in the workshop. Attendance is by having a paper accepted, or by special invitation by the organising committee. Topics of interest for the workshop will include, but will not be limited to:
 

bulletAspect-Oriented Requirements Engineering
bulletHow to identify and model aspects at the requirements level?
bulletHow to integrate and compose aspects with other modelling mechanisms,
such as goals, viewpoints and use cases, and establish trade-offs?
bulletHow to trace requirements level aspects through later development stages
and during re-engineering?
bulletHow to validate aspects identified at the requirements level?
 
bulletAspect-Oriented Domain Engineering
bulletWhat are the criteria for domain aspect decomposition?
bulletHow can we derive aspects from domain knowledge?
bulletHow can we abstract and generalize domain aspects for reuse?
bulletWhat are the composition relations between domain aspects?
bulletHow to represent domain aspects?
 
bulletMapping between aspect-oriented requirements, domain analysis and architecture
bulletShould the mapping be formal or informal?
bulletTo what is a requirements concern mapped onto?
bulletWhat are the language’ features required to support a mapping?
bulletWhat is the benefit ratio of mapping/coding? What are the pros and cons of mapping in the first place?
 
bulletAspect-Oriented Architecture Design
bulletAspect-oriented architecture design
bulletHow to support evolution in the architecture using aspects?
bulletHow to reason about architectures and aspects to know that the architecture is a good one (trade-offs between aspects)?
bulletHow to model the architecture to take aspects into account?
bulletWhen designing an architecture, how and when to identify aspects?
bulletHow to set the scope for a software product line architecture using aspects
bulletAspects in the Model-Driven Architecture approach
 
bulletTool Support and automation for aspect-orientation
bulletWhich tools are there to support aspect-oriented development in the early life cycle?
 
bulletFormalisms and notations for specifying aspects
bulletWhat formalisms can be used at early software development stages?