A Loosely Coupled Aspect Language for Soa Applications

Mendonça, Nabor C.; Silva, Clayton F.; Maia, Ian G.; Rodriguês, Maria Andréia Formico; Valente, Marco

doi:10.1142/s0218194008003623

Cited by 8 publications

(10 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Works in the field of AOP can be categorized into those works that apply AOP at the implementation level ( [17]), those that extend the web service framework (e.g., its roles and technical specifications) with aspect-oriented concepts ( [30]), and those that introduce new aspect languages ( [24,7]). …”

Section: Discussionmentioning

confidence: 99%

“…Nabor C. Mendonça et al [24] introduce the Web Service Aspect Language (WSAL) which provides aspects that can be freely specified, implemented, deployed and executed as loosely coupled web services and thus are implementation technology-independent. Weaving is realized at network level by Web intermediary technology.…”

Section: Aop For Web Services (Black Box View)mentioning

confidence: 99%

See 1 more Smart Citation

Non-functional concerns in web services

Schmeling¹,

Charfi²,

Mezini

2010

Proceedings of the 12th International Conference on Information Integration and Web-Based Applications &Amp; Services

View full text Add to dashboard Cite

For the success and adoption of web services it is essential that not only functional concerns (FC) are addressed but also non-functional concerns (NFC) such as security, reliable messaging, performance, and availability. The support for non-functional concerns encompasses two aspects: the specification and the enforcement and we focus thereby on two views: the black box view (only the interface) and the gray box view (the internal process of a composite service).In this paper we identify the most important requirements for the specification and enforcement of NFCs whilst taking the two different views into account. Furthermore, we present a thorough analysis of the state-of-the-art works based on those requirements and identify areas where future work has to be conducted to fulfill all identified requirements.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Aop For Web Services (Black Box View)mentioning

confidence: 99%

Non-functional concerns in web services

Schmeling¹,

Charfi²,

Mezini

2010

Proceedings of the 12th International Conference on Information Integration and Web-Based Applications &Amp; Services

View full text Add to dashboard Cite

show abstract

“…Scattered requirements can be accepted as a significant obstacle to modularity. In the approach simulation environment, a model is interpreted that it is able to categorize anticipated behaviors by modeler for different conceptual world and resolution [1][2][3].…”

Section: Aspect Oriented Programmingmentioning

confidence: 99%

Aspect Oriented Programming Perspective in Software Agents and Simulation

Hocaoglu¹

2017

Int J Adv Tech

View full text Add to dashboard Cite

MotivationThe motivations of the study are summarized under three categories. These are 1) to give a programming approach based on agent programming to aspect oriented programming, 2) to propose a solution for simulation time management modeled as an aspect and not coded into simulation kernel to make simulation execution algorithms plug- AbstractWhile object-oriented programming paradigm gives a vertical software design, aspect orientation enhances this vertically deep design by horizontal association. An agent based solution is offered for aspect-oriented programming paradigm in agent and simulation development. Agent driven simulation framework (AdSiF) is technological background of the study. AdSiF provides a declarative scripting agent programming language and it combines object oriented programming, logic programming, and agent based programming in state oriented programming paradigm as a surrounding paradigm. State-oriented programming paradigm is at the background of script and it allows programming by extended state charts. In this paper, the solution given by AdSiF for aspect-oriented programming paradigm that draws a solution background related with scattered codes, scattered requirements and tangled requirements is examined. It is explained how to distribute states and behaviors to satisfy scattered requirements, to behaviors and behavior lists, respectively and how behavior phase transitions are used to activate specific behaviors and behavior lists (a group of behaviors) to satisfy a set of requirements and to show different behavioral aspects of an agent and/ or a simulation entity. The solution also provides a solution by shifting modeling aspects conditionally in run time for conceptually different modeling requirements as well as tangled requirements. From this respect, the solution carries aspect oriented programming from design time to execution time and provides a dynamically manageable, flexible, loosely coupled and high coherent simulation and agent design. Using dynamic aspect management, parallel simulation synchronization algorithms are modeled as behaviors and each of them is grouped as an aspect and a rule based reasoning mechanism is developed to shift between algorithms depending on control criteria.

