AOP has matured to become Aspect Oriented Software Development (AOSD) that means the community recognizes the importance of applying aspect orientation to all phases of software development life cycle. Once an initial decomposition of the problem domain identifies software components and the corresponding aspectual properties that cut through these components we would like to be able to express this initial decomposition and carry it to the next life cycle phase. For this refinement process to be effective it must preserve the initial semantics. In this Position paper we propose an initial discussion on UML profile for AO modeling, which we believe will set the stage for AOSD modeling and hence move us towards a truly aspect oriented software systems. We also initiate the discussions regard modeling the orthogonal concerns in the aspectoriented software system, where loosely coupled concerns in different dimensions can be easily modeled and reasoned about in isolation of the core components and aspectual components.
[1]
Jean-Marc Jézéquel,et al.
Aspect-oriented design with the UML
,
2000,
ICSE 2000.
[2]
Cristina V. Lopes,et al.
Aspect-oriented programming
,
1999,
ECOOP Workshops.
[3]
Yoshikazu Yamamoto,et al.
Extending UML with Aspects: Aspect Support in the Design Phase
,
1999,
ECOOP Workshops.
[4]
David Harel,et al.
Statecharts: A Visual Formalism for Complex Systems
,
1987,
Sci. Comput. Program..
[5]
Gregor Kiczales,et al.
Aspect-oriented programming
,
2001,
ESEC/FSE-9.
[6]
Tzilla Elrad,et al.
Building Reusable Concurrent Software Systems
,
2000,
PDPTA.
[7]
David Harel,et al.
From Play-In Scenarios to Code: An Achievable Dream
,
2000,
Computer.
[8]
Siobhán Clarke,et al.
Separating Concerns Throughout the Development Lifecycle
,
1999,
ECOOP Workshops.
[9]
William G. Griswold,et al.
An Overview of AspectJ
,
2001,
ECOOP.
[10]
Scott Ambler.
Persistence modeling in the UML
,
2000
.