Using multidimensional separation of concerns to (re)shape evolving software

Ossher, Harold; Tarr, Peri

doi:10.1145/383845.383856

Cited by 156 publications

(88 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Furthermore, through usage of graph transformation our approach in principal allows composition of two aspect models or even two primary models. This generality is similar to Hyperspaces [3]. Hyperspaces is an extension of subject oriented programming [10], used to achieve multi-dimensional separation of concerns at the implementation level.…”

Section: Discussion and Related Workmentioning

confidence: 99%

An Aspect-oriented Approach to Manage QoS Dependability Dimensions in Model Driven Development

Köllmann

Kutvonen²,

Linington

et al. 2007

Proceedings of the 3rd International Workshop on Model-Driven Enterprise Information Systems

View full text Add to dashboard Cite

Abstract. Model-driven development approaches commonly use an abstraction of platform specific features for improving reusability and verifiability of the core functionality models. However, the core functionality may still be tangled with features that address important dependability concerns across a design model -for example features such as security, trust and performance. These features can commonly be called Quality of Service (QoS) features. This paper presents an approach for managing several dependability dimensions. We use aspect oriented and model driven development techniques to separate and construct QoS independent models, and graph-based transformation techniques to derive the corresponding QoS specific models.

show abstract

Section: Discussion and Related Workmentioning

confidence: 99%

An Aspect-oriented Approach to Manage QoS Dependability Dimensions in Model Driven Development

Köllmann

Kutvonen²,

Linington

et al. 2007

Proceedings of the 3rd International Workshop on Model-Driven Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

“…An interesting alternative to layered designs is Subject-Oriented Programming (SOP) [26,40]. This technique is one of the roots of AOP.…”

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

“…Besides, several other approaches use techniques that can be closely related to around advising, for instance: Composition Filters [2] and Multi-Dimensional Separation of Concerns [12].…”

Section: Around Advice Utilizationsmentioning

confidence: 99%

CompAr: Ensuring Safe Around Advice Composition

Pawlak

Duchien

Seinturier

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Advanced techniques in separation of concerns such as Aspect-Oriented Programming, help to develop more maintainable and more efficient applications by providing means for modularizing crosscutting concerns. However, conflicts may appear when several concerns need to be composed for the same application, especially when dealing with around advice. We call this problem the Aspect Composition Issue (ACI). Based on our experience in programming aspects, this paper presents a language called CompAr, which allows the programmer to abstractly define an execution domain, the advice codes, and their execution constraints. The CompAr compiler then evaluates the definitions in order to check if the execution constraints are fulfilled. Using a concrete AOP case study, we show how to use the CompAr language in order to detect and avoid ACIs.

show abstract

Using multidimensional separation of concerns to (re)shape evolving software

Cited by 156 publications

References 14 publications

An Aspect-oriented Approach to Manage QoS Dependability Dimensions in Model Driven Development

An Aspect-oriented Approach to Manage QoS Dependability Dimensions in Model Driven Development

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

CompAr: Ensuring Safe Around Advice Composition

Contact Info

Product

Resources

About