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, orby special
invitation by the organising
committee.Topics of interest
for the workshop will include, but will not be limited to:
Aspect-Oriented Requirements
Engineering
How to identify and 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?
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?
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
Tool Support and automation for aspect-orientation
Which tools are
there to support aspect-oriented development in the early life
cycle?
Formalisms and
notations for specifying aspects
What formalisms
can be used at early software development stages?
