Towards a Common Reference Architecture for AspectOriented Modeling A' Schauerhuber, W' Schwinger, E

1
Towards a Common Reference Architecture for
Aspect-Oriented ModelingA. Schauerhuber, W.
Schwinger, E. Kapsammer, W. Retschitzegger, M.
Wimmer

• 8th Workshop on Aspect Oriented Modeling
  (AOSD06), Bonn, Germany
• Tuesday, March 21, 2006

Andrea Schauerhuber Womens Postgraduate College
for Internet Technologies Institute of Software
Technology and Interactive Systems Vienna
University of Technology http//wit.tuwien.ac.at
2
Motivation

• Aspect-orientation (AO) stretches over all
  development phases
• No common understanding of aspect-oriented
  concepts
• Situation particularly cumbersome for AO
  beginners
• Application to specific software development
  domains difficult

3
Methodology Related Work

• Reference Architecture developed
• top-down
• AOSD Ontology
• van den Berg et al., 2005, European NoE on AOSD
• Aspect Model
• Chavez et al., 2004
• Criteria used in evaluations of AOP and AOM
  approaches, e.g.,
• Chitchyan et al., 2005, European NoE on AOSD
• Stefan Hanenberg, 2005
• bottom-up
• Evaluation of several existing AOM approaches,
  e.g.,
• Theme/UML, Clarke et al., 2005
• AODM, Stein et al., 2002

4
Our Common Reference Architecture
General decomposition into concerns and their
interrelationships
ConcernDecomposition
Concepts to describe how an aspect adapts a
concern
import
import
AdaptationSubject
AdaptationKind
Concepts for identifying where to introduce an
aspects adaptation
import
import
Language underlying the specification of base and
aspect
Language
5
Our Common Reference Architecture
ConcernDecomposition
import
import
AdaptationSubject
AdaptationKind
import
import
Language
6
Our Common Reference Architecture
ConcernDecomposition
import
import
AdaptationSubject
AdaptationKind
import
import
Language
7
Our Common Reference Architecture
ConcernDecomposition
import
import
AdaptationSubject
AdaptationKind
import
import
Language
8
Our Common Reference Architecture
ConcernDecomposition
import
import
AdaptationSubject
AdaptationKind
import
import
Language
9
Our Common Reference Architecture
ConcernDecomposition
import
import
AdaptationSubject
AdaptationKind
import
import
Language
10
Outlook

• Open Issues
• How to describe aspect refinement policies?
• How to specify adaptation effects?
• How to specify join point kinds more explicitly?
• How to apply multiple languages?
• Future Work
• Mapping to AOM AOP approaches
• Developing an evaluation framework for AOM
  approaches
• Applying Aspect-Orientation to the Model-Driven
  Development of Ubiquitous Web Applications1

1A. Schauerhuber, aspectUWA Applying
Aspect-Orientation to the Model-Driven
Development of Ubiquitous Web Applications,
Student Extravaganza Spring School, AOSD'06,
Bonn, Germany, March 19, 2006.
11
References

• C. Chavez and C. Lucena. A Theory of Aspects for
  Aspect-Oriented Software Development. In Proc. of
  the 7th Brazilian Symposium on Software
  Engineering, 2003.
• R. Chitchyan, A. Rashid, P. Sawyer, A. Garcia, M.
  Pinto Alarcon, J. Bakker, B. Tekinerdogan, S.
  Clarke, and Andrew Jackson. Survey of
  Aspect-Oriented Analysis and Design Approaches.
  Technical Report AOSD-Europe-ULANC-9,
  AOSD-Europe, May 2005.
• S. Clarke and R. J. Walker. Generic
  Aspect-Oriented Design with Theme/UML. In R.
  Filman, T. Elrad, S. Clarke, and M. Aksit (eds).
  Aspect-Oriented Software Development.
  Addison-Wesley, 425-458, 2005.
• S. Hanenberg. Design Dimensions of
  Aspect-Oriented Systems. PhD Thesis, University
  Duisburg-Essen, 2005.
• D. Stein, S. Hanenberg, and R. Unland. An
  UML-based Aspect-Oriented Design Notation. In
  Proc. of the 1st Int. Conf. on Aspect-Oriented
  Software Development, 2002.
• K. van den Berg, J. M. Conejero, and R.
  Chitchyan. AOSD Ontology 1.0 - Public Ontology of
  Aspect-Orientation. Technical Report
  AOSD-Europe-UT-01, AOSD-Europe, May 2005.