Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: ,  propose a service-oriented reliability model that dynamically calculates the reliability of composite b services with rollback recovery based on the real-time reliabilities of the atomic b services of the composition. Our model is a hybrid reliability model based on both path-based and state-based models. Many reliability models assume that failure or error arrival times are exponentially distributed. This is inappropriate for b services as error arrival times are dependent on the operating state including workload of servers where the b service resides. In this manuscript,  modify our previous model (for software based on the Doubly Stochastic Model and Renewal Processes) to evaluate the reliability of atomic b services. In order to fix our idea,  developed the case of one simple b service which contains two states, i.e., idle and active states. In real-world applications, where b services could contain quite a large number of atomic services, the calculus as ll as the computing complexity increases greatly. To limit our computing efforts and calculus,  chose the bounded set techniques that  apply using the previously developed stochastic model. As a first type of system combination,  proposed to study a scheme based on combining b services into parallel and serial configurations with centralized coordination. In this case, the broker has an acceptance testing mechanism that examines the results returned from a particular b service. If it was acceptable, then the computation continues to the next b service. Otherwise, it involves rollback and invokes another b service already specified by a checkpoint algorithm. Finally, the acceptance test is conducted using the broker. The broker can be considered as a single point of failure. To increase the reliability of the broker introduced in our systems and mask out errors at the broker level,  suggest a modified general scheme based on Triple modular redundancy and N-version programming. To imitate a real scenario where errors could happen at any stage of our application and improve the quality of Service QoS of the proposed model,  introduce fault-tolerance techniques using an adaption of the recovery block technique.
['H. Elfawal Mansour', 'Tharam S. Dillon']
I am writing a research paper on a idea Dependability and Rollback Recovery for Composite Web Services
[{"from": "human", "value": "I am writing a research paper on a idea Dependability and Rollback Recovery for Composite Web Services"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: ,  propose a service-oriented reliability model that dynamically calculates the reliability of composite b services with rollback recovery based on the real-time reliabilities of the atomic b services of the composition. Our model is a hybrid reliability model based on both path-based and state-based models. Many reliability models assume that failure or error arrival times are exponentially distributed. This is inappropriate for b services as error arrival times are dependent on the operating state including workload of servers where the b service resides. In this manuscript,  modify our previous model (for software based on the Doubly Stochastic Model and Renewal Processes) to evaluate the reliability of atomic b services. In order to fix our idea,  developed the case of one simple b service which contains two states, i.e., idle and active states. In real-world applications, where b services could contain quite a large number of atomic services, the calculus as ll as the computing complexity increases greatly. To limit our computing efforts and calculus,  chose the bounded set techniques that  apply using the previously developed stochastic model. As a first type of system combination,  proposed to study a scheme based on combining b services into parallel and serial configurations with centralized coordination. In this case, the broker has an acceptance testing mechanism that examines the results returned from a particular b service. If it was acceptable, then the computation continues to the next b service. Otherwise, it involves rollback and invokes another b service already specified by a checkpoint algorithm. Finally, the acceptance test is conducted using the broker. The broker can be considered as a single point of failure. To increase the reliability of the broker introduced in our systems and mask out errors at the broker level,  suggest a modified general scheme based on Triple modular redundancy and N-version programming. To imitate a real scenario where errors could happen at any stage of our application and improve the quality of Service QoS of the proposed model,  introduce fault-tolerance techniques using an adaption of the recovery block technique."}]