| Modeling and integrating aspects with UML activity diagrams |
| Full text |
Pdf
(401 KB)
|
Source
|
Symposium on Applied Computing
archive
Proceedings of the 2009 ACM symposium on Applied Computing
table of contents
Honolulu, Hawaii
SESSION: Software engineering track
table of contents
Pages 430-437
Year of Publication: 2009
ISBN:978-1-60558-166-8
|
|
Authors
|
|
Zhanqi Cui
|
Nanjing University, Nanjing, Jiangsu, P.R. China
|
|
Linzhang Wang
|
Nanjing University, Nanjing, Jiangsu, P.R. China
|
|
Xuandong Li
|
Nanjing University, Nanjing, Jiangsu, P.R. China
|
|
Dianxiang Xu
|
North Dakota State University, Fargo, ND
|
|
| Sponsor |
|
| Publisher |
|
| Bibliometrics |
Downloads (6 Weeks): 25, Downloads (12 Months): 106, Citation Count: 0
|
|
|
ABSTRACT
Dealing with crosscutting concerns has been a critical problem in software development processes. Aspect-Oriented Programming (AOP) provides a viable programming-level solution by separating crosscutting concerns from primary concerns. To facilitate handling crosscutting concerns at earlier software development phases, this paper proposes an aspect-oriented modeling and integration approach at the design level. In our approach, primary concerns are depicted with UML activity diagrams as primary models, whereas crosscutting concerns are described with aspectual extended activity diagrams as aspect models. Each aspect model consists of pairs of pointcut and advice model. Aspect models can be integrated into primary models automatically. To this end, a prototype tool called Jasmine-AOI has been implemented as an Eclipse plug-in. With the tool support, we have conducted two case studies, including 15 primary models and 8 aspect models. The case studies demonstrate that our approach can greatly facilitate reasoning about crosscutting concerns when a system is modeled with activity diagrams.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
G. Kiczales, J. Lamping, A. Mendhekar, C. Maeda, C. V. Lopes, J.-M. Loingtier, and J. Irwin. Aspect-Oriented Programming. In ECOOP, pp. 220--242, 1997.
|
| |
2
|
OMG, UML Superstructure v2.1:, http://www.omg.org/technology/documents/formal/uml.htm.
|
| |
3
|
Gregor Kiczales , Erik Hilsdale , Jim Hugunin , Mik Kersten , Jeffrey Palm , William G. Griswold, An Overview of AspectJ, Proceedings of the 15th European Conference on Object-Oriented Programming, p.327-353, June 18-22, 2001
|
| |
4
|
R. Reddy, A. Solberg, R. France, and S. Ghosh. Composing Sequence Model Using Tags. In MoDELS workshop on Aspect-Oriented Modeling, 2006.
|
 |
5
|
|
 |
6
|
|
 |
7
|
|
| |
8
|
R. B. France, I. Ray, G. Georg, and S. Ghosh. Aspect-Oriented Approach to Early Design Modelling. IEE Proceedings - Software, 151(4): 173--186, 2004.
|
 |
9
|
|
| |
10
|
R. C. Bjork. ATM. http://www.mathcs.gordon.edu/courses/cs211/ATMExample/.
|
| |
11
|
|
| |
12
|
|
| |
13
|
G. Zhang, M. M. Hölzl, and A. Knapp. Enhancing UML State Machines with Aspects. In MoDELS, pp. 529--543, 2007.
|
| |
14
|
Y. R. Reddy, S. Ghosh, R. B. France, G. Straw, J. M. Bieman, N. McEachen, E. Song, and G. Georg. Directives for Composing Aspect-Oriented Design Class Models. T. Aspect-Oriented Software Development I, pp. 75--105, 2006.
|
| |
15
|
|
| |
16
|
J. Whittle, A. Moreira, J. Araújo, P. K. Jayaraman, A. M. Elkhodary, and R. Rabbi. An Expressive Aspect Composition Language for UML State Diagrams. In MoDELS, pp. 514--528, 2007.
|
| |
17
|
J.-M. Jézéquel. Model Driven Design and Aspect Weaving. Journal of Software and Systems Modeling (SoSyM), 7(2): 209--218, May 2008.
|
 |
18
|
|
|