Developing service-based software systems with QoS monitoring and adaptation

Sik-Sang Yau, Nong Ye, Hessam Sarjoughian, D. Huang

Research output: Chapter in Book/Report/Conference proceedingConference contribution

21 Scopus citations

Abstract

The rapid adoption of SOA in many large-scale distributed applications requires the development of adaptive service-based software systems (ASBS), which have the capability of monitoring the changing system status, analyzing and controlling tradeoffs among multiple QoS features, and adapting its service configuration to satisfy multiple QoS requirements simultaneously. In this paper, a performance-model-oriented approach to developing ASBS is presented. This approach consists of the establishment of performance models for SBS through controlled experiments, the development of QoS monitoring and adaptation (M/A) modules based on the performance models, and the validation of ASBS design through simulations. In our approach, four QoS features: timeliness, throughput, accuracy and security, which are important for many critical applications, are considered.

Original languageEnglish (US)
Title of host publicationProceedings of the IEEE Computer Society Workshop on Future Trends of Distributed Computing Systems
Pages74-80
Number of pages7
DOIs
StatePublished - 2008
Event12th IEEE International Workshop on Future Trends of Distributed Computing Systems, FTDCS 2008 - Kunming, China
Duration: Oct 21 2008Oct 23 2008

Other

Other12th IEEE International Workshop on Future Trends of Distributed Computing Systems, FTDCS 2008
Country/TerritoryChina
CityKunming
Period10/21/0810/23/08

Keywords

  • Adaptive service-based software systems
  • Performance modeling
  • QoS adaptation
  • QoS monitoring
  • SOA-based simulation

ASJC Scopus subject areas

  • Software
  • Hardware and Architecture
  • Computer Networks and Communications

Fingerprint

Dive into the research topics of 'Developing service-based software systems with QoS monitoring and adaptation'. Together they form a unique fingerprint.

Cite this