Requirements-driven verification of WSBPEL processes

Mohsen Rouached*, Claude Godart

*Corresponding author for this work

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

19 Citations (Scopus)

Abstract

Current Web services composition proposals, such as BPML, WSBPEL, WSCL and OWL-S, provide solutions for describing the control and data flows in Web service composition. However, such proposals remain at the descriptive level, without providing any kind of mechanisms or tool support for analysis and verification. Therefore, there is a growing interest for the verification techniques which enable designers to test and repair design errors even before actual running of the service, or allow designers to detect erroneous properties and formally verify whether the service process design does have certain desired properties. In this paper, we propose to verify Web services composition using an event driven approach. We assume Web services that are coordinated by a composition process expressed in WSBPEL and we use Event Calculus to specify the properties and requirements to be monitored.

Original languageEnglish
Title of host publicationProceedings - 2007 IEEE International Conference on Web Services, ICWS 2007
Pages354-363
Number of pages10
DOIs
Publication statusPublished - 2007
Externally publishedYes
Event2007 IEEE International Conference on Web Services, ICWS 2007 - Salt Lake City, UT, United States
Duration: Jul 9 2007Jul 13 2007

Publication series

NameProceedings - 2007 IEEE International Conference on Web Services, ICWS 2007

Other

Other2007 IEEE International Conference on Web Services, ICWS 2007
Country/TerritoryUnited States
CitySalt Lake City, UT
Period7/9/077/13/07

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Information Systems
  • Information Systems and Management
  • Electrical and Electronic Engineering

Fingerprint

Dive into the research topics of 'Requirements-driven verification of WSBPEL processes'. Together they form a unique fingerprint.

Cite this