Using AspectJ for component integration in middleware

Colyer, Adrian; Clement, Andy; Bodkin, Ron; Hugunin, Jim

doi:10.1145/949437.949440

Cited by 5 publications

(7 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…All authors come to the conclusion that AOP is a very promising approach, although still not widely used in the industrial practice [38]. In the middleware area several case studies showed that AOP allows software developers to scale features and footprint by supporting the static configuration of fine-grained configurable features [50,13,51]. All of these studies were conducted with AspectJ.…”

Section: Related Workmentioning

confidence: 99%

Lean and Efficient System Software Product Lines: Where Aspects Beat Objects

Lohmann

Spinczyk

Schröder-Preikschat

2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Software development in the domain of embedded and deeply embedded systems is dominated by cost pressure and extremely limited hardware resources. As a result, modern concepts for separation of concerns and software reuse are widely ignored, as developers worry about the thereby induced memory and performance overhead. Especially object-oriented programming (OOP) is still little in demand. For the development of highly configurable fine-grained system software product lines, however, separation of concerns (SoC) is a crucial property. As the overhead of object-orientation is not acceptable in this domain, we propose aspect-oriented programming (AOP) as an alternative. Compared to OOP, AOP makes it possible to reach similar or even better separation of concerns with significantly smaller memory footprints. In a case study for an embedded system product line the memory costs for SoC could be reduced from 148-236% to 2-10% by using AOP instead of OOP.

show abstract

Section: Related Workmentioning

confidence: 99%

Lean and Efficient System Software Product Lines: Where Aspects Beat Objects

Lohmann

Spinczyk

Schröder-Preikschat

2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…C4 uses AOP concepts to implement a "semantic patch system" for the application of kernel patches [16]. Several other publication show that AOP provides benefits for the development of configurable infrastructure software in the broad sense, namely middleware [8,31,19] and databases [29] product lines. All these studies demonstrate that there are real cases for aspects in system software.…”

Section: Applicationsmentioning

confidence: 99%

“…From the 28 analyzed kernel functions that are called directly or indirectly from the test applications and that are affected by interrupt synchronization, 19 functions turned out to be actually identically in the machine code 8 . Eight functions turned out to be minimal different with respect to the order of instructions and differences in sub-sequences of up to 4 instructions.…”

Section: Runtime Costsmentioning

confidence: 99%

“…This furthermore can be subdivided into work based on static weaving, and work based on dynamic weaving. An overview of related work regarding AOP in system software with static weaving was already presented in the introduction [7,6,25,27,2,16,8,31,29]. The main contribution of this paper over existing work is the in-depth cost-analysis, performed with system-specific and cost-critical concerns.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

A quantitative analysis of aspects in the eCos kernel

Lohmann

SchelerFabian

TartlerReinhard

et al. 2006

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

Nearly ten years after its first presentation and five years after its first application to operating systems, the suitability of AspectOriented Programming (AOP) for the development of operating system kernels is still highly in dispute. While the AOP advocacy emphasizes the benefits of AOP towards better configurability and maintainability of system software, most kernel developers express a sound skepticism regarding the thereby induced runtime and memory costs: Operating system kernels have to be lean and efficient. We have analyzed the runtime and memory costs of aspects in general, on the level of µ-benchmarks, and by refactoring and extending the eCos operating system kernel using AspectC++, an AOP extension to the C++ language. Our results show that most AOP features do not induce a intrinsic overhead and that the actual overhead induced by AspectC++ is very low. We have also analyzed a test case with significant aspect-related costs. This example shows how the structure of the underlying kernel can have a negative impact on aspect implementations and how these costs can be avoided by an aspect-aware design. Based on this analysis, our conclusion is that AOP is suitable for the development of operating system kernels and other kinds of highly efficient infrastructure software.

show abstract

“…In recent years, Aspect Oriented Programming (AOP) has become an increasingly important software development method, whose goal is to improve the development and the maintenance of large applications through separation of concerns [6], [5], [3]. In AOP, a program is developed as a set of distinct, non-overlapping concerns, called aspects, Aspects are composed into a coherent application through a process called weaving, that takes place at various points of interest in the program-called join points.…”

Section: Introductionmentioning

confidence: 99%