Post on 23-Jan-2016
description
transcript
Towards an Integrated Aspect-Oriented Modeling Approach for Software
Architecture Design
Ivan KrechetovBedir TekinerdoganAlessandro GarciaChristina ChavezUirá Kulesza
Software Architecture
– structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships among them.
Early aspects
Inherent crosscutting on the code levelCrosscutting architectural concerns, f.e.
– Scalability– Distribution– Security and privacy
The goal is to provide the means for:
Dealing with architecture complexity– Modelling in aspect-oriented fashion– Abstraction– Facilitate architectural concerns identification and
separation
Communicating the aspect-oriented architecture
Solution – integrate the best existing AO architecture modelling practices
1. Classify the required expressive elements2. Choose the “source” modelling approaches3. Decompose each source approach by the
expressive elements classification4. Having a criteria, choose a single element
from each class of source elements5. Adapt the selected elements to match
together
Expressive elements
Aspect Component Point-cut Advice Static and dynamic crosscutting Aspect-component relation Aspect-aspect relation
Source approaches
PCS Framework AOGA TranSAT CAM of DAOP-ADL
Decomposition
Guidelines for selecting the elements
1. General-purpose
2. Complete, distinctive with element classes
3. Implementation language-independent
4. Minimal
Selection
Case study – CVS
Case study – CVS
Result
Analysis of the existing AO architecture design techniques.
Start point for elaborating a general-purpose AO architecture design approach.
Questions, further work
Components - aspects symmetry Architectural views Fitting into the design process
– Connection with requirements analysis– Architectural concerns identification– Refinement of the design at the lower levels
Real world case study