%0 Conference Paper %1 de_miguel_qos_2003 %A de Miguel, M. A %B Proceedings of the Eighth International Workshop on Object-Oriented Real-Time Dependable Systems, 2003. %D 2003 %I IEEE %K Architecture; Group; Management OMG; Object QoS QoS-aware Quality Real Resource Software Timing; UML Unified Vocabulary description extension; fault formal high interface language; languages; management; mathematical metamodel; model; modeling modeling; object-oriented of oriented programming; quality service; specification specification; system; systems; time tolerance; %P 210--216 %R 10.1109/WORDS.2003.1218085 %T QoS modeling language for high quality systems %X We introduce the main elements of UML (Unified Modeling Language) extension to support QoS specifications, which are the basic constructors of QoS-aware models. Different types of languages are used to specify QoS systems, the most common include extensions of Interface Description Languages, UML extensions and metamodels, and mathematical models. QoS specification methods support the description of QoS concepts that are used for different purposes: i) generation of code for the management of QoS concepts (e.g., negotiation, access to resource managers), ii) specification of QoS-aware architectures, and iii) management of QoS information in QoS reflective infrastructures (e.g., QoS adaptable systems). QoS-aware models support the description of software architectures with quality requirements. The extensions included in this paper are part of an initial submission of OMG Object Management Group) RFP UML profile for quality of service and fault tolerance characteristics and mechanisms %@ 0-7695-1929-6

@inproceedings{de_miguel_qos_2003, abstract = {We introduce the main elements of UML (Unified Modeling Language) extension to support QoS specifications, which are the basic constructors of QoS-aware models. Different types of languages are used to specify QoS systems, the most common include extensions of Interface Description Languages, UML extensions and metamodels, and mathematical models. QoS specification methods support the description of QoS concepts that are used for different purposes: i) generation of code for the management of QoS concepts (e.g., negotiation, access to resource managers), ii) specification of QoS-aware architectures, and iii) management of QoS information in QoS reflective infrastructures (e.g., QoS adaptable systems). QoS-aware models support the description of software architectures with quality requirements. The extensions included in this paper are part of an initial submission of OMG Object Management Group) RFP UML profile for quality of service and fault tolerance characteristics and mechanisms}, added-at = {2013-02-28T11:13:35.000+0100}, author = {de Miguel, M. A}, biburl = {https://www.bibsonomy.org/bibtex/24134738d06893f6586442b0c4df1531f/fritzsolms}, booktitle = {Proceedings of the Eighth International Workshop on Object-Oriented Real-Time Dependable Systems, 2003.}, doi = {10.1109/WORDS.2003.1218085}, interhash = {0f47db6f197e36b9832ea0d0e08980d0}, intrahash = {4134738d06893f6586442b0c4df1531f}, isbn = {0-7695-1929-6}, keywords = {Architecture; Group; Management OMG; Object QoS QoS-aware Quality Real Resource Software Timing; UML Unified Vocabulary description extension; fault formal high interface language; languages; management; mathematical metamodel; model; modeling modeling; object-oriented of oriented programming; quality service; specification specification; system; systems; time tolerance;}, month = jan, pages = {210--216}, publisher = {IEEE}, review = {SUMMARY (Fritz): Overview paper with little details. Ideas used in UML Profile for modeling QoS and Fault Tolerance. 4 general approaches to QoS specification: (1) modeling languages, (2) interface languages, (3) application interfaces and (4) mathematical models. Requirements for QoS language: (1) def of quantifiable quality characteristics, (2) QoS forec = bounds on QoS characteristics, (3) QoS execution models, each with their own Qos Force and (4) QoS adaption and monitoring.}, timestamp = {2013-02-28T11:14:17.000+0100}, title = {QoS modeling language for high quality systems}, year = 2003 }