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.
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.
sending position papers: Monday, January 19, 2004
Date of Notification: Monday, February 9, 2004