| G. Gottlob, M. Schrefl, and B. Rock. Extending Object - Oriented Systems with Roles. ACM Trans. Inf. Syst., 14(3):268--296, July 1996. |
....pattern which is very useful for adding responsibilities to individual objects incrementally, recursively, and transparently to their clients. However, the Decorator pattern fundamentally incurs several violations of the identity property and the abstractivity property of roles. Gottlob et al. [29] proposed a way to handle roles in object oriented systems, and demonstrated how practical and useful for object evolution it is to implement roles via two kinds of hierarchies: a class hierarchy and a role hierarchy. A role hierarchy is used to describe how objects from a specific class type ....
Gottlob G, Schrefl M, Rock B. Extending object-oriented systems with roles. ACM Transactions on Information Systems 1996; 14:411--428.
....by expanding the existing pointcut pattern class.method to class. instance set .method. 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 ....
Gottlob, G., Schrefl, M., and Rock, B., "Extending Object Oriented Systems with Roles," ACM Trans on Info. Sys., Vol. 14, No. 3, July, 1996, pp. 268 - 296.
....uses type inference techniques to track accesses to resources[17] Our ideas about models of objects map closely to the object oriented design notion of roles. A role is the part of an object that that ful lls its responsibilities to other objects. There has been work on specifying role models[12] and mechanisms for role based programming[14] Kuncak et al. describe a system for the programmer to specify the roles of objects by their aliasing relationships with other objects, along with a mechanism to statically verify those aliasing constraints[15] 10 7. CONCLUSIONS This paper ....
G. Gottlob, M. Schre , and B. Rock. Extending object-oriented systems with roles. ACM Transactions on Information Systems, 14(3):268-296, 1996.
....control. We have investigated at modeling objects that play dynamically 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 ....
....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 ....
[Article contains additional citation context not shown here]
George Gottlob, Michael Schre , and Brigitte Rock, \Extending Object-Oriented Systems with Roles," ACM Transactions on Information Systems, vol. 14, pp. 268{ 296, July 1996.
....notion of context is of fundamental importance in cognitive psychology, linguistics, and computer science. In computer science, a number of formal or informal definitions of some notion of context have appeared in several areas, such as artificial intelligence [15, 24, 13] software development [31, 12, 34, 35, 36, 19, 20], databases [3, 11, 14, 1, 7, 18, 30] machine learning [25, 44, 23] and knowledge representation [28, 42, 40, 46, 8, 38, 6, 4] See also [26] for a general survey on the subject. However, all these notions of context are very diverse and serve different purposes. In software development the ....
....[28, 42, 40, 46, 8, 38, 6, 4] See also [26] for a general survey on the subject. However, all these notions of context are very diverse and serve different purposes. In software development the notion of context appears in the form of views [3, 11, 14, 33, 1] aspects [31] and roles [12, 34], for dealing with data from different perspectives, or even in the form of workspaces which are used to support cooperative work [19] In machine learning, context is treated as environmental information for concept classification [25, 44, 23] In so called multi bases , context appears as a ....
G. Gottlob, M. Schrefl, and B. R ock. Extending Object - Oriented Systems with Roles. ACM Trans. Inf. Syst., 14(3):268--296, July 1996.
....that uses type inference techniques to track accesses to resources. Our ideas about models of objects map closely to the object oriented design notion of roles. A role is the part of an object that that ful lls its responsibilities to other objects. There has been work on specifying role models [12] and mechanisms for role based programming [14] Kuncak [15] describes a system for the programmer to specify the roles of objects by their aliasing relationships with other objects, along with a mechanism to statically verify those aliasing constraints. 7. CONCLUSIONS 10 This paper proposes a ....
G. Gottlob, M. Schre , and B. Rock. Extending object-oriented systems with roles. ACM Transactions on Information Systems, 14(3):268-296, 1996.
....LAYOM [2] C [23] have done that. Our implementation is carried out for ConceptBase, a database system for managing conceptual information [16] using the metaclass mechanisms of its underlying data model, Telos [27] Metaclasses have been used successfully to implement generic relationships [6, 7, 12, 14, 21]. In particular, we have used Telos metaclasses to formalize materialization [4, 29] They were also used to partially formalize the semantics of a variant of the part relationship [25] The paper is structured as follows. Our part relationship model is described in Section 2. Section 3 presents ....
....16 address those requirements, classes must be treated as objects, which is possible only in systems and languages supporting metaclasses. Metaclasses. The metaclass approach, adopted in this paper, was suggested in [21] as an appropriate mechanism to implement generic relationships (see, e.g. [4, 6, 7, 12, 14]) In particular, a variant of part relationship was implemented in [14] using the metaclass mechanism of the VODAK modeling language (VML) 21] The part relationship is represented by a metaclass PartWholeClass. Two types are associated to the metaclass accounting, respectively, for the classand ....
G. Gottlob, M. Schrefl, and B. Rock. Extending object-oriented systems with roles. ACM Trans. on O#ce Information Systems, 14(3):268--296, 1996.
....to distinguish multiple occurrences in the same role is that each occurrence of the object in a role is associated with a different state (item 10) For example, an employee has one salary and one office address per job. Not in [3,4,53] 5. An object may acquire and abandon roles dynamically [3,29,41,43,49,55]. This is a dynamic property of the role concept that comes close to object migration or dynamic (re)classification [46,69] However, the two are not necessarily the same; for example, Wieringa et al. 75] make an explicit distinction between dynamic classification and role playing. 6. The ....
....in which it is being addressed. Together with item 4, i.e. the possibility of one object playing the same role multiply at the same time, this seems to suggest that each role played by an object should be viewed as a separate instance of the object. 11. Features of an object can be role specific [3,29,43,52,55]. Attributes and behaviour of an object may be overloaded on a by role basis, i.e. different roles may declare the same features, but 87 realize them differently. If an object plays several of these roles simultaneously, it responds according to the role in which it is being addressed. 12. Roles ....
[Article contains additional citation context not shown here]
G. Gottlob, M. Schrefl, B. R6ck, Extending object-oriented systems with roles, ACM Transactions on Information Systems 14 (3) (1996) 268 296.
No context found.
G. Gottlob, M. Schrefl, and B. Rock. Extending Object - Oriented Systems with Roles. ACM Trans. Inf. Syst., 14(3):268--296, July 1996.
No context found.
G. Gottlob, M. Schrefl, and B. Rock, "Extending object-oriented systems with roles," ACM Transactions on Information Systems, vol. 14(3), pp. 268 -- 296, 1996.
No context found.
G. Gottlob, M. Schrefl, B. Rck, "Extending Object-oriented Systems with Roles", ACM Transactions on Information Systems 14 (3), 1996, pp. 268-296.
No context found.
G. Gottlob, M. Schrefl, B. Rck, "Extending Object-oriented Systems with Roles", ACM Transactions on Information Systems 14 (3) (1996) pp. 268-296.
No context found.
G. Gottlob, M. Schrefl, and B. R ock. Extending Object - Oriented Systems with Roles. ACM Transactions on Information Systems, 14(3):268--296, July 1996.
No context found.
G. Gottlob, M. Schrefl, and B. R ock. Extending object-oriented systems with roles. ACM Transactions on Information Systems, 14(3):268--296, 1996.
No context found.
G. Gottlob, M. Schrefl, B. Rock. Extending Object-Oriented Systems With Roles. ACM Transactions on Information Systems, pp. 268-296, 1996.
No context found.
G. Gottlob, M. Schrefl, and B. Rock. Extending ObjectOriented Systems with Roles. ACM Transactions on Information Systems, 14(3):268--296, July 1996.
No context found.
G. Gottlob, M. Schrefl, and B. Rock. Extending object-oriented systems with roles. ACM Trans. on O#ce Information Systems, 14(3):268--296, 1996.
No context found.
G. Gottlob, M. Schrefl, and B. Rock. Extending Object - Oriented Systems with Roles. ACM Trans. Inf. Syst., 14(3):268--296, July 1996.
No context found.
G. Gottlob, M. Schrefl, B. R# oock,Extending object-oriented systems with roles, ACM Trans. Inf. Syst. 14 (3) (1996) 268--296.
No context found.
G. Gottlob, M. Schrefl, and B. Rock. Extending object-oriented systems with roles. ACM Trans. on O#ce Information Systems, 14(3):268--296, 1996.
No context found.
Gottlob..G and al.1996. Extending Object-Oriented Systems with Roles. ACM Transactions on Information Systems (TOIS), page 268-296. 86
No context found.
G. Gottlob, M. Schrefl, and B. Rock. Extending object-oriented systems with roles. ACM Transactions on Information Systems, 14(3):268--296, 1996.
No context found.
G. Gottlob, M. Schrefl, and B. Rck. Extending object-oriented systems with roles. ACM Transactions on Information Systems, 14(3), July 1996.
No context found.
Gottlob, G., Schre#, M., and Rock, B. #1994#. Extending Object-Oriented Systems with Roles. ACM Transactions on Information Systems.To appear.
No context found.
G. Gottlob, M. Schre#, and B. R#ock. Extending Object-Oriented Systems with Roles. ACM Transactions on Information Systems, 14#3#, July 1996
First 50 documents Next 50
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