ACM Home Page
Please provide us with feedback. Feedback
Back to the future: a retroactive study of aspect evolution in operating system code
Full text PdfPdf (976 KB)
Source Aspect-oriented software development archive
Proceedings of the 2nd international conference on Aspect-oriented software development table of contents
Boston, Massachusetts
Pages: 50 - 59  
Year of Publication: 2003
ISBN:1-58113-660-9
Authors
Yvonne Coady  University of British Columbia, Vancouver, BC
Gregor Kiczales  University of British Columbia and Intentional Software Corporation, Bellevue, WA
Sponsors
: Northeastern University
: Intentional Software Corporation
ACM: Association for Computing Machinery
AOSA : Aspect-Oriented Software Association, Inc.
IBMR : IBM Research
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 79,   Downloads (12 Months): 439,   Citation Count: 26
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/643603.643609
What is a DOI?

ABSTRACT

The FreeBSD operating system more than doubled in size between version 2 and version 4. Many changes to primary modularity are easy to spot at a high-leveL For example, new device drivers account for 38% of the growth. Not surprisingly, changes to crosscutting concerns are more difficult to track. In order to better understand how an aspect-oriented implementation would have fared during this evolution, we introduced several aspects to version 2 code, and then rolled them forward into their subsequent incarnations in versions 3 and 4 respectively. This paper describes the impact evolution had on these concerns, and provides a comparative analysis of the changes required to evolve the tangled versus aspect-oriented implementations.Our results show that for the concerns we chose, the aspect-oriented implementation facilitated evolution in four key ways: (1) changes were better localized, (2) configurability was more explicit, (3) redundancy was reduced, and (4) extensibility aligned with an aspect was more modular. Additionally, we found that the aspect-oriented implementation had negligible impact on performance.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
 
3
AspectC.www.cs.ubc.ca/labs/spl/aspects/aspectc.html.
 
4
Luciano Porto Barreto, and Gilles Muller. Bossa: A Language-Based Approach for the Design of Real Time Schedulers, in Proceedings of the 23rd IEEE Real-Time Systems, 2002.
5
6
 
7
Marc E. Fiuczynski, and Brian N. Bershad. An Extensible Protocol Architecture for Application-Specific Networking, in Proceedings of the Winter USENIX Conference, 1996.
 
8
9
 
10
 
11
Gregor Kiczales, John Lamping, Anurag Mendhekar, Chris Maeda, Cristina Videira Lopes, Jean-Marc Loingtier, and John Irwin. Aspect-Oriented Programming, in Proceedings of the European Conference on Object-Oriented Programming (ECOOP), 1997.
 
12
Chris Maeda. Flexible System Software through Service Decomposition, in Proceedings of the Conference on Object-Oriented Programming: Systems, Languages, and Applications (OOPSLA), 1994.
 
13
Dylan McNamee, and Katherine Armstrong. Extending the Mach External Pager Interface to Allow User Level Page Replacement Policies, in Technical Report University of Washington UWCSE 90-09-05, 1990.
14
 
15
Paniti Netinant, Constantinos Constantinides, Tzilla Elrad, Mohamed Fayad. Supporting Aspectual Decomposition in the Design of Adaptable Operating Systems Using Aspect-Oriented Frameworks, in Proceedings of the 3rd Workshop on Object-Orientation and Operating Systems (ECOOP-OOOWS), 2000.
16
 
17
 
18
Christopher Small, and Margo Seltzer. A Comparison of Os Extension Technologies, in Proceedings of the USENIX Conference, 1996.
19
 
20
21
22

CITED BY  26

Collaborative Colleagues:
Yvonne Coady: colleagues
Gregor Kiczales: colleagues