Towards a proper aspect-oriented model for distributed systems

Mejía, Ismael

doi:10.1145/1960314.1960346

Cited by 1 publication

(1 citation statement)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since crosscutting features implement collaborations involving multiple software components that can be located at different hosts, support for feature distribution is mandatory. Fortunately, AO is also concerned with distribution; several works are dedicated to extending AO with distribution support [54][55][56]; distributed aspects define pointcuts enabling matching interaction points with components at different hosts; they also indicate hosts where advices can be executed. For ACSD approaches enabling distribution of components, distributed aspects are needed for plugging features interacting with components at different hosts.…”

Section: Support For Distributed Aspectsmentioning

confidence: 99%

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Hannousse

2019

IET softw.

View full text Add to dashboard Cite

Coping with crosscutting and dynamic features of software systems has significant impacts on software modularity, reusability, adaptability, and maintainability. However, dealing with such features is a tremendous challenge for different software paradigms, particularly component-based software development (CBSD) where components can be used as black box software units. Fortunately, dealing with crosscutting features is the main focus of aspect-orientation (AO). To compromise, a plethora of different AO and CBSD combinations are available. There is, however, little consensus on how AO and CBSD can be combined and what AO qualities need to be integrated for getting maximum benefits from the combination. In the aim to reach a consensus and increase the understanding of requirements for proper combinations that deal with crosscutting and dynamic features, the authors conduct a domain analysis study of existing combination endeavours; they first identify a set of requirements ought to be fulfilled for proper modelling of crosscutting and dynamic features in component software using AO; second, they group the identified requirements into an evaluation model; third, they check the capability of existing combinations to validate the evaluation model. The study highlighted mandatory requirements for proper combinations and revealed that none of the existing endeavours validates the evaluation model.

show abstract

Section: Support For Distributed Aspectsmentioning

confidence: 99%

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Hannousse

2019

IET softw.

View full text Add to dashboard Cite

show abstract

Towards a proper aspect-oriented model for distributed systems

Cited by 1 publication

References 9 publications

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Contact Info

Product

Resources

About