Explicit modelling of QoS-dependencies [1 citations — 1 self]
Download:
by Steffen Zschaler, Marcus Meyerhöfer
In Bruel [Bru03
http://www-st.inf.tu-dresden.de/comquad/qoscbse03-explicit.pdf
Add To MetaCart
Abstract:
Abstract. When specifying Quality of Service (QoS) for components the usual method employed is to specify regions of QoS offers and requirements. The component offers a certain QoS under the condition that it will be provided some specified QoS by the environment. The dependency between offered and used QoS is essentially given through discrete examples, rather than an equation or inequity. In the COMQUAD project 3 we have come to the conclusion that in some cases it is both more natural and more efficient to specify these dependencies more explicitly, and precisely. In this position paper we discuss the advantages and disadvantages of both approaches and give some first ideas as to how QoS–dependencies can be specified explicitly. 1
Citations
| 857 | Component Software: Beyond Object-Oriented Programming", AddisonWesley and ACM-Press – Szyperski - 1997 |
| 544 | Interval Analysis – Moore - 1966 |
| 112 | Specification and Design of (Parallel) Programs – Jones - 1983 |
| 96 | Making components contract aware – Beugnard |
| 5 | Øyvind Aagedal. Quality of Service Support in Development of Distributed Systems – Jan - 2001 |
| 2 | Integrating orthogonal middleware functionality in components using interceptors – Pohl, Göbel - 2003 |
| 1 | Choosing a parser for anaphora resolution – unknown authors |
