|
Early aspects
are crosscutting concerns that exist in
the early life cycle phases of software development, including the
requirements analysis, domain analysis and architecture design activities.
Whereas conventional aspect-oriented software development approaches are
mainly concerned with identifying aspects at the programming level (thus
leaving the identification and treatment of aspects to implementers), early
aspects work focuses on the impact of crosscutting concerns at the early
phases of the software development. Identifying and managing early aspects
across phases can:
-
help ensure
that cross-cutting concerns evident in a system’s problem domain or
solution space are captured as aspects in the implementation.
-
increase
consistency of requirements and architecture with each other and with
implementation;
-
provide
a way for people with system-wide responsibility and scope (such as
architects and domain experts) to identify aspects
-
provide
rationale and traceability for aspects across lifecycle activities;
This is the ninth Early Aspects workshop,
and the first at ICSE. (Others have been held at AOSD, OOPSLA, and SPLC.)
The goal of the workshop series is to articulate, develop, and codify best
practices for working with aspects beyond just the implementation phase.
_______________________________________________________________________________________________________
This website is maintained by: Bedir Tekinerdogan
| |
