Modelling languages and development frameworks give support for functional and structural description of software architectures. But quality-aware applications require languages which allow expressing QoS as a first-class concept during architecture design and service composition, and to extend existing tools and infrastructures adding support for modelling, evaluating, managing and monitoring QoS aspects. In addition to its functional behaviour and internal structure, the developer of each service must consider the fulfilment of its quality requirements. If the service is flexible, the output quality depends both on input quality and available resources (e.g., amounts of CPU execution time and memory). From the software engineering point of view, modelling of quality-aware requirements and architectures require modelling support for the description of quality concepts, support for the analysis of quality properties (e.g. model checking and consistencies of quality constraints, assembly of quality), tool support for the transition from quality requirements to quality-aware architectures, and from quality-aware architecture to service run-time infrastructures. Quality management in run-time service infrastructures must give support for handling quality concepts dynamically. QoS-aware modeling frameworks and QoS-aware runtime management infrastructures require a common evolution to get their integration.
2008 11th IEEE International Symposium on Object Oriented Real-Time Distributed Computing (ISORC)
year
2008
month
may
pages
563--569
publisher
IEEE
isbn
978-0-7695-3132-8
review
SUMMARY (Fritz): Largely a review paper of current/then support for QoS within MDD approaches. - point out that not all quality requirements are necessarily known at compile time, but that quality requirements could be negotiated at run-time (e.g. based on actual loads). - quality requirements from client and quality guarantees/paramers from service provider Quality languages: - QML (QoS Modeling Language) - CQML (Component Quality Modeling Language) - UML Profile for QoS and Fault Tolerance Quality requirements should be specified with metrics
%0 Conference Paper
%1 de_miguel_model_2008
%A de Miguel, M. A
%A Massonet, P.
%A Silva, J. P
%A Briones, J.
%B 2008 11th IEEE International Symposium on Object Oriented Real-Time Distributed Computing (ISORC)
%D 2008
%I IEEE
%K Application Architecture; Assembly; Computer Monitoring; Quality Runtime; Software architecture; architectures; based checking; development; engineering; formal languages languages; management; model modelling of quality quality-aware quality; requirements; service; services; software software; specification specification; support; verification; {QoS};
%P 563--569
%R 10.1109/ISORC.2008.23
%T Model Based Development of Quality-Aware Software Services
%X Modelling languages and development frameworks give support for functional and structural description of software architectures. But quality-aware applications require languages which allow expressing QoS as a first-class concept during architecture design and service composition, and to extend existing tools and infrastructures adding support for modelling, evaluating, managing and monitoring QoS aspects. In addition to its functional behaviour and internal structure, the developer of each service must consider the fulfilment of its quality requirements. If the service is flexible, the output quality depends both on input quality and available resources (e.g., amounts of CPU execution time and memory). From the software engineering point of view, modelling of quality-aware requirements and architectures require modelling support for the description of quality concepts, support for the analysis of quality properties (e.g. model checking and consistencies of quality constraints, assembly of quality), tool support for the transition from quality requirements to quality-aware architectures, and from quality-aware architecture to service run-time infrastructures. Quality management in run-time service infrastructures must give support for handling quality concepts dynamically. QoS-aware modeling frameworks and QoS-aware runtime management infrastructures require a common evolution to get their integration.
%@ 978-0-7695-3132-8
@inproceedings{de_miguel_model_2008,
abstract = {Modelling languages and development frameworks give support for functional and structural description of software architectures. But quality-aware applications require languages which allow expressing {QoS} as a first-class concept during architecture design and service composition, and to extend existing tools and infrastructures adding support for modelling, evaluating, managing and monitoring {QoS} aspects. In addition to its functional behaviour and internal structure, the developer of each service must consider the fulfilment of its quality requirements. If the service is flexible, the output quality depends both on input quality and available resources (e.g., amounts of {CPU} execution time and memory). From the software engineering point of view, modelling of quality-aware requirements and architectures require modelling support for the description of quality concepts, support for the analysis of quality properties (e.g. model checking and consistencies of quality constraints, assembly of quality), tool support for the transition from quality requirements to quality-aware architectures, and from quality-aware architecture to service run-time infrastructures. Quality management in run-time service infrastructures must give support for handling quality concepts dynamically. {QoS-aware} modeling frameworks and {QoS-aware} runtime management infrastructures require a common evolution to get their integration.},
added-at = {2013-02-28T11:13:35.000+0100},
author = {de Miguel, M. A and Massonet, P. and Silva, J. P and Briones, J.},
biburl = {https://www.bibsonomy.org/bibtex/23492c88cad8d447e6065b5d6c8942a0b/fritzsolms},
booktitle = {2008 11th IEEE International Symposium on Object Oriented Real-Time Distributed Computing (ISORC)},
doi = {10.1109/ISORC.2008.23},
interhash = {e6fae8d14f803a93f78ade33b7feeab4},
intrahash = {3492c88cad8d447e6065b5d6c8942a0b},
isbn = {978-0-7695-3132-8},
keywords = {Application Architecture; Assembly; Computer Monitoring; Quality Runtime; Software architecture; architectures; based checking; development; engineering; formal languages languages; management; model modelling of quality quality-aware quality; requirements; service; services; software software; specification specification; support; verification; {QoS};},
month = may,
pages = {563--569},
publisher = {IEEE},
review = {SUMMARY (Fritz): Largely a review paper of current/then support for QoS within MDD approaches. - point out that not all quality requirements are necessarily known at compile time, but that quality requirements could be negotiated at run-time (e.g. based on actual loads). - quality requirements from client and quality guarantees/paramers from service provider Quality languages: - QML (QoS Modeling Language) - CQML (Component Quality Modeling Language) - UML Profile for QoS and Fault Tolerance Quality requirements should be specified with metrics},
timestamp = {2013-02-28T11:14:17.000+0100},
title = {Model Based Development of Quality-Aware Software Services},
year = 2008
}