Realizing changes by aspects at the design level

Abstract

The cost of a change is high, but changes are an inevitable part of software development lifecycle, which comes to be recognized under a more general term: software evolution. To mitigate this problem, an approach to aspectoriented change realization has been proposed earlier based on the idea of representing change by aspect. In many cases, software development relies on graphical modeling, mainly UML, and thus a legitimate question is how aspect-oriented change realization could be supported at the modeling level. This paper proposes an approach to achieve this based on Theme, a comprehensive approach to aspect-oriented analysis and design. One of the results of the work reported here is a catalog of change type models for the domain of web applications comprising the models of eleven specification change types and seven implementation change types. Apart from the examples presented in the paper, the approach was successfully applied to a real web mail system. As no dedicated Theme modeling tool is available, a UML profile for both analytical (Theme/Doc) and design part (Theme/UML) of the Theme approach has been designed and implemented in IBM Rational Software Architect.

Preliminary Report on Empirical Study of Repeated Fragments in Internal Documentation

“…Documentation fragments that represent the same documentation phrase usually document the same domain or design property that is shared by the documented program elements [6]. Horie et al [7] likened the documentation phrases to crosscutting concerns from aspect oriented programming (AOP [8]). …”

Language composition using source code annotations

“…In this the reader can find a better correspondence with domain-specific aspect languages (DSAL)[12] that are designed to express crosscutting concerns (aspects[46]) and thus are closely coupled with the base language.…”