John Vlissides. Subject-Oriented Design. C++ Report, February 1998. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Extending Java to dynamic object behaviors - Bettini, Capecchi, Venneri (2003) (Correct)
....into single modules. In order to overcome the problems due to the static nature of inheritance, several solutions have been proposed, that we classify into three groups: design patterns [9] extensions of class based languages either with new basic concepts [16] or with new features [21,18,7], solutions inspired by the object based model [13,11,20] In this paper we address the above issue in the speci c context of class based languages, that form the main stream of object oriented programming [1] The proposed solution is a combination of the three approaches listed above. We ....
John Vlissides. Subject-Oriented Design. C++ Report, February 1998.
Progressive Implementation of Aspects - Massoni, Sampaio, Borba (2001) (Correct)
....are based on RUP. In this work we have discussed the aspects ideas mainly on implementation activities, since Pim is an implementation method. However, in our future work 4 we aim at using techniques and language constructs for considering aspects on design activities, as subject oriented design [13]. When compared to RUP, the new process o ers better support to reduce the impact of inevitable requirements changes during development. By following RUPim, functional prototypes are tested and validated continuously, thus most changes will likely occur before implementing the non functional ....
J. Vlissides. Subject-oriented design. C++ Report, February 1998.
Operation-Level Composition: A Case in (Join) Point - Ossher, Tarr (1998) (1 citation) (Correct)
....analyses are inherently exponential, further suggesting the difficulty involved in understanding the effects of statement level composition. One of the significant contributions of object oriented software development was to make changes additive rather than invasive (see, for example, [3]) This is a particularly important property because of the well documented, extremely adverse effects on software systems of invasive changes. The notion of general statement level joins represents invasive software change, violating the additive changes principle. In light of these concerns, we ....
John Vlissides. Subject-Oriented Design. In C++ Report, February 1998.
Extending Java to dynamic object behaviors - Bettini, Capecchi, Venneri (2003) (Correct)
No context found.
John Vlissides. Subject-Oriented Design. C++ Report, February 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC