Implementing QoS Aware Component-Based Applications

Chimaris, Avraam; Papadopoulos, George Α.

doi:10.1007/978-3-540-30469-2_24

Cited by 1 publication

(3 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Chimaris and Papadopoulos [16] present a quite different notion of contracts. In their view, a contract consists of both a specification of a non-functional property and an aspect (in the sense of aspect-oriented programming (AOP) [25,41]) that can be used to guarantee that property at runtime.…”

Section: Basic Contract Conceptsmentioning

confidence: 98%

“…Notice how the two different measurements are applied to the same component (lines [11][12][13][14][15][16][17][18][19][20][21][22][23][24][25] and how these two specifications are then conjoined together with a constraint over both execution time and accuracy to form the complete specification of the component (lines [27][28][29][30]. A specification like this can be used wherever a component specification can be used.…”

Section: Relations Between Measurementsmentioning

confidence: 99%

“…10 see[49] for a discussion of how to model such properties in TLA + 16. A simple connector context model including the definition of a delay measurement components: is it via an open network, via inter-process communication (IPC), or directly inside the same address space on the same machine?…”

mentioning

confidence: 99%

See 2 more Smart Citations

Formal specification of non-functional properties of component-based software systems

Zschaler

2009

Softw Syst Model

View full text Add to dashboard Cite

Component-based software engineering (CBSE) is viewed as an opportunity to deal with the increasing complexity of modern-day software. Along with CBSE comes the notion of component markets, where more or less generic pieces of software are traded, to be combined into applications by third-party application developers. For such a component market to work successfully, all relevant properties of components must be precisely and formally described. This is especially true for non-functional properties, such as performance, memory foot print, or security. While the specification of functional properties is well understood, nonfunctional properties are only beginning to become a research focus. This paper discusses semantic concepts for the specification of non-functional properties, taking into account the specific needs of a component market. Based on these semantic concepts, we present a new specification language QML/CS that can be used to model non-functional product properties of components and component-based software systems.

show abstract

Section: Basic Contract Conceptsmentioning

confidence: 98%