%0 Book Section %1 kiczales97 %A Kiczales, Gregor %A Lamping, John %A Menhdhekar, Anurag %A Maeda, Chris %A Lopes, Cristina %A Loingtier, Jean-Marc %A Irwin, John %B Proceedings European Conference on Object-Oriented Programming %C Berlin, Heidelberg, and New York %D 1997 %E Ak\csit, Mehmet %E Matsuoka, Satoshi %I Springer-Verlag %K aspects %P 220--242 %T Aspect-Oriented Programming %U http://citeseer.ist.psu.edu/kiczales97aspectoriented.html %V 1241 %X this paper, we present an overview of our recent research on programming language expressivity. The goal of this work is to make it possible for programs to clearly capture all of the important aspects of a system's behavior, including not only its functionality, but also issues such as its failure handling strategy, its communication strategy, its coordination strategy, its memory reference locality, etc. Our current work is based on the belief that programming languages based on any SINGLE...

@inbook{kiczales97, abstract = {this paper, we present an overview of our recent research on programming language expressivity. The goal of this work is to make it possible for programs to clearly capture all of the important aspects of a system's behavior, including not only its functionality, but also issues such as its failure handling strategy, its communication strategy, its coordination strategy, its memory reference locality, etc. Our current work is based on the belief that programming languages based on any SINGLE...}, added-at = {2006-03-24T16:34:33.000+0100}, address = {Berlin, Heidelberg, and New York}, author = {Kiczales, Gregor and Lamping, John and Menhdhekar, Anurag and Maeda, Chris and Lopes, Cristina and Loingtier, Jean-Marc and Irwin, John}, biburl = {https://www.bibsonomy.org/bibtex/223a1eeb52678d4af61ef91c8193ce4e5/neilernst}, booktitle = {Proceedings European Conference on Object-Oriented Programming}, citeulike-article-id = {125532}, comment = {- "(from fig 1) ... the functional decomposition ... aligns so directly with the domain model" this is why OO took off, I suppose. - "With respect to a system and its implementation using a GP-based language, a property that must be implemented is: * A component, if it can be cleanly encapsulated in a generalized procedure (i.e. object, method, procedure, API). By cleanly, we mean welllocalized, and easily accessed and composed as necessary. Components tend to be units of the system’s functional decomposition, such as image filters, bank accounts and GUI widgets. * An aspect, if it can not be cleanly encapsulated in a generalized procedure. Aspects tend not to be units of the system’s functional decomposition, but rather to be properties that affect the performance or semantics of the components in systemic ways. Examples of aspects include memory access patterns and synchronization of concurrent objects." - could aspects be an element in knowledge engineering design? aspects could be similar, maintainability, reusability, documentation, modeling}, description = {sdasda}, editor = {Ak\csit, Mehmet and Matsuoka, Satoshi}, interhash = {050819acb2cd3a9867dad7ed4b5fa657}, intrahash = {23a1eeb52678d4af61ef91c8193ce4e5}, keywords = {aspects}, pages = {220--242}, priority = {0}, publisher = {Springer-Verlag}, timestamp = {2006-03-24T16:34:33.000+0100}, title = {Aspect-Oriented Programming}, url = {http://citeseer.ist.psu.edu/kiczales97aspectoriented.html}, volume = 1241, year = 1997 }