QoS, SLA, Fault, Workflow
One of our project goals has been to implement a system which will automate the process of choosing services and modifying workflows in order to satisfy dependability requirements. This involves integrating the quality-of-service (QoS) ontology, service level agreement (SLA), and fault tolerant container (FTC) elements of our work into a coherent whole — the SLA specifies the dependability requirements, and the FTC (in conjunction with a workflow engine) allows us to boost the dependability characteristics of component services in order to meet the SLA. To link these up, we need to choose services and FTC policies which will best satisfy the SLA — but in order to make the right choices, we need to understand what the consequences of each choice would be in context of the target workflow.
• A simplified description of the workflow
Agrajag calculates the aggregate QoS characteristics
for the entire workflow. This makes it possible to choose the particular
services and FTC policies which will best match the desired dependability
|Page Maintainer: firstname.lastname@example.org||Credits||Project Members only||Last Modified: 10 August, 2005|