show abstract

“…One strategy is to apply AOP on implementation level using programming language specific extensions such as AspectJ and another one is to extend the web services framework with new concepts and technologies. For example Henkel et al [12] use AspectJ for monitoring the quality of service of web services, whereas Aspect-Oriented Web Services (AOWS by Singh et al [25]), Web Service Aspect Language (WSAL by Nabor C. Mendonça et al [16]) and Web Services Management Layer (WSML by Verheecke et al [29]) provide new language concepts for extending the web services technology stack with aspect technology.…”

Section: State Of the Art And Related Workmentioning

confidence: 99%

“…Most of them ( [27], [7], [9], [8], [18], [17]) focus only on particular aspects of either specification or realization and a majority does not take composition into account [27], [7], [9], [8], [18], [12], [25], [16], [29]. Sometimes composition is accomplished on specification level where no knowledge of the realization of those concerns exists [26].…”

mentioning

confidence: 99%

Composing Non-functional Concerns in Web Services

Schmeling¹,

Charfi

Thome³

et al. 2011

2011 IEEE Ninth European Conference on Web Services

View full text Add to dashboard Cite

Affirmation / Ehrenwörtliche Erklärung I hereby declare that I have written the following thesis without the inadmissible assistance of third parties and using only the indicated sources and aids. All instances in which outside sources were used have been marked accordingly. This work has not been presented to any test authority in its current or in a similar form. Hiermit versichere ich, die vorliegende Doktorarbeit ohne Hilfe Dritter und nur mit den an-gegebenen Quellen und Hilfsmitteln angefertigt zu haben. Alle Stellen, die aus den Quellen entnommen wurden, sind als solche kenntlich gemacht worden. Diese Arbeit hat in gleicher oder ähnlicher Form noch keiner Prüfungsbehörde vorgelegen. Darmstadt, March 2013 Benjamin Schmeling Acknowledgments My sincere thanks go to Prof. Dr. Mira Mezini and Prof. Dr. Tai for their support and guidance during my Ph.D. work as well as to my colleague Anis Charfi for his advice, guidance and help throughout the rendering of this Ph.D. thesis. He contributed much of his time in fruitful discussion with me about new ideas and their realization. I am also grateful for the excellent support from SAP Research and my colleague Steffen Heinzl for the many valuable discussions on my Ph.D. thesis, and in this regard I would also like to thank Mohamed Aly, Heiko Witteborg, Francesco Novelli and all the other colleagues. My students Rainer Thome, Marko Martin and Ajay Sagar contributed to the work described in this thesis by implementing parts of the modeling tool and code generator in the context of their theses. A well-deserved word of appreciation is also in order for Evelyn Nichols for her efforts to improve my English. Finally, I extend my profound gratitude to my family for their unwavering support throughout my studies, which ultimately helped to make their successful conclusion and this thesis a reality. I authored this paper while working as a research associate at SAP Research, during which time I contributed to projects PREMIUM|Services (01IA08003A) and InDiNet (01IC10S04A) which were partially funded by the German Federal Ministry of Education (BMBF). Hence, I thank the BMBF for its financial support. Abstract In software development, two types of concerns must generally be addressed: functional and non-functional ones. Functional concerns relate to the main or core functionality of a software, whereas non-functional concerns represent quality characteristics of the same. It is widely accepted that the two types of concerns should be strictly separated from one another to increase maintainability, understandability and reusability of a software. In component-based software systems, this strict separation of concerns results in the implementation of the respective concerns as functional as well as non-functional components. From the current perspective, web services are the prevalent technology for implementing such component-based software systems. They adhere to open standards and describe a well-defined interface which is strictly separated from the implementation of the ser...

show abstract

A Loosely Coupled Aspect Language for Soa Applications

Cited by 8 publications

References 4 publications

Non-functional concerns in web services

Non-functional concerns in web services

Aspect Oriented Programming Perspective in Software Agents and Simulation

Composing Non-functional Concerns in Web Services

Contact Info

Product

Resources

About