%0 Conference Paper %1 coady03 %A Coady, Yvonne %A Kiczales, Gregor %B AOSD '03: Proceedings of the 2nd international conference on Aspect-oriented software development %C New York, NY, USA %D 2003 %I ACM Press %K evolution aspects software litmap %P 50--59 %R 10.1145/643603.643609 %T Back to the future: a retroactive study of aspect evolution in operating system code %U http://dx.doi.org/10.1145/643603.643609 %@ 1581136609

@inproceedings{coady03, added-at = {2006-03-24T16:34:33.000+0100}, address = {New York, NY, USA}, author = {Coady, Yvonne and Kiczales, Gregor}, biburl = {https://www.bibsonomy.org/bibtex/20a6c92edcbb5f460663b41c53536126a/neilernst}, booktitle = {AOSD '03: Proceedings of the 2nd international conference on Aspect-oriented software development}, citeulike-article-id = {333436}, comment = {- could the same results be achieved by refactoring (e.g. smart person syndrome) - what are cross-cutting concerns? Kiczales et al 1997. - "each concern evolved differently... and we found that the aspect-oriented implementation better facilitated independent development and localized change" p 50 - is there a tool for doing high-level aspect design, eg. for new systems? There is UML for OO, what do you do for AOP? - would like to see something on validity threats,e.g. does this apply to all other systems?}, description = {sdasda}, doi = {10.1145/643603.643609}, interhash = {920074e6d0bc0ab52896b90675f117ca}, intrahash = {0a6c92edcbb5f460663b41c53536126a}, isbn = {1581136609}, keywords = {evolution aspects software litmap}, pages = {50--59}, priority = {0}, publisher = {ACM Press}, timestamp = {2006-03-24T16:34:33.000+0100}, title = {Back to the future: a retroactive study of aspect evolution in operating system code}, url = {http://dx.doi.org/10.1145/643603.643609}, year = 2003 }