[aosd-announce] CFP: Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design Workshop
bedir at cs.utwente.nl
Fri Dec 5 04:53:32 EST 2003
CALL FOR PAPERS
Early-Aspects: Aspect-Oriented Requirements Engineering and Architecture
Lancaster, UK, Monday, March 22, 2003.
(affiliated with AOSD conference)
Early aspects are defined as crosscutting concerns in the early life
cycle phases including the requirements analysis, domain analysis and
architecture design phases. Early aspects cannot be localized and
tend to be scattered over multiple early life cycle modules. This
reduces the modularity of the artifacts in the early life cycle which
might consequently lead to serious maintenance problems.
Unfortunately, conventional aspect-oriented software development
approaches have mainly focused on identifying the aspects at the
programming level and less attention has been taken on the impact of
crosscutting concerns at the early phases of the software
development. Obviously, the early software development phases
actually set the early design decisions and have a large impact on
the whole system. Coping with aspects at the early life cycle phases
as such is a primary issue.
This workshop aims to support the cross-fertilization of ideas in
requirements engineering, domain engineering, software architecture
design and aspect-oriented software development in order to identify
the problems and potential solutions of early aspects. It continues
the work started at the first and second workshop on this topic held
in conjunction with AOSD 2002 and AOSD 2003 respectively.
Topics of interest for the workshop will include, but will not be
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
- 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
- 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
- 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 in the Model-Driven Architecture approach
- Tool support and automation for aspect-orientation
- Which tools are there to support aspect-oriented development?
Formalisms and notations for specifying aspects
- What formalisms can be used at early software development stages?
- Bedir Tekinerdogan, University of Twente, The Netherlands (Contact)
- Paul Clements, CMU Software Engineering Institute, US
- Ana Moreira, Universidade Nova de Lisboa, Portugal
- João Araújo, Universidade Nova de Lisboa, Portugal
Deadline for sending position papers: Monday, January 19, 2004
Date of Notification: Monday, February 9, 2004
Submissions should be send in pdf format to bedir at cs.utwente.nl
PLANNED WORKSHOP FORMAT
The workshop will be highly interactive. During the morning session
there will be short presentations. The afternoon will be reserved for
discussions and overall conclusions. The discussions will be
organized as follows: firstly the participants will be allocated to
groups that reflect specific topics. Then, the discussions will be
realized by raising and debating relevant questions. Finally, each
group will present their conclusions. This format has worked well at
the previous versions of this workshop.
Prospective participants are invited to submit a 4-6 pages position
paper. All submissions will be reviewed by members of the program
committee and the organising committee for quality and relevance.
Three or four papers will be chosen to be presented during the
workshop with the aim to foment discussion. Attendance is by having a
paper accepted, or by special invitation.
WORKSHOP PROGRAM COMMITTEE
- Mehmet Aksit, University of Twente, The Netherlands
- Krzysztof Czarnecki, University of Waterloo, US
- Charles Haley, Open University, UK
- Kim Mens,Universite catholique de Louvain, Belgium
- Awais Rashid, Lancaster University, UK
- Stan Sutton, NFA Consulting, USA
The first workshop dedicated to this topic was held in AOSD 2002 and
AOSD 2003 organised by the same organisers of this proposal and some
others (see http://trese.cs.utwente.nl/AOSD-EarlyAspectsWS/ and
http://www.cs.bilkent.edu.tr/AOSD-EarlyAspects/ respectively). Both
workshops were very successful and provided new insight in techniques
for coping with early aspects.
More information about the announce