Aspect-Oriented Software Development has been popularized primarily as an approach to coding since the late 1990’s [9, 10] although put forward as an approach applicable to the larger design-through-codingaspects of development since the early part of that decade [1, 7]. In addressing the need for design representations of the same kind of separation of concerns addressed in coding, a rush to simply represent coding-level artifacts in the design must be avoided, and the issues of difference in intent and difference in expression of various design artifacts must be taken into account. This paper addresses some of the considerations. The following sections discuss the general impact of level-of-design, of packaging, and of aspect attachment, and then review several relevant UML diagrams to discuss the impact of these on how aspect information may best fit into those diagrams.
By: William H. Harrison, Peri L. Tarr, Harold L. Ossher
Published in: RC22409 in 2002
LIMITED DISTRIBUTION NOTICE:
This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.
Questions about this service can be mailed to reports@us.ibm.com .