Modularizing Design Patterns with Aspects: A Quantitative Study

Garcia, Alessandro; Sant’Anna, Cláudio; Figueiredo, Eduardo; Kulesza, Uirá; Lucena, Carlos José Pereira de; Staa, Arndt von

doi:10.1007/11687061_2

Cited by 109 publications

(202 citation statements)

References 17 publications

Supporting

Mentioning

195

Contrasting

Unclassified

Order By: Relevance

“…AOP emergenced as a new paradigm to modularize the concerns whose implementations would otherwise have been spread throughout the whole application, because of the limited abstractions of the underlying programming languages. Since then, several studies [15,16,17,19,35,36] have suggested that AOP is successful in modularizing crosscutting concerns. Unfortunately, these studies either wrongly identify modularization with the lexical SoC offered by AOP, or wrongly measure coupling in AO systems.…”

Section: Motivations and Goalsmentioning

confidence: 99%

“…The same suite of metrics was used by Garcia et al [17] to compare the AO and OO implementations of the Gang-of-Four design patterns. They performed two studies, one on the original implementations from Hannemann & Kiczales and the other on the implementations with introduced changes.…”

Section: Related Workmentioning

confidence: 99%

“…They performed two studies, one on the original implementations from Hannemann & Kiczales and the other on the implementations with introduced changes. These changes were introduced because the H&K implementations encompassed few participant classes to play pattern roles [17]. Garcia and his team concluded that "the use of aspects helped to improve the coupling and cohesion of some pattern implementations."…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Where the Truth Lies: AOP and Its Impact on Software Modularity

Przybyłek

2011

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. Modularity is the single attribute of software that allows a program to be intellectually manageable [29]. The recipe for modularizing is to define a narrow interface, hide an implementation detail, keep low coupling and high cohesion. Over a decade ago, aspect-oriented programming (AOP) was proposed in the literature to "modularize the un-modularizable" [24]. Since then, aspect-oriented languages have been providing new abstraction and composition mechanisms to deal with concerns that could not be modularized because of the limited abstractions of the underlying programming language. This paper is a continuation of our earlier work [32] and further investigates AO software with regard to coupling and cohesion. We compare two versions (Java and AspectJ) of ten applications to review AOP within the context of software modularity. It turns out that the claim that "the software built in AOP is more modular than the software built in OOP" is a myth.

show abstract

Section: Motivations and Goalsmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Where the Truth Lies: AOP and Its Impact on Software Modularity

Przybyłek

2011

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…An extensive study on modularizing design patterns have been performed by Garcia et al [20]. They use Hannemann's implementation of GoF patterns to apply seven metrics that extend and adapt to AOP Chidamber and Kemerer's metrics [16].…”

Section: Related Workmentioning

confidence: 99%

Measuring and Characterizing Crosscutting in Aspect-Based Programs: Basic Metrics and Case Studies

Lopez-Herrejon

Apel

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. Aspects are defined as well-modularized crosscutting concerns. Despite being a core tenet of Aspect Oriented Programming, little research has been done in characterizing and measuring crosscutting concerns. Some of the issues that have not been fully explored are: What kinds of crosscutting concerns exist? What language constructs do they use? And what is the impact of crosscutting in actual Aspect Oriented programs? In this paper we present basic code metrics that categorize crosscutting according to the number of classes crosscut and the language constructs used. We applied the metrics to four non-trivial open source programs implemented in AspectJ. We found that for these systems, the number of classes crosscut by advice per crosscutting is small in relation to the number of classes in the program. We argue why we believe this result is not atypical for Aspect Oriented programs and draw a relation to other non-AOP techniques that provide crosscutting.

show abstract

“…A number of pure code-level approaches have also shown that AO source code may improve certain software qualities (e.g. [30,31]). Obviously, this approach will not work if OO source code is required.…”

Section: Interspace Compositionsmentioning

confidence: 99%

Specifying and Composing Concerns Expressed in Domain-Specific Modeling Languages

Hovsepyan

Baelen

Berbers

et al. 2009

Objects, Components, Models and Patterns

View full text Add to dashboard Cite

Summary. Separation of concerns and levels of abstraction are key software engineering principles that can help master the increasing complexity of software applications. Aspect-oriented modeling (AOM) and domain-specific modeling languages (DSML) are two important and promising approaches in this context. However, little research is done to investigate the synergy between AOM and DSMLs. In this paper we present an asymmetric approach to compose modularized concerns expressed in different DSMLs with an application base model expressed in a general-purpose modeling language (GPML). This allows to specify each concern in the most appropriate modeling language. We introduce the concept of a concern interface, expressed in a GPML, that serves as a common language between a specific concern and the application base. In addition, we use an explicit composition model to specify the syntactic and the semantic links between entities from the different concerns. We explore these concepts using an application where we modularize the user interface modeled in WebML and the access control specified in XACML. The modularized concerns are then composed with an application base that has been specified in UML.

show abstract

Modularizing Design Patterns with Aspects: A Quantitative Study

Cited by 109 publications

References 17 publications

Where the Truth Lies: AOP and Its Impact on Software Modularity

Where the Truth Lies: AOP and Its Impact on Software Modularity

Measuring and Characterizing Crosscutting in Aspect-Based Programs: Basic Metrics and Case Studies

Specifying and Composing Concerns Expressed in Domain-Specific Modeling Languages

Contact Info

Product

Resources

About