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, orby 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
Relationship/contrast/synergy
of early aspects with OO analysis techniques
Modelling of early aspects
Analysis of requirements for
appropriate design patterns and their adaptation to aspect-orientation
Elicitation of aspectual requirements
Composition languages
What are the characteristics of a
composition language for requirements analysis and modelling?
How can concerns be composed at
requirements level?
How can concerns be composed at
architecture design level
Composition semantics of early aspects
Aspect-oriented Architecture
Description Languages
Aspect-Oriented Architecture Design
Aspect-oriented architecture
design
How to support evolution in the
architecture using aspects?
How to reason about architectures
and aspects to know that the architecture is a good one (trade-offs
between aspects)?
How to model the architecture to
take aspects into account?
When designing an architecture,
how and when to identify aspects?
How to set the scope for a
software product line architecture using aspects
Aspects in the Model-Driven
Architecture approach
Aspect-Oriented Requirements
Engineering
How to identify aspects
at the requirements level?
How to model aspects
at the requirements level?
How to integrate
and compose aspects with other modelling mechanisms,
such as goals, viewpoints and use cases, and establish trade-offs?
How to trace
requirements level aspects through later development stages
and during re-engineering?
How to validate
aspects identified at the requirements level?
How to manage requirements change
with aspects?
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?
Mapping between aspect-oriented
requirements, domain analysis and architecture
Should the
mapping be formal or informal?
To what is a
requirements concern mapped onto?
What are the
language’ features required to support a mapping?
What 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
How can traceability be guaranteed
from requirements to design and implementation?
Verification of aspect-oriented
implementations against the initial aspectual requirements and
architecture
Tool Support and automation for aspect-orientation
Which tools are
there to support aspect-oriented development in the early life
cycle?
Are there tools for
object-orientation that can be easily used for aspect-orientation?
Formalisms and
notations for specifying aspects
What formalisms
can be used at early software development stages?
