| Elizabeth Kendall. Aspect-oriented programming for role models. In ECOOP '99 Workshop Proceedings on AspectOriented Programming Proceedings, 1999. |
....5. Related Work Instance level customization dictates the need for instance level aspects. The idea of customizing instances according to their context is not new. The idea of roles and role models [3] 11] 19] is to customize objects to fit their roles, as determined by their context. Kendall in [14][15] showed the implementation of role models based on an earlier version of the AspectJ tutorial [4] Kendall [14] recognizes that aspect instances can serve to selectively extend object instance behavior based on the particular role an object plays in a system, but uses only the limited features ....
....instances according to their context is not new. The idea of roles and role models [3] 11] 19] is to customize objects to fit their roles, as determined by their context. Kendall in [14] 15] showed the implementation of role models based on an earlier version of the AspectJ tutorial [4] Kendall [14] recognizes that aspect instances can serve to selectively extend object instance behavior based on the particular role an object plays in a system, but uses only the limited features of AspectJ (per this , per target) That work does not attempt to generalize, e.g. to the notion that an aspect ....
Kendall, E. A., "Aspect Oriented Programming for Role Models," International Workshop on Aspect Oriented Programming, European Conference on Object Oriented Programming (ECOOP'99), Lisbon, June, 1999
....varying multifarious roles. Role playing objects have to satisfy such necessary properties as visibility, dependency, identity, multiplicity, dynamicity, and abstractivity [1, 2, 3, 4] These properties are described also in [5] in other words. The importance of these properties is emphasized in [5, 6, 7]. We call a role model that satis es these properties an RPCM (Role Paradigm Conformance Model) 2, 3] The existing work on role models shows an evolutionary path towards RPCMs. The rudimentary role models in [8, 9] do not use any message forwarding mechanism such as delegation. The later role ....
....objects [1, 5] The role models in [3, 5] are advanced role models in that they are RPCMs. An RPCM called Typehole model [3] was developed. The model was implemented in the 1 Java programming language. We have investigated the problems related to the RPCMs. Object schizophrenia problem (OSP) [6, 7, 13] has been examined. Object schizophrenia (OS) is a condition of an object characterized by broken identity, broken contracts [14] broken state and broken implementation. This means that identity, state and behavior of what actually belongs to a single object is rather broken and captured in ....
Elizabeth A. Kendall, \Aspect-Oriented Programming For Role Models," in Position paper, Proceedings of the ECOOP'99 Workshop on Aspect-Oriented Programming, pp. 49-55, 1999. 3
....explicitly additional dimensions that constitute the inherent complexity of software. We believe that these works at the implementation level can be broaden to the entire software cycle and lead to aspect oriented design (AOD) The use of UML in the context of AO modeling is already evident in [13], 2] 3] 26] and [3] has proposed to explicit multidimensional concerns for the entire software development cycle. Our work aims at providing an automated tool to support the expression of aspects at the design model level. The provision of meta level interpreter has the added advantage that ....
Elizabeth Kendall. Aspect-oriented programming for role models. In ECOOP '99 Workshop Proceedings on AspectOriented Programming Proceedings, 1999.
No context found.
Elizabeth Kendall. Aspect-oriented programming for role models. In ECOOP '99 Workshop Proceedings on AspectOriented Programming Proceedings, 1999.
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