General framework for the description of QoS in UML
M. de Miguel. Sixth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, 2003, Seite 61--68. IEEE, (Mai 2003)
DOI: 10.1109/ISORC.2003.1199237
Zusammenfassung
UML is useful for modeling object-oriented systems, their behavior and interaction. However, UML currently does not support the modeling of quality of service (QoS) criteria, such as the reliability and accuracy (i.e., quality). A QoS framework provides support to ensure consistency in modeling various qualities of service. It supports a general categorization of different kinds of QoS; including QoS that are fixed at design time as well as ones that are managed dynamically. And it supports the integration of different categories of QoS for the purpose of QoS modeling of system aspects. Frequently the behavior of a system component is functionally correct, but the result it generates is nevertheless unacceptable because the result does not meet some QoS criteria. One way to enhance the capability of the system to deliver results of acceptable quality is to use flexible components that adapt their behavior depending on the resources available and the QoS required.
SUMMARY (Fritz): Foundation paper for UML Profile for modeling QoS and Fault Tolerance. Similar to QoS modeling language for high quality systems paper, but with more details, particularly around the QoS metamodel. Basic functional elemets: (1) Resource Consuming Component (RCC) for QoS application architectures (service provider infrastructure demands) and (2) QoS-aware Specification Functions (QASF) (client quality requirements).
%0 Conference Paper
%1 de_miguel_general_2003
%A de Miguel, M. A
%B Sixth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, 2003
%D 2003
%I IEEE
%K Delay; Jitter; Object Pattern QoS Quality Real Telecommunications; Unified description; distributed fault formal language languages; management; methods; modeling modeling; object object-oriented of oriented quality recognition; service; specification specification; system systems; time tolerance; uml;
%P 61--68
%R 10.1109/ISORC.2003.1199237
%T General framework for the description of QoS in UML
%X UML is useful for modeling object-oriented systems, their behavior and interaction. However, UML currently does not support the modeling of quality of service (QoS) criteria, such as the reliability and accuracy (i.e., quality). A QoS framework provides support to ensure consistency in modeling various qualities of service. It supports a general categorization of different kinds of QoS; including QoS that are fixed at design time as well as ones that are managed dynamically. And it supports the integration of different categories of QoS for the purpose of QoS modeling of system aspects. Frequently the behavior of a system component is functionally correct, but the result it generates is nevertheless unacceptable because the result does not meet some QoS criteria. One way to enhance the capability of the system to deliver results of acceptable quality is to use flexible components that adapt their behavior depending on the resources available and the QoS required.
%@ 0-7695-1928-8
@inproceedings{de_miguel_general_2003,
abstract = {UML is useful for modeling object-oriented systems, their behavior and interaction. However, UML currently does not support the modeling of quality of service (QoS) criteria, such as the reliability and accuracy (i.e., quality). A QoS framework provides support to ensure consistency in modeling various qualities of service. It supports a general categorization of different kinds of QoS; including QoS that are fixed at design time as well as ones that are managed dynamically. And it supports the integration of different categories of QoS for the purpose of QoS modeling of system aspects. Frequently the behavior of a system component is functionally correct, but the result it generates is nevertheless unacceptable because the result does not meet some QoS criteria. One way to enhance the capability of the system to deliver results of acceptable quality is to use flexible components that adapt their behavior depending on the resources available and the QoS required.},
added-at = {2013-02-28T11:13:35.000+0100},
author = {de Miguel, M. A},
biburl = {https://www.bibsonomy.org/bibtex/2585d1bb87a335a66019e1e8ce20ab6af/fritzsolms},
booktitle = {Sixth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, 2003},
doi = {10.1109/ISORC.2003.1199237},
interhash = {59972d5891519696114628a26e2284e6},
intrahash = {585d1bb87a335a66019e1e8ce20ab6af},
isbn = {0-7695-1928-8},
keywords = {Delay; Jitter; Object Pattern QoS Quality Real Telecommunications; Unified description; distributed fault formal language languages; management; methods; modeling modeling; object object-oriented of oriented quality recognition; service; specification specification; system systems; time tolerance; uml;},
lccn = {0007},
month = May,
pages = {61--68},
publisher = {IEEE},
review = {SUMMARY (Fritz): Foundation paper for UML Profile for modeling QoS and Fault Tolerance. Similar to QoS modeling language for high quality systems paper, but with more details, particularly around the QoS metamodel. Basic functional elemets: (1) Resource Consuming Component (RCC) for QoS application architectures (service provider infrastructure demands) and (2) QoS-aware Specification Functions (QASF) (client quality requirements).},
timestamp = {2013-02-28T11:14:17.000+0100},
title = {General framework for the description of QoS in UML},
year = 2003
}