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

Monday, October 25, 2004, Vancouver, Canada

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

Early Aspects

OOPSLA '04
In conjunction with the OOPSLA conference
October 24-28,2004,
Vancouver, Canada

 

================

Supported by AOSD-Europe: European Network of Excellence on Aspect-Oriented Software Development


 


 

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  (amm@di.fct.unl.pt)  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 organizing committee. Topics of interest for the workshop will include, but will not be limited to:
 

Extending object-oriented techniques with aspects

bullet

Relationship/contrast/synergy of early aspects with OO analysis techniques

bullet

Modelling of early aspects

bullet

Analysis of requirements for appropriate design patterns and their adaptation to aspect-orientation

bullet

Elicitation of aspectual requirements

Composition languages 

bullet

What are the characteristics of a composition language for requirements analysis and modelling?

bullet

How can concerns be composed at requirements level?

bullet

How can concerns be composed at architecture design level

bullet

Composition semantics of early aspects

bullet

Aspect-oriented Architecture Description Languages


Aspect-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

Aspect-Oriented Requirements Engineering

bulletHow to identify aspects at the requirements level?
bulletHow to 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?
bulletHow to manage requirements change with aspects?

Aspect-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?

Mapping 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?
 

Traceability of aspect-oriented requirements to code

bullet How can traceability be guaranteed from requirements to design and implementation?
bulletVerification of aspect-oriented implementations against the initial aspectual requirements and architecture
 
bulletTool Support and automation for aspect-orientation
bulletWhich tools are there to support aspect-oriented development in the early life cycle?
bulletAre there tools for object-orientation that can be easily used for aspect-orientation?
 
bulletFormalisms and notations for specifying aspects
bulletWhat formalisms can be used at early software development stages?