Aspect-Oriented Coordination

Fuentes, Lidia; Sánchez, Pablo

doi:10.1016/j.entcs.2007.05.049

Cited by 5 publications

(4 citation statements)

References 33 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The improvement on modularization due to the use of aspect-orientation is valid only if aspect-orientation fulfils its promise of being able to encapsulate a crosscutting concern in a single module. Whereas some works have demonstrated that concerns such as Persistence [87], Scheduling [69], Context-Awareness [101];), Distribution [97] or Coordination [40], among others [75], can be adequately modularized in a single module using aspects, aspect-orientation should not be considered the Holy Grail in Software Engineering, as there are still some challenges to separate any kind of crosscutting concern, as discussed in [65]; Kienzle and Gélinau, 2006). So, if aspect-orientation fails on adequately encapsulating a crosscutting concern into a single module, the benefits of using aspect-oriented techniques at the architectural level would be limited, for that concern, to the automation provided to model-driven techniques, but the benefits regarding improvement on maintenance and evolution would be lost.…”

Section: Applicability: Threats To Validitymentioning

confidence: 99%

Model-driven development for early aspects

Sánchez

Moreira

Fuentes

et al. 2010

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Section: Applicability: Threats To Validitymentioning

confidence: 99%

Model-driven development for early aspects

Sánchez

Moreira

Fuentes

et al. 2010

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

“…Whereas some works have demonstrated that concerns such as persistence [38], scheduling [26], context-awareness [46], distribution [44] or coordination [15], among others [30], can be adequately modularized in a single module using aspects, there are some crosscutting concerns, such as transactions [22,23] whose proper encapsulation into an aspect still remains a challenge for aspect-oriented techniques.…”

Section: Aspect-orientationmentioning

confidence: 99%

Aspect-oriented design and implementation of context-aware pervasive applications

Fuentes

Gámez

Sánchez

2009

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

Pervasive applications must be aware of the contexts where they are executed. These contexts may vary greatly and change quickly. Two main problems are associated with this issue: (1) context-awareness is a crosscutting concern that cannot be well-encapsulated in a single module using traditional technologies, thus hindering software maintenance and reusability; and (2) reasoning about application design correctness can be complex due to the number and diversity of potential contexts where a pervasive application could be executed. In order to overcome these problems, we present a process for the design and implementation of context-aware pervasive applications that uses aspect-orientation and executable modelling in order to overcome these shortcomings. Aspect-oriented techniques contribute to the encapsulation of crosscutting concerns, such as context-awareness, into well-localized modules. Executable modelling helps engineers to reason about application design by executing the design models in different contexts and situations. Pervasive applications are modelled using the aspect-oriented executable modelling UML 2.0 profile, executed at the modelling level for testing purposes, and then mapped into an aspect-oriented middleware platform for pervasive applications. This process is illustrated using a

show abstract

“…2. Study aspect-oriented system: Aspect-oriented technologies [31] are aimed at providing mechanisms to reduce the coupling between components. One such research is to compare aspect-oriented program with object-oriented program and investigate whether the feature metrics of objected-oriented program, crosscutting concerns, have lower impact on component co-evolution.…”

Section: Conclusion and Future Researchmentioning

confidence: 99%

Component co-evolution and component dependency: speculations and verifications

Mishra

Ramaswamy

2010

IET Softw.

View full text Add to dashboard Cite

Software component interaction is essential for realising proper software system functions. Such interactions between software components induce interdependencies between multiple components. One effect of such a dependency is co-evolution, wherein changes made to one component also requires corresponding changes to other component(s). This study presents a mathematical framework for representing component co-evolution. Two types of co-evolution, internal co-evolution and external co-evolution are defined for an evolving software component. The component dependency metrics that are related with component co-evolutions are analysed and the correlations between component dependency and component co-evolution are hypothesised. Further, in a quasi-experiment of nine open-source Java projects, component dependencies are measured and component revision histories are mined to verify the speculated correlations.

show abstract

Aspect-Oriented Coordination

Cited by 5 publications

References 33 publications

Model-driven development for early aspects

Model-driven development for early aspects

Aspect-oriented design and implementation of context-aware pervasive applications

Component co-evolution and component dependency: speculations and verifications

Contact Info

Product

Resources

About