Describing and using non functional aspects in component based applications

Duclos, F.; Estublier, Jacky; Morat, Philippe

doi:10.1145/508387.508394

Cited by 23 publications

(33 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The implementation of middleware can also benefit from such crosscutting modularization mechanisms [29,30,69,87].…”

Section: 22mentioning

confidence: 99%

“…Assume that these operations return a string result with the vacation package information, the flight information, or accommodation information. The advice (lines [16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32][33][34][35]) is a sequence activity that executes before the join point activity. At the beginning of the advice, the input parameters of the car rental Web Service are taken from the parent process using the context collection variable ThisProcess(clientrequest) (line 20).…”

Section: Listing 6 the Aspect For Monitoring Execution Timementioning

confidence: 99%

See 1 more Smart Citation

AO4BPEL: An Aspect-oriented Extension to BPEL

2007

View full text Add to dashboard Cite

Process-oriented composition languages such as BPEL allow Web Services to be composed into more sophisticated services using a workflow process. However, such languages exhibit some limitations with respect to modularity and flexibility. They do not provide means for a well-modularized specification of crosscutting concerns such as logging, persistence, auditing, and security. They also do not support the dynamic adaptation of composition at runtime. In this paper, we advocate an aspect-oriented approach to Web Service composition and present the design and implementation of AO4BPEL, an aspect-oriented extension to BPEL. We illustrate through examples how AO4BPEL makes the composition specification more modular and the composition itself more flexible and adaptable.

show abstract

“…The implementation of middleware can also benefit from such crosscutting modularization mechanisms [29,30,69,87].…”

Section: 22mentioning

confidence: 99%

Section: Listing 6 the Aspect For Monitoring Execution Timementioning

confidence: 99%

AO4BPEL: An Aspect-oriented Extension to BPEL

2007

View full text Add to dashboard Cite

show abstract

“…In the same spirit, Duclos et al [14] have proposed to specify QoS requirements as aspects in the architectural models for providing separation of concerns, monitoring these requirements at runtime. The approach of Genssler et al enables generating scheduling support based on QoS declarations [16].…”

Section: Related Workmentioning

confidence: 99%

A Step-Wise Approach for Integrating QoS throughout Software Development

Gatti

Balland

Consel

2011

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. When developing real-time systems such as avionics software, it is critical to ensure the performance of these systems. In general, deterministic Quality of Service (QoS) is guaranteed by the execution platform, independently of a particular application. For example, in the avionics domain, the ARINC 664 standard defines a data network that provides deterministic QoS guarantees. However, this strategy falls short of addressing how the QoS requirements of an application get transformed through all development phases and artifacts. Existing approaches provide support for QoS concerns that only cover part of the development process, preventing traceability. In this paper, we propose a declarative approach for specifying QoS requirements that covers the complete software development process, from the requirements analysis to the deployment. This step-wise approach is dedicated to control-loop systems such as avionics software. The domainspecific trait of this approach enables the stakeholders to be guided and ensures QoS requirements traceability via a tool-based methodology.

show abstract

“…We choose to focus on the ones that provide languages, or tools for AOP. Hence, even if they are of great interest, we leave apart works on AOP in the design and analysis stages [14][15], UMLbased design notations for aspects [16][17] [18], AOP for databases [38], AOP for operating systems [39], AOP for component based systems [40][41], formalization of AOP systems [42], OO frameworks to support crosscutting concerns [43], or AOP for other languages than Java. The projects we review are classified according to the way aspects are introduced: either at compile time (AspectJ, CFOM, Aspectual components), or at run time (PROSE, Lasagne) with some support for dynamic AOP.…”

Section: Related Workmentioning

confidence: 99%

JAC: an aspect‐based distributed dynamic framework

et al. 2004

View full text Add to dashboard Cite

SUMMARYIn this paper, we present the JAC (Java Aspect Components) framework for building aspect-oriented distributed applications in Java. This paper describes the aspect-oriented programming model and the architectural details of the framework implementation. The framework enables extension of application semantics for handling well-separated concerns. This is achieved with a software entity called an aspect component (AC). ACs provide distributed pointcuts, dynamic wrappers and metamodel annotations. Distributed pointcuts are a key feature of our framework. They enable the definition of crosscutting structures that do not need to be located on a single host. ACs are dynamic. They can be added, removed, and controlled at runtime. This enables our framework for use in highly dynamic environments where adaptable software is needed.

show abstract

Describing and using non functional aspects in component based applications

Cited by 23 publications

References 0 publications

AO4BPEL: An Aspect-oriented Extension to BPEL

AO4BPEL: An Aspect-oriented Extension to BPEL

A Step-Wise Approach for Integrating QoS throughout Software Development

JAC: an aspect‐based distributed dynamic framework

Contact Info

Product

Resources

About